.\" -*- mode: troff; coding: utf-8 -*-
.TH "" "5" ""
.SH NAME
.LP
alpm-repo-desc - File format for the metadata representation of ALPM based packages in package repositories (version 1).
.SH DESCRIPTION
.LP
The \fBalpm-repo-desc\fR format is a textual format that represents the metadata of a single package in a specific version in a repository.
Each file describes various properties of an \fBalpm-package\fR file, including its name, version, dependencies, size, licensing information, and more.
For a full list of properties refer to its \fBsections\fR.
.PP
The accumulation of all \fBalpm-repo-desc\fR files in an \fBalpm-repo-db\fR describe the current state of the repository (i.e. which packages are available in what version).
.PP
An operating system relying on \fBA\fRrch \fBL\fRinux \fBP\fRackage \fBM\fRanagement maintains one or more \fBalpm-repo-db\fR files which each contain one \fBalpm-repo-desc\fR file per package, each named \fIdesc\fR and located in a unique, per-package directory.
More specifically, package management software such as \fBpacman\fR and related tools use this file format e.g. to resolve dependencies and to display package information of \fBalpm-package\fR files in repositories.
.PP
The data in an \fBalpm-repo-desc\fR file is derived from an \fBalpm-package\fR.
Much of its metadata originates from the package\(cqs \fBPKGINFO\fR data.
An \fBalpm-repo-desc\fR file is usually created by software managing an \fBalpm-repo\fR, such as \fBrepo-add\fR.
.PP
The file format described in this document must not be confused with the \fBalpm-db-desc\fR file format, which is used in the context of a \fBlibalpm\fR database and carries a different set of metadata, but is usually also named \fIdesc\fR.
.PP
The \fBalpm-repo-desc\fR format exists in multiple versions.
This document describes version 1, which is a legacy version and has been available since the release of \fBpacman\fR 5.1.0 on 2018-05-28.
For the latest specification, refer to \fBalpm-repo-desc\fR.
.SS
General Format
.LP
An \fBalpm-repo-desc\fR file is a UTF-8 encoded, newline-delimited file consisting of a series of \fBsections\fR.
.PP
Each section starts with a unique \fIsection header line\fR.
The section header line is followed by one or more lines with a \fIsection-specific value\fR each.
All \fIsection-specific values\fR must consist of \fBprintable ASCII characters\fR[1] unless stated otherwise.
A section ends when another section header line is encountered or the end of the file is reached.
.PP
Empty lines between sections are ignored.
.SS
Sections
.LP
Each \fIsection header line\fR contains the \fIsection name\fR in all capital letters, surrounded by percent signs (e.g. \f(CR%NAME%\fR).
\fISection names\fR serve as key for each \fIsection-specific value\fR.
.PP
Each section allows for a single \fIsection-specific value\fR, following the \fIsection header line\fR.
As exemption to this rule the \f(CR%LICENSE%\fR, \f(CR%GROUPS%\fR, \f(CR%CHECKDEPENDS%\fR, \f(CR%DEPENDS%\fR, \f(CR%OPTDEPENDS%\fR, \f(CR%REPLACES%\fR, \f(CR%CONFLICTS%\fR and \f(CR%PROVIDES%\fR sections may have more than one \fIsection-specific value\fR.
.SS
%FILENAME%
.LP
The file name of the \fBalpm-package\fR (e.g. \f(CRexample-1.2.3-any.pkg.tar.zst\fR).
.SS
%NAME%
.LP
An \fBalpm-package-name\fR, which represents the name of a package (e.g. \f(CRexample\fR).
.SS
%BASE%
.LP
An \fBalpm-package-base\fR which represents the package base from which a package originates.
If a package is not an \fBalpm-split-package\fR, the value is the same as that of the \f(CR%NAME%\fR section.
If a package is an \fBalpm-split-package\fR, the value may be different from that in the \f(CR%NAME%\fR section.
.SS
%VERSION%
.LP
An \fBalpm-package-version\fR (\fIfull\fR or \fIfull with epoch\fR) which represents the version of a package (e.g. \f(CR1.0-1\fR).
.SS
%DESC%
.LP
The description of the package.
The value is a UTF-8 string, zero or more characters long (e.g. \f(CRA project used for something\fR).
If the description is empty, the section can be omitted.
.SS
%GROUPS%
.LP
An \fBalpm-package-group\fR that denotes a distribution-wide group the package is in.
One or more values may be present.
If the package is not in a group, the section is omitted.
.PP
The value is represented by a UTF-8 string.
Although it is possible to use a UTF-8 string, it is highly recommended to rely on the \fBalpm-package-name\fR format for the value instead, as package managers may use a package group to install an entire group of packages.
.SS
%CSIZE%
.LP
The size of the compressed \fBalpm-package\fR in bytes.
The value is a non-negative integer (e.g. \f(CR1818463\fR).
.SS
%ISIZE%
.LP
The size of the (uncompressed and unpacked) package contents in bytes.
The value is a non-negative integer representing the absolute size of the contents of the package, with multiple hardlinked files counted only once (e.g. \f(CR181849963\fR).
.SS
%MD5SUM%
.LP
The \fBMD-5\fR[2] hash digest of the \fBalpm-package\fR file.
The string consists of 32 hexadecimal characters (e.g. \f(CRd3b07384d113edec49eaa6238ad5ff00\fR).
.SS
%SHA256SUM%
.LP
The \fBSHA-256\fR[3] hash digest of the \fBalpm-package\fR file.
The string consists of 64 hexadecimal characters (e.g. \f(CRb5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c\fR).
.SS
%PGPSIG%
.LP
The \fBbase64\fR[4] encoded \fBOpenPGP signature\fR[5] for the \fBalpm-package\fR file (e.g. \f(CRiHUEABYKAB0WIQRizHP4hOUpV7L92IObeih9mi7GCAUCaBZuVAAKCRCbeih9mi7GCIlMAP9ws/jU4f580ZRQlTQKvUiLbAZOdcB7mQQj83hD1Nc/GwD/WIHhO1/OQkpMERejUrLo3AgVmY3b4/uGhx9XufWEbgE=\fR).
.SS
%URL%
.LP
The URL for the project of the package.
The value is a valid URL or an empty string (e.g. \f(CRhttps://example.org\fR).
If the URL is an empty string, the section can be omitted.
.SS
%LICENSE%
.LP
An optional set of license identifiers that apply for the package.
One or more values may be present.
If there is no license identifier, the section is omitted.
.PP
Each value represents a license identifier, which is a string of non-zero length (e.g. \f(CRGPL\fR).
Although no specific restrictions are enforced for the value aside from its length, it is highly recommended to rely on SPDX license expressions (e.g. \f(CRGPL-3.0-or-later\fR or \f(CRApache-2.0 OR MIT\fR).
See \fBSPDX License List\fR[6] for further information.
.SS
%ARCH%
.LP
The architecture of the package (see \fBalpm-architecture\fR for further information).
The value must be covered by the set of alphanumeric characters and \(oq_\(oq (e.g. \f(CRx86_64\fR or \f(CRany\fR).
.SS
%BUILDDATE%
.LP
The date at which the build of the package started.
The value must be numeric and represent the seconds since the Epoch, aka. \(oqUnix time\(cq (e.g. \f(CR1729181726\fR).
.SS
%PACKAGER%
.LP
The User ID of the entity, that built the package.
The value is meant to be used for identity lookups and represents an \fBOpenPGP User ID\fR[7].
As such, the value is a UTF-8-encoded string, that is conventionally composed of a name and an e-mail address, which aligns with the format described in \fBRFC 2822\fR\c
.UR e.g.%20%60John%20Doe%20%3Cjohn@example.org%3E%60
8
.UE \c
\&.
.SS
%REPLACES%
.LP
Another \fIvirtual component\fR or \fIpackage\fR, that the package replaces upon installation.
One or more values may be present.
If the package does not replace anything, the section is omitted.
The value is an \fBalpm-package-relation\fR of type \fBreplacement\fR (e.g. \f(CRexample\fR or \f(CRexample=1.0.0\fR).
.SS
%CONFLICTS%
.LP
Another \fIvirtual component\fR or \fIpackage\fR, that the package conflicts with.
One or more values may be present.
If the package does not conflict with anything, the section is omitted.
The value is an \fBalpm-package-relation\fR of type \fBconflict\fR (e.g. \f(CRexample\fR or \f(CRexample=1.0.0\fR).
.SS
%PROVIDES%
.LP
Another \fIvirtual component\fR or \fIpackage\fR, that the package provides.
One or more values may be present.
If the package does not provide anything, the section is omitted.
The value is an \fBalpm-package-relation\fR of type \fBprovision\fR (e.g. \f(CRexample\fR or \f(CRexample=1.0.0\fR).
.SS
%DEPENDS%
.LP
A run-time dependency of the package (\fIvirtual component\fR or \fIpackage\fR).
One or more values may be present.
If the package has no run-time dependency, the section is omitted.
The value is an \fBalpm-package-relation\fR of type \fBrun-time dependency\fR (e.g. \f(CRexample\fR or \f(CRexample=1.0.0\fR).
.SS
%OPTDEPENDS%
.LP
An optional dependency of the package (\f(CRvirtual component\fR or \f(CRpackage\fR).
One or more values may be present.
If the package has no optional dependency, the section is omitted.
The value is an \fBalpm-package-relation\fR of type \fBoptional dependency\fR (e.g. \f(CRexample\fR or \f(CRexample: this is a description\fR).
.SS
%MAKEDEPENDS%
.LP
A dependency for building the upstream software of the package.
One or more values may be present.
If the package has no build dependency, the section is omitted.
The value is an \fBalpm-package-relation\fR of type \fBbuild dependency\fR (e.g. \f(CRexample\fR or \f(CRexample=1.0.0\fR).
.SS
%CHECKDEPENDS%
.LP
A dependency for running tests of the package\(cqs upstream project.
One or more values may be present.
If the package has no test dependency, the section is omitted.
The value is an \fBalpm-package-relation\fR of type \fBtest dependency\fR (e.g. \f(CRexample\fR or \f(CRexample=1.0.0\fR).
.SH EXAMPLES
.LP
A full example of an \fBalpm-repo-desc\fR file for a package named \f(CRexample\fR in version \f(CR1.0.0-1\fR:
.LP
.EX
%FILENAME%
example-1.0.0-1-any.pkg.tar.zst

%NAME%
example

%BASE%
example

%VERSION%
1.0.0-1

%DESC%
An example package

%GROUPS%
example-group
other-group

%CSIZE%
1818463

%ISIZE%
18184634

%MD5SUM%
d3b07384d113edec49eaa6238ad5ff00

%SHA256SUM%
b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c

%PGPSIG%
iHUEABYKAB0WIQRizHP4hOUpV7L92IObeih9mi7GCAUCaBZuVAAKCRCbeih9mi7GCIlMAP9ws/jU4f580ZRQlTQKvUiLbAZOdcB7mQQj83hD1Nc/GwD/WIHhO1/OQkpMERejUrLo3AgVmY3b4/uGhx9XufWEbgE=

%URL%
https://example.org

%LICENSE%
MIT
Apache-2.0

%ARCH%
x86_64

%BUILDDATE%
1729181726

%PACKAGER%
Foobar McFooface <foobar@mcfooface.org>

%REPLACES%
other-pkg-replaced

%CONFLICTS%
other-pkg-conflicts

%PROVIDES%
example-component

%DEPENDS%
glibc
gcc-libs

%OPTDEPENDS%
bash: for a script

%MAKEDEPENDS%
cmake

%CHECKDEPENDS%
bats
.EE
.PP
A minimal example of an \fBalpm-repo-desc\fR file for an \fBalpm-meta-package\fR named \f(CRexample-meta\fR in version \f(CR1.0.0-1\fR:
.LP
.EX
%FILENAME%
example-meta-1.0.0-1-any.pkg.tar.zst

%NAME%
example-meta

%BASE%
example-meta

%VERSION%
1.0.0-1

%DESC%
An example meta package

%CSIZE%
4634

%ISIZE%
0

%MD5SUM%
d3b07384d113edec49eaa6238ad5ff00

%SHA256SUM%
b5bb9d8014a0f9b1d61e21e796d78dccdf1352f23cd32812f4850b878ae4944c

%PGPSIG%
iHUEABYKAB0WIQRizHP4hOUpV7L92IObeih9mi7GCAUCaBZuVAAKCRCbeih9mi7GCIlMAP9ws/jU4f580ZRQlTQKvUiLbAZOdcB7mQQj83hD1Nc/GwD/WIHhO1/OQkpMERejUrLo3AgVmY3b4/uGhx9XufWEbgE=

%URL%
https://example.org

%LICENSE%
GPL-3.0-or-later

%ARCH%
any

%BUILDDATE%
1729181726

%PACKAGER%
Foobar McFooface <foobar@mcfooface.org>
.EE
.SH SEE ALSO
.LP
\fBlibalpm\fR(3), \fBBUILDINFO\fR(5), \fBPKGBUILD\fR(5), \fBPKGINFO\fR(5), \fBalpm-db-desc\fR(5), \fBalpm-architecture\fR(7), \fBalpm-meta-package\fR(7), \fBalpm-package\fR(7), \fBalpm-package-name\fR(7), \fBalpm-package-relation\fR(7), \fBalpm-package-version\fR(7), \fBalpm-repo-db\fR(7), \fBalpm-split-package\fR(7), \fBpacman\fR(8), \fBrepo-add\fR(8)
.SH NOTES
.IP "1." 3
printable ASCII characters
.IP
.UR https://en.wikipedia.org/wiki/ASCII#Printable_characters
.UE
.IP "2." 3
MD-5
.IP
.UR https://en.wikipedia.org/wiki/MD5
.UE
.IP "3." 3
SHA-256
.IP
.UR https://en.wikipedia.org/wiki/SHA-2
.UE
.IP "4." 3
Base64
.IP
.UR https://en.wikipedia.org/wiki/Base64
.UE
.IP "5." 3
OpenPGP signature
.IP
.UR https://openpgp.dev/book/signing_data.html#detached-signatures
.UE
.IP "6." 3
SPDX License List
.IP
.UR https://spdx.org/licenses/
.UE
.IP "7." 3
OpenPGP User ID
.IP
.UR https://openpgp.dev/book/certificates.html#user-ids
.UE
.IP "8." 3
RFC 2822
.IP
.UR https://www.rfc-editor.org/rfc/rfc2822
.UE