--- xml/htdocs/proj/en/glep/glep-0049.html 2006/05/20 14:22:15 1.2 +++ xml/htdocs/proj/en/glep/glep-0049.html 2006/05/21 10:23:55 1.3 @@ -32,9 +32,9 @@ Title:Alternative Package Manager requirements -Version:2215 +Version:2218 -Last-Modified:2006-05-20 16:18:10 +0200 (Sat, 20 May 2006) +Last-Modified:2006-05-20 20:39:14 +0200 (Sat, 20 May 2006) Author:Paul de Vrieze <pauldv at gentoo.org>, @@ -143,13 +143,18 @@

As a package manager is in a state of higher support there are higher requirements to it. The purpose of these requirements is to ensure the unity of the distribution and the package tree. For this purpose it is needed that there -is only one primary package manager.

+is only one primary package manager. This is from gentoo's perspective. From a +user perspective it is perfectly possible to use another package +manager. Candidate primary package managers and secondary package managers are +also supported in regards to bugs etc.

Primary package manager requirements

The primary package manager is the package manager that sets the standards for the tree. All ebuilds in the tree must function with the primary package manager. As the primary package manager sets the standard it does not have to -maintain compatibility with other package managers.

+maintain compatibility with other package managers. This does not mean that the +actual implementation is the standard, but that the maintainers have the ability +to define new standards, together with the other involved gentoo projects.

The primary package manager does however have the responsibility that it must be very stable. The primary package manager must maintain compatibility with old versions of itself for extended periods of time. This compatibility time is set @@ -162,6 +167,10 @@ having write support later. Another way would be the provision of a conversion tool that ensures that the on disk information maintained by the package manager is supported by the stable package manager.

+

The primary package manager maintainers further have the responsibility to allow +competition. This means that reasonable patches from the maintainers of +secondary or candidate primary package managers must be applied, given that +these patches are as independent of that package manager as possible.

The primary package manager is maintained on official Gentoo infrastructure, under control of Gentoo developers.

@@ -218,7 +227,7 @@

The second kind is formed by those package managers that maintain their own package database, or a package database incompatible with the primary package manager. To ensure the secondary role of these package managers the support in -the tree for these package manager is provided along with restrictions.

+the tree for these package managers is provided along with restrictions.

The first restriction is that no packages in the tree must rely on the secondary package manager. While packages may provide a level of support (while being compatible with the primary package manager) this may not result in a @@ -267,9 +276,11 @@

Primary package manager transition phase

A candidate primary package manager can be chosen to become primary package -manager. This can only happen by council decision. This decision can only be -made when the candidate primary package manager is stable on all stable -architectures. (all architectures except experimental ones).

+manager. This can only happen by council decision. This decision can only be +made when the candidate primary package manager is stable on all stable +architectures. (all architectures except experimental ones). There is a +incubation period of at least 3 months before a candidate primary package +manager can become the primary package manager.

After the decision has been made to replace the primary package manager, the transition phase starts. The use of the old stable package manager must remain supported for a period of 6 months. This means that core packages must be @@ -329,7 +340,7 @@