Paludis Logo Introduction Hooks environment.conf sets/
Bugs, Requests, Support Syncers keywords.conf repositories/
Overview Fetchers use.conf ebuild
FAQ Env Vars licenses.conf vdb
Clients File Formats mirrors.conf installed unpackaged
Configuration Dep Specs package_mask.conf  
API specpath.conf bashrc  

Repositories

This document applies only to clients using PaludisEnvironment. Any standard client that supports a --environment command line option uses PaludisEnvironment unless overridden, either by explicitly selecting another environment (e.g. --environment portage) or, on distributions also supporting Portage, by lack of a Paludis configuration and presence of a Portage configuration.

Each file in repositories/ named *.conf defines a repository. A repository configuration file is a standard key=value config file, and it may be in bash format (in which case it has a .bash extension rather than .conf). The repository_defaults.conf file (which does not live in the repositories subdirectory), if it exists, is treated as if it were prepended to each individual file.

The filenames used for repository configuration files have no effect upon the names of the repositories. Whilst you could use the name giant-space-monkey.conf for the repository named gentoo, for user sanity reasons it is best to use the repository name as the filename.

Predefined Keys

The following keys are predefined. They should not be modified.

root
The filesystem root. Relevant if specpath.conf is in use. Using this variable can create a configuration system that works both inside and outside of a chroot (e.g. location = ${root}/var/db/paludis/repositories/paludis-overlay).

General Keys

The following keys are meaningful for all repository formats.

format
Determines which repository class Paludis uses to create the repository. Example formats are ebuild, vdb and installed_unpackaged. Mandatory.
importance
Must be an integer. Used by Paludis to determine from which repository a package should be selected, all other things being equal (a higher importance is preferred over a lower importance). By default, 0, except if the master_repository key is set, in which case it is 10 instead.

For format-specific keys, see the documentation for that format.

Predefined Repositories

If using a distribution that supports old-style virtuals, two repositories are magically defined:

virtuals
A special repository that contains special package entries for old style virtuals, mapping them to their providers.
installed-virtuals
A special repository that contains special package entries for installed old style virtuals (provided packages).