architecture =

A string setting the CPU architecture used for any repository, which does not define it. Understood values are

"aarch64", "any", "arm", "armv6h", "armv7h", "i486", "i686", "pentium4", "riscv32", "riscv64", "x86_64", "x86_64_v2", "x86_64_v3", "x86_64_v4"

archiving =

An optional table or boolean value, which defines the archiving options used for any repository, that do not define them explicitly. When unset or set to true, default archiving options are created. If set to false, archiving is disabled by default, but may still be set per repository. When defined as a table, the option has to define the following key-value pairs:

build_requirements_exist =

An optional boolean value, which defines whether the build requirements of added packages must exist in the archive (if configured), any of the stability layers of the target repository or the set of packages being added. When unset, the value will be set to the default (see DEFAULT OPTIONS). When set to false, the build requirements of added packages are not checked, when set to true, they are checked. This setting may still be overriden per repository.

database_compression =

A string setting the database compression used for any repository, which does not define it. Understood values are

"", "bz2", "gz", "xz", "zst"

management_repo

A table providing configuration for the management repository for any repository, which does not define one explicitly. As each configured binary package repository is represented as a subdirectory structure in the management repository, several repositories can share the same management_repo.

1057

package_pool =

A string setting a directory that serves as the package pool for any repository, which does not define it.

package_verification =

An optional string setting the implementation of the package signature verification for all repositories. If a signature verification implementation is selected, packages that are added to the repository must be signed. Understood values are

"pacman-key"

source_pool =

A string setting a directory that serves as the source tarball pool for any repository, which does not define it.

desc_version =

An integer setting the desc version used when exporting the management repository to a repository sync database. Understood values are

2, 1

files_version =

An integer setting the files version used when exporting the management repository to a repository sync database. Understood values are

1

architecture =

An optional string setting the CPU architecture. Understood values are

"aarch64", "any", "arm", "armv6h", "armv7h", "i486", "i686", "pentium4", "riscv32", "riscv64", "x86_64", "x86_64_v2", "x86_64_v3", "x86_64_v4"

archiving =

An optional inline table or boolean value, which defines the archiving options. When unset or set to true, the global archiving options are used. If set to false, archiving is disabled.

NOTE: When repositories are used together, they should be using the same archiving options.

When defined as an inline table, the option has to define the following key-value pairs:

build_requirements_exist =

An optional boolean value, which defines whether the build requirements of added packages must exist in the archive (if configured), any of the stability layers of the target repository or the set of packages being added. When unset, the value will be set to the value defined globally. When set to false, the build requirements of added packages are not checked, when set to true, they are checked.

database_compression =

An optional string setting the database compression used for the repository. Understood values are

"", "bz2", "gz", "xz", "zst"

group =

An optional positive integer, which defines the group a repository belongs to.

NOTE: When repositories are grouped together, the pkgbase and package names must be unique amongst them (i.e. the same package can not exist in two repositories at the same time - this is different from the same package existing in different stability layers of the same repository!). Furthermore, the repositories must use the same management repository (which resides below the management repository base directory), the same package repository base directory, the same package pool base directory and the same source pool base directory!

management_repo =

An optional inline table providing configuration for the management repository of the repository. If it is provided, it has precedence over a globally defined management_repo. As each configured repository is represented as a subdirectory structure in the management repository, several repositories can share the same management_repo.

1057

package_url_validation =

An optional inline table providing configuration for the validation of source URLs. Source URLs are links, that may be provided per pkgbase using repod-file and serve as reference to the source files (e.g. PKGBUILD) for each package.

name =

A string setting the name of the repository. It is used to construct the location below which stable package data of the repository is stored.

NOTE: The name and architecture combination must be unique among all repositories.

If the string denotes a relative directory it is used below the default package repository base directory and management repository base directory (see DEFAULT DIRECTORIES).

If the string denotes an absolute directory it is used directly and the default base directories are disregarded.

debug =

An optional string setting the debug name of the repository. It is used to construct the location below which stable debug package data of the repository is stored.

NOTE: When using this option and also using the staging or testing options, the staging_debug and testing_debug options (respectively) must be set as well.

If the string denotes a relative directory it is used below the default package repository base directory and management repository base directory (see DEFAULT DIRECTORIES).

If the string denotes an absolute directory it is used directly and the default base directories are disregarded.

package_pool =

An optional string setting a directory that serves as the package pool for the repository.

NOTE: If repositories move packages amongst one another, they need to use the same package_pool.

If the string denotes a relative directory it is used below the default package pool base directory (see DEFAULT DIRECTORIES).

If the string denotes an absolute directory it is used directly and the default base directories are disregarded.

source_pool =

An optional string setting a directory that serves as the source tarball pool for the repository.

NOTE: If repositories move packages amongst one another, they need to use the same source_pool.

If the string denotes a relative directory it is used below the default source pool base directory (see DEFAULT DIRECTORIES).

If the string denotes an absolute directory it is used directly and the default base directories are disregarded.

staging =

An optional string setting the staging name of the repository. It is used to construct the location below which staging package data of the repository is stored.

If the string denotes a relative directory it is used below the default package repository base directory and management repository base directory (see DEFAULT DIRECTORIES).

If the string denotes an absolute directory it is used directly and the default base directories are disregarded.

staging_debug =

An optional string setting the staging debug name of the repository. It is used to construct the location below which staging debug package data of the repository is stored.

NOTE: The staging and debug option must be set when using this option. Similarly, if debug and staging are configured for a repository, this option also has to be configured.

If the string denotes a relative directory it is used below the default package repository base directory and management repository base directory (see DEFAULT DIRECTORIES).

If the string denotes an absolute directory it is used directly and the default base directories are disregarded.

testing =

An optional string setting the testing name of the repository. It is used to construct the location below which testing package data of the repository is stored.

If the string denotes a relative directory it is used below the default package repository base directory and management repository base directory (see DEFAULT DIRECTORIES).

If the string denotes an absolute directory it is used directly and the default base directories are disregarded.

testing_debug =

An optional string setting the testing debug name of the repository. It is used to construct the location below which testing debug package data of the repository is stored.

NOTE: The testing and debug option must be set when using this option. Similarly, if debug and testing are configured for a repository, this option also has to be configured.

If the string denotes a relative directory it is used below the default package repository base directory and management repository base directory (see DEFAULT DIRECTORIES).

If the string denotes an absolute directory it is used directly and the default base directories are disregarded.

DEFAULT DIRECTORIES

DEFAULT OPTIONS

"any"

true

"gz"

"default"

2

1

Example 1. One repository with custom architecture

[[repositories]]
architecture = "x86_64"
name = "repo"
staging = "repo-staging"
testing = "repo-testing"

Example 2. Two repositories with debug locations

[[repositories]]
architecture = "x86_64"
name = "repo1"
debug  = "repo1-debug"
staging = "repo1-staging"
staging_debug = "repo1-staging-debug"
testing = "repo1-testing"
testing_debug = "repo1-testing-debug"
[[repositories]]
architecture = "x86_64"
name = "repo2"
debug = "repo2-debug"
staging = "repo2-staging"
staging_debug = "repo2-staging-debug"
testing = "repo2-testing"
testing_debug = "repo2-testing-debug"

Example 3. One repository with custom management repo

[[repositories]]
architecture = "x86_64"
name = "repo1"
staging = "repo-staging"
testing = "repo-testing"
management_repo = {directory = "custom_management", url = "ssh://user@custom-upstream.tld/repository.git"}

Example 4. One repository with non-standard directories

[[repositories]]
architecture = "x86_64"
name = "/absolute/path/to/repo1"
staging = "/absolute/path/to/repo-staging"
testing = "/absolute/path/to/repo-testing"
management_repo = {directory = "/absolute/path/to/management_repo"}

Example 5. One repository with pacman-key based signature verification

package_verification = "pacman-key"
[[repositories]]
architecture = "x86_64"
name = "repo1"
debug = "repo-debug"
staging = "repo-staging"
testing = "repo-testing"

Example 6. One repository with source URL validation

[[repositories]]
architecture = "x86_64"
name = "repo1"
debug = "repo-debug"
staging = "repo-staging"
testing = "repo-testing"
package_url_validation = {urls = ["https://custom.tld"], tls_required = true}

Example 6. One repository without archiving

[[repositories]]
architecture = "x86_64"
archiving = false
name = "repo1"

Example 7. One repository without checks for build requirements

[[repositories]]
architecture = "x86_64"
build_requirements_exist = false
name = "repo1"

Example 8. Two repositories in the same group

[[repositories]]
architecture = "x86_64"
build_requirements_exist = false
name = "repo1"
group = 1
[[repositories]]
architecture = "x86_64"
build_requirements_exist = false
name = "repo2"
group = 1