mirrors/aports
3
0
Fork 0
mirror of https://gitlab.alpinelinux.org/alpine/aports.git synced 2025-06-02 17:05:07 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
aports/community/dotnet9-runtime
History
Exact
…
..
APKBUILD
aspire_5956-override-ci-env.patch
build_44361-ignore-clean-while-building-errors.patch
build_enable-timestamps.patch
dotnet.sh.in
README.md
runtime_82269-mono-thread-coop-undefine-fortify-source.patch
runtime_arm-pcode-null.patch
runtime_openssl-sha1.patch
runtime_re-enable-implicit-rejection.patch
sdk_hard-dereference-tar-gz.patch

README.md

dotnet9-runtime

This is the .NET 9.0 package for Alpine Linux.

Please report any issues using Gitlab and tag @ayakael

Building info

Generated packages

  • aspnetcore9-runtime
  • aspnetcore9-targeting-pack
  • dotnet9-apphost-pack (used by dotnet9-runtime)
  • dotnet9-hostfxr (used by dotnet-host)
  • dotnet9-runtime
  • dotnet9-runtime-artifacts (aimed for internal use as bootstrap)
  • dotnet9-runtime-bootstrap (aimed for internal use as bootstrap)
  • dotnet9-targeting-pack
  • dotnet-host

How to build dotnet9 on Alpine

As dotnet is a self-hosting compiler (thus it compiles using itself), it requires a bootstrap for the initial build. To solve this problem, this package follows the stage0 proposal outlined here

The goal of stage0 is to bootstrap dotnet with as little intervention as possible, thus allowing seamless Alpine upgrades. Unfortunately, upstream only builds bootstraps for Alpine on x86_64, aarch64, and armv7. Thus, stage0 has also been designed to be crossbuild aware, allowing bootstrapping to other platforms.

In summary, dotnet9 is built using three different aports.

  • community/dotnet9-stage0 Builds minimum components for full build of dotnet9, and packages these in an initial dotnet9-stage0-bootstrap package that dotnet9-runtime pulls.
  • community/dotnet9-runtime Builds full and packages dotnet9 fully using either stage0 or previoulsy built dotnet9 build.
  • community/dotnet9-sdk As abuild does not allow different versions for subpackages, a different aport is required to package sdk bits from dotnet9-runtime. dotnet9-runtime only builds 9.0.1xx feature branch of SDK. Thus, when a new feature branch of sdk is released, the updated components are to be built on dotnet9-sdk rather than simply repackaging dotnet9-runtime artifacts.

Crossbuilding with stage0

Crossbuilding stage0 is a three step process:

  1. Build sysroot for target platform by using scripts/bootstrap.sh in aports repo:
./bootstrap.sh $CTARGET_ARCH
  1. Although not necessary, it is recommended to add Alpine repositories to $HOME/sysroot-$CTARGET_ARCH/etc/apk/repositories, making sure to add required keys. This makes it so that whatever package is not built in step 1 will be pulled from package repos
  2. Crossbuild dotnet9-stage0 via:
CHOST=$CTARGET_ARCH abuild -r

Specification

This package follows package naming and contents suggested by upstream, with two exceptions. It installs dotnet to /usr/lib/dotnet (aka $_libdir). In addition, the package is named dotnet9 as opposed to dotnet-9.0 to match Alpine Linux naming conventions for packages with many installable versions

Contributing

The steps below are for the final package. Please only contribute to a pre-release version if you know what you are doing. Original instructions follow.

General Changes

  1. Fork the main aports repo.

  2. Checkout the forked repository.

    • git clone ssh://git@gitlab.alpinelinux.org/$USER/aports
    • cd community/dotnet9-runtime

  3. Make your changes. Don't forget to add a changelog.

  4. Do local builds.

    • abuild -r

  5. Fix any errors that come up and rebuild until it works locally.

  6. Commit the changes to the git repo in a git branch

    • git checkout -b dotnet9/<name>
    • git add any new patches
    • git remove any now-unnecessary patches
    • git commit -m 'community/dotnet9-runtime: descriptive description'
    • git push

  7. Create a merge request with your changes, tagging @ayakael for review.

  8. Once the tests in the pull-request pass, and reviewers are happy, your changes will be merged.

Updating to an new upstream release

  1. Fork the main aports repo.

  2. Checkout the forked repository.

    • git clone ssh://git@gitlab.alpinelinux.org/$USER/aports
    • cd community/dotnet9-runtime

  3. Build the new upstream source tarball. Update the versions in the APKBUILD file, and then create a snapshot. After build, update checksum.

    • abuild snapshot
    • abuild checksum

  4. Do local builds.

    • abuild -r

  5. Fix any errors that come up and rebuild until it works locally. Any patches that are needed at this point should be added to the APKBUILD file in _patches variable.

  6. Upload the source archive to a remote location, and update source variable.

  7. Commit the changes to the git repo in a git branch.

    • git checkout -b dotnet9/<name>
    • git add any new patches
    • git remove any now-unnecessary patches
    • git commit -m 'community/dotnet9-runtime: upgrade to <new-version>
    • git push

  8. Create a merge request with your changes, tagging @ayakael for review.

  9. Once the tests in the pull-request pass, and reviewers are happy, your changes will be merged.

Testing

This package uses CI tests as defined in check() function. Creating a merge-request or running a build will fire off tests and flag any issues.

The tests themselves are contained in this external repository: https://github.com/redhat-developer/dotnet-regular-tests/