The metadata/layout.conf file is a file describing global properties of a repository.
- The file consists of a number of key-value pairs, one pair per line, with the two separated by
- Comment lines start with
key1 = value1 # comment key2 = value2
This page contains only some of the possible keys and values in layout.conf. For a thorough listing, refer to the Portage manual:
man 5 portage
This setting specifies the name of the repository. It takes precedence over an existing value in profiles/repo_name:
repo-name = foo-overlay
The masters key specifies a list of master repositories for this particular repository. Whenever installing an ebuild from the particular repository, the package manager can use eclasses from one more more master repositories.
The most common example is a repository (overlay) which provides additional packages for Gentoo. Such a package uses eclasses from the gentoo ebuild repository:
masters = gentoo
A particular repository may have more than a single masters entry. These are not inherited over repositories. In the following example eclasses from gentoo take precedence over eclasses in python, that share the same name:
masters = python gentoo
Finally, a stand-alone repository like gentoo should provide an empty masters list. This means that all eclasses used by packages in that repository must be found in that repository:
This setting bans EAPIs (repoman will fail):
eapis-banned = 0 1
This setting marks EAPIs as deprecated (repoman will prompt a warning):
eapis-deprecated = 2 3
If enabled, the commits made in this repository will be signed:
sign-commits = true
This applies only to git repositories. It requires git 1.7.9 or newer.
The key used to sign commits can be set through:
git config user.signingkey <keyid>
Enabled by default. If enabled, the manifest files will be signed whenever committing to this repository from a GPG-enabled client:
sign-manifests = false
In Portage, the manifest signing is enabled by adding
sign to the FEATURES variable in /etc/portage/make.conf.
Disabled by default. If enabled, thin manifests will be used inside the repository instead of the regular manifests:
thin-manifests = true
Strict by default. Enforces a correct manifest for each package:
use-manifests = strict
Possible values are
strict to enforce manifest usage and
false to disable manifest usage.