Paludis Logo Introduction General Questions
Bugs, Requests, Support How do I ...?
Overview Operation
FAQ Stricter than Portage
Clients Things Paludis Does Differently
Configuration Repository Questions
API Upgrades, Old Bugs, Migration

FAQ: Operation

Paludis does not update DEPENDs of already installed packages

Paludis ignores build time dependencies (DEPENDs) of already installed packages by default. If you need a different behaviour, use the --dl-installed-deps-pre option. You may also want to use the everything set rather than world.

Updating world misses things

Paludis doesn't 'miss' packages. If you think it is missing something, check the following:

Get package information for a bug report

Use paludis --info to get general configuration information. Paludis will not show any configuration that is 'per-package' in this output. (This is different to emerge, which misleadingly shows an arbitrary global configuration no matter what.)

If you are submitting a bug report for a particular package, use paludis --info spec instead. If it's an installed package, spec can usually just be the qualified package name (for example, paludis --info sys-apps/paludis). If you're installing a package, you should instead specify an exact package ID (such as paludis --info =sys-apps/paludis-0.26.0_alpha12::paludis-overlay).

What do those fancy arrows when merging things mean?

They tell how each file is merged to root. They consist of three parts:

Profiles Updates for Package Moves and Slot Moves

Gentoo includes support for repositories specifying that a package has moved (e.g. app-misc/foo is now called app-admin/foo) or changed slot (e.g. app-misc/foo:0 is now app-misc/foo:2). These are known as 'profiles updates'. Paludis will perform profiles updates after a sync.

Sometimes it is possible for renames to cause collisions. For example, if foo is being renamed to bar, and you have both foo and bar installed, Paludis will be unable to perform the update. In this situation, you should generally manually uninstall the older of foo or bar.

I can't install */*::installed or */*::overlay->

You can't install (or reinstall) a package ID that is already installed. The foo/bar-1.23 you have installed has absolutely nothing whatsoever to do with any other foo/bar-1.23, and by specifying ::installed or ::overlay-> you are specifically saying "give me the installed ID".