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 section gives an overview on where to configure various things in Paludis.


 * Toolchain and environmental package behavior:
 * Keywords (allowing packages from unstable branch): or
 * USE flags (enabling package features): or
 * Licenses: or
 * Package (un)masks: or  and  or  respectively
 * Hooks: various subdirectories of
 * Output and log behavior:

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:

You can omit the  part, in which case Paludis will try to look it up.

The switch tells Paludis to actually execute the resolution and apply updates and so on. Otherwise it will just give you a list of what it would do. You can use a resume-file though, which is typically used on world updates.

Uninstall a package
Either this way:

or the following way, which lets you combine it with installation of packages:

If you want to uninstall all unneeded packages, do

Update world
If you want to review the changes that will be performed before they are actually applied, you can do this:

Now review the changes. If everything is ok, we apply these changes:

If a build fails, you can try to fix it manually and then resume the rest of the resolution again:

Install a repository
If you have configured unavailable layman repositories as per the the Paludis guide, then you should be able to install 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:

Post-Configure a package
Some ebuilds have a pkg_config phase which allows post-install configuration for packages.

A lot of ebuilds might output something like this:

* In order to update your hddtemp database, run: * emerge --config =app-admin/hddtemp-0.3_beta15-r7

Since we don't use portage, we have to do this instead for the above case:

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.

Keep output logs
Add the following file:

Make Paludis quiet
Add the following file:

External resources

 * http://exherbo.org/ - Exherbo Linux.
 * https://zaufi.github.io/my-paludis-hooks-and-addons.html