Paludis

This page is about the multi-format package manager Paludis.

Installation
Refer to the Paludis guide for instructions on how to install Paludis and set up the basic configuration.

Configuration
This sections gives an overview on where to configure various things in Paludis.


 * toolchain and environmental package behavior: /etc/paludis/bashrc
 * keywords (allowing packages from unstable branch): /etc/paludis/keywords.conf or /etc/paludis/keywords.conf.d/*.conf
 * USE flags (enabling package features): /etc/paludis/use.conf or /etc/paludis/use.conf.d/*.conf
 * licenses: /etc/paludis/licenses.conf or /etc/paludis/licenses.conf.d/*.conf
 * package (un)masks: /etc/paludis/package_mask.conf or /etc/paludis/package_mask.conf.d/*.conf and /etc/paludis/package_unmask.conf or /etc/paludis/package_unmask.conf.d/*.conf respectively
 * hooks: various subdirectories of /etc/paludis/hooks/

How do I...?
The official documentation already answers various of these questions, so this section just tries to extend it and be a little more basic.

Install a package
The most basic form is:

Install a repository
If you have configured unavailable layman repositories as per the the Paludis guide, then you should be able to install (and uninstall) repositories just like regular packages.

If the repository name could be ambiguous with a package name, then you can tell cave explicitly that this is a repository:

Tell the resolver how much work it should perform
There are 3 main switches that change the default behavior:
 * : Does as little work as possible, typically used when quickly installing a single package only
 * : Does all optional work, typically used when updating 'world'
 * : Does all optional work and always reinstalls, typically used when you want to rebuild everything after a major gcc upgrade for example

If you don't pass any of those switches, then the default behavior is roughly in between and. These switches are in fact just shorthands for more fine-grained options. Check the manpage of.