Title:Supporting alternative package managers
Last-Modified:2006/09/05 20:54:30
Author:Grant Goodyear <g2boojum at>
Type:Standards Track
Post-History:15-Jun-2006, 6-Sep-2006



The council rejected this GLEP in favor of starting from a package manager API and requiring Gentoo package managers in the tree to support that API. (That API is still pending, however.)


To support alternatives to the official package manager (portage, at the time of this writing), some sane ground rules need to be set. Specifically, no alternative ebuild-based package manager may be added to the tree unless it successfully works with all ebuilds supported by the official package manager. Moreover, no ebuilds may be added to the tree unless they are supported (without change) by the official package manager.



The first rule sets a reasonable bar for adding an alternative package manager to the tree. Note that if an ebuild currently in the tree doesn't work with the official package manager, it isn't expected to work with an alternative package manager either. The second rule ensures that an alternative package manager cannot become a de-facto requirement by supporting packages that the official package manager cannot handle.

In order to keep this proposal as simple and focused as possible, it has nothing to say about the process by which an alternative package manager might one day become the official package manager. It is assumed that sanity will reign, and no package manager will become official without being able to build installation media, providing a transition path from or to the existing official package manager, etcetera.


Backwards Compatibility

Pretty much the whole point, and it's explicit here.


This document has been placed in the public domain.