(7)

NAME

alpm-source-repo - a repository containing sources for building one or more Arch Linux Package Management (ALPM) based packages.

DESCRIPTION

ALPM based packages (see alpm-package) are created from package sources using package build software, such as makepkg. Refer to the contents section for an overview of required and optional files in an alpm-source-repo. For Arch Linux specific package build software refer to devtools and pkgctl.

  Contents

Package sources are represented by a single PKGBUILD per alpm-source-repo, which may define and/or additional require files, such as an alpm-install-scriptlet, arbitrary custom local source files for the package build process and files for tooling (e.g. configuration files, etc.). The PKGBUILD script may be accompanied by a SRCINFO file which represents a parseable data format exposing relevant metadata defined by the PKGBUILD.

  Required files

•   PKGBUILD: The package build script.

  Optional files

•   .SRCINFO: The data representation of the package build script metadata (see SRCINFO).

•   .nvchecker.toml: A minimal configuration file for nvchecker (supported by pkgctl) to allow detection of new upstream versions.

•   LICENSES/: A directory containing license files used by reuse (see RFC 0040[1] and RFC 0052[2]).

•   REUSE.toml: A configuration file for reuse which covers the license information of all files in the alpm-source-repo (see RFC 0040[1] and RFC 0052[2]).

•   alpm-install-scriptlet: An installation scriptlet that is added to a resulting alpm-package (needs to be specified in the PKGBUILD).

•   keys/pgp/: A directory containing ASCII-armored[3] OpenPGP certificates[4] that represent verifiers for OpenPGP signatures[5] created by upstreams for their release artifacts.

Apart from the above specific files, an alpm-source-repo may contain a list of arbitrary, custom source files that are used with the PKGBUILD when building package files with package build software. Common examples for these files are patches, systemd.service, systemd.socket, sysusers.d, tmpfiles.d or other configuration files.

  Version control

It is advisable to keep the contents of an alpm-source-repo in a version control system such as git. In doing so the relationship between a PKGBUILD and its resulting list of alpm-package files can be established, by associating a (preferably signed) git commit hash with the package. This is important for reproducible builds[6].

Upstream sources and build artifacts (e.g. build logs, or package files) should not be included in the git repository. They can be ignored using a gitignore file. Alternatively makepkg.conf can be used to instruct the makepkg package build tool to store artifacts elsewhere.

  Best practices

Although a basic setup technically only requires a PKGBUILD file, further components are considered best practice.

•   .SRCINFO: Creating this file (see SRCINFO for the description of the format) and keeping it in sync with the PKGBUILD file allows consumers of the alpm-source-repo to extract metadata of the PKGBUILD without requiring bash.

•   .nvchecker.toml: Using nvchecker (e.g. through pkgctl) enables users to check for new releases of an upstream project.

•   LICENSES/ and REUSE.toml: A reuse setup ensures that licensing is clearly defined for all files in the alpm-source-repo which enables others to use it and adapt it.

•   keys/pgp/: If the PKGBUILD defines an alpm-package-source with OpenPGP signature verification[7], storing current versions of relevant ASCII-armored[3] OpenPGP certificates[4] allows users of the alpm-source-repo to authenticate the upstream artifacts using OpenPGP signatures[5].

EXAMPLES

The following example illustrates a basic alpm-source-repo:

    .
    └── PKGBUILD

The following example illustrates a more complete alpm-source-repo with best practices applied for a package named example:

    .
    ├── .SRCINFO
    ├── .nvchecker.toml
    ├── LICENSES
    │   └── 0BSD.txt
    ├── PKGBUILD
    ├── REUSE.toml
    ├── example.install
    └── keys
        └── pgp
            └── F1D2D2F924E986AC86FDF7B36C94BCDF32BEEC15.asc

SEE ALSO

bash(1), git(1), nvchecker(1), pkgctl(1), reuse(1), PKGBUILD(5), SRCINFO(5), alpm-install-scriptlet(5), gitignore(5), makepkg.conf(5), systemd.service(5), systemd.socket(5), sysusers.d(5), tmpfiles.d(5), alpm-package(7), alpm-package-source(7), devtools(7), makepkg(8)

NOTES

1.  RFC 0040

    https://rfc.archlinux.page/0040-license-package-sources/

2.  RFC 0052

    https://rfc.archlinux.page/0052-reuse/

3.  ASCII armored

    https://openpgp.dev/book/armor.html

4.  OpenPGP certificates

    https://openpgp.dev/book/certificates.html

5.  OpenPGP signatures

    https://openpgp.dev/book/signatures.html

6.  reproducible builds

    https://reproducible-builds.org/

7.  OpenPGP signature verification

    https://openpgp.dev/book/verification.html