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  

licenses.conf / licences.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.

We apologise for misspelling 'licence' as 'license' throughout. This is done to match the ebuild variable 'LICENSE', whose name cannot be fixed for Gentoo-based distributions for historical reasons.

On Gentoo and derived distributions, the license.conf file controls which licenses are and are not accepted. It is a standard configuration file which may be a bash file (license.bash) and which may use the licenses.conf.d/ directory.

On Exherbo, the licence.conf file controls which licences are and are not accepted. It is a standard configuration file which may be a bash file (licence.bash) and which may use the licences.conf.d/ directory.

Each line in the file consists of a specification followed by one or more license symbols. A specification may be any of:

A license symbol can be any of:

Any token may be quoted using either single or double quotes. Note that CRAN repository entries can use spaces in license names, so quoting would be required to explicitly accept those licenses.

License settings are cumulative. To only accept listed licenses for a given spec, include -* in the symbols list.

Example

Most users will only want:

# Accept everything
*/* *