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  

package_mask.conf and package_unmask.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 package_mask.conf file allows a package to be explicitly masked. The package_unmask.conf file allows repository and profile masked packages to be unmasked. Both are standard configuration files which may be bash files (package_mask.bash etc) and which may use a .conf.d/ directory.

Each line in the file consists of a specification.

The specifications in package_unmask.conf override the specifications in package_mask.conf. If a package version is matched by entries in both files, it is unmasked.

Example

An example package_mask.conf:

# Mask gcc 4.2 for now
sys-devel/gcc:4.2

# Mask all versions of Portage
sys-apps/portage

And an example package_unmask.conf:

# Ignore repository and profile masks for things in the toolchain overlay
*/*::toolchain