e Repository Format
e repository format is used on Gentoo and derived distributions for repositories containing ebuilds,
and on Exherbo for repositories containing exheres packages. Except where noted, all options described below are common
to both distributions.
As well as the general keys supported for all repositories, the following keys have meaning
e format repositories:
- The location of the repository. Mandatory.
- If set to the name of another e-format repository, that repository is used as a 'master' for any part of this repository that is not defined. Also changes the default importance of this repository from 0 to 10. (In Portage terms, this is similar to saying that this repository is an overlay with the master as the main repository. However, identically named and versioned packages in this repository do not hide those in the master.) Exheres repositories describe their own masters, so this option does not apply to them.
- A space separated list of directories to use as profiles. Later entries override earlier entries. Inherited from
a master if unspecified, mandatory otherwise. (In Portage terms, this is like the
- A space separated list of directories in which to find eclasses. The first directory is used to set
ECLASSDIR, but eclasses in later directories have priority. Optional, and not used by Exheres repositories.
- Where to look for and save downloaded files. Inherited from a master. Optional.
- Where to look for repository-defined sets. Optional.
- Where to look for GLSAs (security advisories). Optional.
- Where to look for GLEP 42 news items. Optional.
- Where to look for read-only repository defined metadata cache items. If set to
/var/empty, no repository defined cache is used. Optional.
- Where to look for and save generated metadata cache items. If set to
/var/empty, no write cache is used. Optional, but recommended for repositories that do not ship with their own metadata cache.
- Boolean. If true (default), the repository name is appended to the
write_cachedirectory. Optional, for internal use.
- Boolean. If true (default is false), profiles deprecated files are ignored. Optional, for internal use.
- The EAPI to use when a package's EAPI is unknown (e.g. before it has been sourced to generate its metadata, if it does not use an EAPI filename suffix). Optional, generally set by the distribution.
- The EAPI to use when a package does not specify an EAPI, either explicitly or by suffix. Optional, generally set by the distribution.
- The EAPI to use for profiles when unspecified. Optional, generally set by the distribution.
- The directory in which to look for a names cache, and in which to generate a names cache. A names cache will
significantly speed up converting a
cat/pkg. See Getting Started for notes. Optional.
- How to sync the repository. See Syncers for supported formats. Optional if the
repository does not need to be synced. Different sync URIs to use when a different source is requested may be
sync = git+http://host/path local: git+file:///path.
- Any options to be passed to the syncer. Optional. Options for alternative sources are specified using the same format as
- The temporary directory to use when building packages. Optional.
- The repository's layout. Supported values are
exheres. Optional, usually set by the distribution.
- Whether to use Manifest2. Valid values are
- Space-separated list of hash functions to use when generating
Manifestfiles. Supported values are
WHIRLPOOL. Optional, usually set by the distribution or the repository's
- If set to
Manifestfiles will only contain
DISTentries. Optional, usually set by the distribution or the repository's
- If set to
true, this repository is treated as a destination when creating binary packages.
- When writing URIs for the binary tarball, the value of this setting is prepended to the tarball name. Typically
this setting can be ignored for local-only binary packages, and should be set to something like
mirror://yourreponame/for binary repositories that are to be distributed.
- Controls where binary package tarballs are written.
- When deciding upon keywords for a binary package, the keywords of the origin package are unioned with the
keywords in this setting. A typical value is