Paludis

• We use Trac for bug reports, feature requests etc.
• The current version is 0.26.1. See the release notes and changelog.

Overview

• Features: an overview of Paludis, and how it differs from its predecessor, Portage.
• Getting started: where to begin.
• Contact: how to get in touch.

FAQ

• General questions about Paludis.
• How do I do and use various things.
• Operation of Paludis.
• Stricter than Portage: why certain things happen to work with Portage, but not Paludis.
• Undesirable misfunctionality: why Paludis doesn't do certain things.
• Things Paludis does differently: why Paludis does some things differently.
• Repository questions.
• Upgrades, old bugs and migration.

Configuration

In general:

• Hooks: how to execute additional code at well defined points.
• Syncers: options for built-in syncers, and how to implement custom sync protocols or override built-in syncers.
• Fetchers: options for built-in fetchers, and how to implement custom URI fetching protocols or replace built-in fetchers.
• Environment variables that Paludis itself recognises.

For the 'Paludis' environment:

• Configuration file formats in general, including conf.d/ directories and .bash dynamic configuration files.
• Dependency specifications in general.
• specpath.conf, and where Paludis looks for configuration files.
• environment.conf: for environment options.
• keywords.conf: for keywords.
• use.conf: for USE flags.
• licenses.conf: for licence filtering.
• mirrors.conf: for mirrors.
• package_mask.conf and package_unmask.conf: for masks.
• bashrc: for package build environment options.
• sets/*.conf: for user defined package sets.
• repositories/*.conf and repository_defaults.conf, in general.
• ... and configuration keys for ebuild repositories.
• ... and configuration keys for VDB repositories.
• ... and configuration keys for installed unpackaged repositories.

Client Documentation

For users:

• paludis, the console package management client.
• contrarius, a tool for creating cross-toolchains.
• importare, the unpackaged package installer.
• inquisitio, the search client.
• reconcilio, a tool for rebuilding packages with broken linkage.

For ebuild developers and distribution maintainers:

• accerso, the mirror client.
• adjutrix, a collection of utilities for ebuild developers and arch teams.
• instruo, the metadata generation client.
• qualudis, the QA client.

API Documentation

• There are examples of how to use the API and bindings.
• The core library code is written in C++.

• Bindings are available for:

  • Ruby
  • Python