#title: builds.sr.ht compatibility matrix

If you have any special requests, please send an email. Only architectures supported by each Linux distribution upstream are listed, and named after the upstream port (e.g. Debian uses "amd64" while Alpine uses "x86_64").

Note: support for multi-arch builds is underway, but not yet available.

The "native" column is checked if these builds run on native hardware for that architecture, if unchecked the builds are run on emulated hardware and may suffer from poor performance.

Support lifecycle

The support lifecycle for each build image follows the upstream support cycle. Each supported upstream release is generally offered on sr.ht, as well as the bleeding edge or development releases if applicable. No sooner than two weeks after a release becomes unsupported upstream, it will be unsupported on builds.sr.ht - and anyone who's submitted recent builds using those images will get an email warning them of the impending breakage.

It's recommended that you use aliases like "alpine/latest" or "debian/testing" rather than using a specific release in your build manifests.

#Alpine Linux

Maintainer: Drew DeVault sir@cmpwn.com

Support policy: upstream

packages

The packages array is installed with apk add.

repositories

To add custom apk repositories, use repo-url key-url key-name (separated with spaces), where repo-url is the URL of the package repository and key-url is a URL from where the signing key may be downloaded, and key-name is the name of the file written to /etc/apk/keys/. If the name of the repo is prefixed with an @, it will use that prefix in apk.

Example:

repositories:
  sr.ht: >
    https://mirror.sr.ht/alpine/sr.ht/
    https://mirror.sr.ht/alpine/sr.ht/alpine%40sr.ht.rsa.pub
    alpine@sr.ht.rsa.pub

#Arch Linux

Maintainer: Drew DeVault sir@cmpwn.com

packages

The package array is installed with yay -Syu (AUR packages are transparently installed).

repositories

To add custom pacman repositories, use url#key-id, where url is the URL of the package repository and key-id is the ID of the published PGP key the packages are signed with.

#Debian

Maintainer: Drew DeVault sir@cmpwn.com

Support policy: stable, testing, unstable, and oldstable are supported. See also: upstream releases

packages

The packages array is installed with apt-get install.

repositories

To add custom repositories, specify url distro component key-id (separated by spaces), where url is the URL of the package repository, distro is e.g. jessie or stretch, component is e.g. main or non-free, and key-id is an optional PGP key ID to add to apt-key. Example:

repositories:
  sr.ht: https://mirror.sr.ht/debian/sr.ht/ stretch main DEADBEEFCAFEF00D

#Fedora

Maintainer: Timothée Floure timothee.floure@posteo.net

packages

The packages array is installed with dnf install.

repositories

Given the following list of repositories in your manifest:

repositories:
  example: https://example.org

The following commands will be used to configure it:

dnf config-manager --add-repo https://example.org
dnf config-manager --set-enabled example

#FreeBSD

Maintainer: Simon Ser contact@emersion.fr

Support policy: Upstream production releases are supported.

packages

The packages array is installed with pkg install.

repositories

Custom package repositories are not supported on FreeBSD builds.

#NixOS

Maintainer: Francesco Gazzetta fgaz@fgaz.me

Support policy: NixOS upstream does not have a clear support policy. We ship the latest stable version and the latest bleeding edge.

packages

The packages array is installed with nix-env -iA. Since it's possible to specify multiple channels, you must provide the full selection path, for example nixpkgs.hello. Note that the nixpkgs channel is not added by default.

repositories

To add custom channels, use repo-name: channel-url. The repo name is relevant, since repo-name: repo-url will execute the commands nix-channel --add repo-url repo-name and nix-channel --update repo-name. Given the nature of nix, no channels are added by default.

#OpenBSD

Maintainer: Jarkko Oranen oranenj@iki.fi

Support policy: the most recent release and the version prior are supported. See also: upstream release cycle

notes

Binary patches are applied to the base system using syspatch.

packages

The packages array is installed with pkg_add.

repositories

Custom package repositories are not supported on OpenBSD builds.

#Ubuntu

Maintainer: David Krauser david@krauser.org

Support cycle: the latest LTS, previous LTS, and the next normal release of Ubuntu are all supported. See the upstream support schedule for more information.

packages

The packages array is installed with apt-get install.

repositories

To add custom repositories, specify url distro component key-id (separated by spaces), where url is the URL of the package repository, distro is e.g. bionic or cosmic, component is e.g. main or non-free, and key-id is an optional PGP key ID to add to apt-key. Example:

repositories:
  sr.ht: https://mirror.sr.ht/debian/sr.ht/ cosmic main DEADBEEFCAFEF00D

#9front

Maintainer: Drew DeVault sir@cmpwn.com

Support cycle: no support guarantees are made for 9front

Caveats

• Git submodules are not supported by git9
• 9front ships a dated Mercurial version which is not compatible with hg.sr.ht's wire protocol
• Custom packages and custom repositories are not supported
• Shell access is not supported