specpath.conf
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.
Configuration File Locations
Paludis looks in the following places for configuration files:
- ${PALUDIS_HOME}/.paludis, if the- PALUDIS_HOMEenvironment variable is set, or- ${HOME}/.paludisotherwise.
- ${SYSCONFDIR}/paludis, where- SYSCONFDIRis- /etcon most systems.
If --environment :suffix or --environment paludis:suffix is specified, Paludis will use
.paludis-suffix or paludis-suffix. This can be used to maintain multiple configurations, for
example for chroots.
specpath.conf
If a file named specpath.conf exists in the configuration directory, Paludis uses this to find a second,
real configuration directory. It is a standard key=value configuration file. This file overwrites the key=value sets
from the commandline given in --environment(-E). Recognised keys are as follows:
- root
- The real configuration directory is taken to be ${root}/SYSCONFDIR/paludis/(note that HOME values are not used). When installing,${root}/is used rather than/as the base install location.
- config-suffix
- If set, Paludis will instead look in ${root}/SYSCONFDIR/paludis-suffixfor configuration files. By default, no configuration suffix is used under root.
- system_root
- If set, Paludis will use this value for the root for resolving dependencies. Defaults to /, and should not be changed except under exceptional circumstances.
