He's not dead, he's resting
Configuring Repositories Automatically via RepositoryRepository
Paludis is aware of packages that are in repositories you don’t have configured thanks to the unavailable repository. However, once Paludis has shown you that the package you want is in a repository you don’t have configured, you need to set up a configuration file for that repository (and any repositories it requires) and then sync. This is more work than is really necessary.
Enter RepositoryRepository, also known as r^2. Conceptually, it works as follows:
As well as providing special packages for packages in unavailable repositories, the unavailable repository also now provides packages named ‘repository/blah’ for repositories you don’t have configured. The metadata for these packages includes dependency information etc, along with useful things like the repository’s sync URI.
A new repository, using
format = repository, provides special packages for repositories you do have configured.
Repository packages in
unavailable repositories can be ‘installed’ to
repository repositories. ‘Installing’ a repository creates a configuration file for it, and then syncs the newly created repository.
The configuration file it creates is controlled by a simple template, so it can contain anything you want it to contain.
Exherbo users can follow the setup instructions to start using this. On Gentoo this functionality is not yet available, since we won’t be switching the generated unavailable data to the new format until we’re reasonably sure that everyone is using a Paludis release that supports it.