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

environment.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.

The environment.conf file can be used to control general environment settings. It is a standard key=value configuration file, and may optionally be in bash format. This file overwrites the key=value sets from the commandline given in --environment(-E). Recognised keys are as follows:

world
The location of the world file.
reduced_username
If set, Paludis will use this username rather than paludisbuild when a reduced privilege user is required.
accept_breaks_portage
Possibly-empty list of characteristics that can cause a package to be incompatible with Portage, but that should not cause the package to be masked, or * (the default) to ignore Portage compatibility entirely. Currently available characteristics are:
eapi
ebuilds with an EAPI that is not supported by Portage
version
ebuilds that use Paludis-specific features of the package version syntax
format
packages other than ebuilds
Note that this does not disable cache options that would cause interoperability problems.
portage_compatible
If set to a non-empty string, deprecated equivalent of accept_breaks_portage =.
distribution
If set, overrides the distribution used when distribution-specific defaults are used.

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. world = ${root}/var/db/pkg/world).