/[gentoo]/xml/htdocs/proj/en/glep/glep-0049.html
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0049.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.3
… …
30<tbody valign="top"> 30<tbody valign="top">
31<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">49</td> 31<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">49</td>
32</tr> 32</tr>
33<tr class="field"><th class="field-name">Title:</th><td class="field-body">Alternative Package Manager requirements</td> 33<tr class="field"><th class="field-name">Title:</th><td class="field-body">Alternative Package Manager requirements</td>
34</tr> 34</tr>
35<tr class="field"><th class="field-name">Version:</th><td class="field-body">2213</td> 35<tr class="field"><th class="field-name">Version:</th><td class="field-body">2218</td>
36</tr> 36</tr>
37<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0049.txt?cvsroot=gentoo">2006-05-19 12:58:14 +0200 (Fri, 19 May 2006)</a></td> 37<tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0049.txt?cvsroot=gentoo">2006-05-20 20:39:14 +0200 (Sat, 20 May 2006)</a></td>
38</tr> 38</tr>
39<tr class="field"><th class="field-name">Author:</th><td class="field-body">Paul de Vrieze &lt;pauldv&#32;&#97;t&#32;gentoo.org&gt;,</td> 39<tr class="field"><th class="field-name">Author:</th><td class="field-body">Paul de Vrieze &lt;pauldv&#32;&#97;t&#32;gentoo.org&gt;,</td>
40</tr> 40</tr>
41<tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td> 41<tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td>
42</tr> 42</tr>
… …
44</tr> 44</tr>
45<tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0002.html">text/x-rst</a></td> 45<tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0002.html">text/x-rst</a></td>
46</tr> 46</tr>
47<tr class="field"><th class="field-name">Created:</th><td class="field-body">18-May-2006</td> 47<tr class="field"><th class="field-name">Created:</th><td class="field-body">18-May-2006</td>
48</tr> 48</tr>
49<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">20-May-2006</td> 49<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">19-May-2006</td>
50</tr> 50</tr>
51</tbody> 51</tbody>
52</table> 52</table>
53<hr /> 53<hr />
54<div class="contents topic"> 54<div class="contents topic">
… …
58<li><a class="reference" href="#motivation" id="id8" name="id8">Motivation</a></li> 58<li><a class="reference" href="#motivation" id="id8" name="id8">Motivation</a></li>
59<li><a class="reference" href="#rationale" id="id9" name="id9">Rationale</a></li> 59<li><a class="reference" href="#rationale" id="id9" name="id9">Rationale</a></li>
60<li><a class="reference" href="#backwards-compatibility" id="id10" name="id10">Backwards Compatibility</a></li> 60<li><a class="reference" href="#backwards-compatibility" id="id10" name="id10">Backwards Compatibility</a></li>
61<li><a class="reference" href="#categories-of-package-managers" id="id11" name="id11">Categories of package managers</a></li> 61<li><a class="reference" href="#categories-of-package-managers" id="id11" name="id11">Categories of package managers</a></li>
62<li><a class="reference" href="#package-manager-requirements" id="id12" name="id12">Package manager requirements</a><ul> 62<li><a class="reference" href="#package-manager-requirements" id="id12" name="id12">Package manager requirements</a><ul>
63<li><a class="reference" href="#primary-package-manager-requirements" id="id13" name="id13">primary package manager requirements</a></li> 63<li><a class="reference" href="#primary-package-manager-requirements" id="id13" name="id13">Primary package manager requirements</a></li>
64<li><a class="reference" href="#candidate-primary-package-manager-requirements" id="id14" name="id14">candidate primary package manager requirements</a></li> 64<li><a class="reference" href="#candidate-primary-package-manager-requirements" id="id14" name="id14">Candidate primary package manager requirements</a></li>
65<li><a class="reference" href="#secondary-package-manager-requirements" id="id15" name="id15">secondary package manager requirements</a></li> 65<li><a class="reference" href="#secondary-package-manager-requirements" id="id15" name="id15">Secondary package manager requirements</a></li>
66<li><a class="reference" href="#third-party-package-manager-requirements" id="id16" name="id16">third party package manager requirements</a></li> 66<li><a class="reference" href="#third-party-package-manager-requirements" id="id16" name="id16">Third party package manager requirements</a></li>
67</ul> 67</ul>
68</li> 68</li>
69<li><a class="reference" href="#transition-phases" id="id17" name="id17">transition phases</a><ul> 69<li><a class="reference" href="#transition-phases" id="id17" name="id17">Transition phases</a><ul>
70<li><a class="reference" href="#primary-package-manager-transition-phase" id="id18" name="id18">primary package manager transition phase</a></li> 70<li><a class="reference" href="#primary-package-manager-transition-phase" id="id18" name="id18">Primary package manager transition phase</a></li>
71<li><a class="reference" href="#secondary-package-manager-to-candidate-primary-package-manager-transition" id="id19" name="id19">Secondary package manager to candidate primary package manager transition</a></li> 71<li><a class="reference" href="#secondary-package-manager-to-candidate-primary-package-manager-transition" id="id19" name="id19">Secondary package manager to candidate primary package manager transition</a></li>
72<li><a class="reference" href="#third-party-to-other-transition" id="id20" name="id20">Third party to other transition</a></li> 72<li><a class="reference" href="#third-party-to-other-transition" id="id20" name="id20">Third party to other transition</a></li>
73</ul> 73</ul>
74</li> 74</li>
75<li><a class="reference" href="#references" id="id21" name="id21">References</a></li> 75<li><a class="reference" href="#references" id="id21" name="id21">References</a></li>
… …
81<p>This GLEP describes four classes of package managers. What the requirements for 81<p>This GLEP describes four classes of package managers. What the requirements for
82them are, and what support they can receive.</p> 82them are, and what support they can receive.</p>
83</div> 83</div>
84<div class="section"> 84<div class="section">
85<h1><a class="toc-backref" href="#id8" id="motivation" name="motivation">Motivation</a></h1> 85<h1><a class="toc-backref" href="#id8" id="motivation" name="motivation">Motivation</a></h1>
86<p>To set a standard that package managers that seek gentoo project approval and 86<p>To set a standard that package managers that seek Gentoo project approval and
87support should adhere to.</p> 87support should adhere to.</p>
88</div> 88</div>
89<div class="section"> 89<div class="section">
90<h1><a class="toc-backref" href="#id9" id="rationale" name="rationale">Rationale</a></h1> 90<h1><a class="toc-backref" href="#id9" id="rationale" name="rationale">Rationale</a></h1>
91<p>Currently portage is showing its age. The code of portage does not seem to be 91<p>Currently Portage is showing its age. The code of Portage does not seem to be
92salvageable for new versions. There are two known alternative package managers 92salvageable for new versions. As of the date of publication, there are two known
93that claim a level of portage compatibility. These alternatives are <a class="reference" href="http://paludis.berlios.de/">paludis</a> <a class="footnote-reference" href="#id1" id="id2" name="id2">[1]</a> 93alternative package managers that claim a level of Portage compatibility. These
94and <a class="reference" href="http://gentooexperimental.org/~ferringb/bzr/pkgcore/">pkgcore</a> <a class="footnote-reference" href="#id3" id="id4" name="id4">[2]</a>. Before these alternatives are developed further, a set of rules 94alternatives are <a class="reference" href="http://paludis.berlios.de/">paludis</a> <a class="footnote-reference" href="#id1" id="id2" name="id2">[1]</a> and <a class="reference" href="http://gentooexperimental.org/~ferringb/bzr/pkgcore/">pkgcore</a> <a class="footnote-reference" href="#id3" id="id4" name="id4">[2]</a>. Before these alternatives are
95should be created to level the playing field and ensuring that decisions can be 95developed further, a set of rules should be created to level the playing field
96made clearly.</p> 96and ensuring that decisions can be made clearly.</p>
97</div> 97</div>
98<div class="section"> 98<div class="section">
99<h1><a class="toc-backref" href="#id10" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1> 99<h1><a class="toc-backref" href="#id10" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1>
100<p>Not a problem for this GLEP. There is no previous standard as the issue did not 100<p>Not a problem for this GLEP. There is no previous standard as the issue did not
101exist before. This GLEP is to prevent future compatibility issues.</p> 101exist before. This GLEP is to prevent future compatibility issues.</p>
… …
106transition from one category to another, it can not be in two categories at the 106transition from one category to another, it can not be in two categories at the
107same time. It can be in a state of transition though.</p> 107same time. It can be in a state of transition though.</p>
108<dl class="docutils"> 108<dl class="docutils">
109<dt><em>Primary Package Manager</em></dt> 109<dt><em>Primary Package Manager</em></dt>
110<dd>There is one primary package manager. Currently this position is held by 110<dd>There is one primary package manager. Currently this position is held by
111portage. The primary package manager is assigned by the council and all 111Portage. The primary package manager is assigned by the council and all
112packages in the official tree must be installable by a useable version of the 112packages in the official tree must be installable by a usable version of the
113primary package manager.</dd> 113primary package manager.</dd>
114<dt><em>Candidate Primary Package Managers</em></dt> 114<dt><em>Candidate Primary Package Managers</em></dt>
115<dd>A candidate Primary Package Manager does aim, or show an aim, at replacing 115<dd>A candidate Primary Package Manager does aim, or show an aim, at replacing
116the current primary package manager. At a point where the package manager is 116the current primary package manager. At a point where the package manager is
117deemed stable a decision must be made whether this package manager should 117deemed stable a decision must be made whether this package manager should
118become the new primary package manager. At that point the <a class="reference" href="#primary-package-manager-transition-phase">primary package 118become the new primary package manager. At that point the <a class="reference" href="#primary-package-manager-transition-phase">Primary package
119manager transition phase</a> starts.</dd> 119manager transition phase</a> starts.</dd>
120<dt><em>Secondary Package Managers</em></dt> 120<dt><em>Secondary Package Managers</em></dt>
121<dd><p class="first">A secondary package manager is a package manager that coexists with the 121<dd><p class="first">A secondary package manager is a package manager that coexists with the
122primary package manager, while not aiming to replace it. Package managers 122primary package manager, while not aiming to replace it. Examples of package
123that would fall into this category are:</p> 123managers that would fall into this category are:</p>
124<ul class="last simple"> 124<ul class="last simple">
125<li>Experimental package managers. Package managers whose purpose it is to try 125<li>Experimental package managers. Package managers whose purpose it is to try
126out new features.</li> 126out new features.</li>
127<li>Focussed package managers. For example a package manager that allows the 127<li>Focused package managers. For example a package manager that allows the
128use of rpm formatted binary packages would be an example.</li> 128use of RPM formatted binary packages would be an example.</li>
129<li>Alternate package managers. Package managers that aim to coexist with the
130primary package manager. They might for example offer a nicer user
131interface than the primary package manager (e.g. show a cow instead of
132compilation messages).</li>
129</ul> 133</ul>
130</dd> 134</dd>
131<dt><em>Third Party Package Managers</em></dt> 135<dt><em>Third Party Package Managers</em></dt>
132<dd>A third party package manager is any package manager that lacks recognition 136<dd>A third party package manager is any package manager that lacks recognition
133from gentoo as being in any other category. A third party package manager may 137from Gentoo as being in any other category. A third party package manager may
134or may not have a gentoo package, but is not supported beyond that.</dd> 138or may not have a Gentoo package, but is not supported beyond that.</dd>
135</dl> 139</dl>
136</div> 140</div>
137<div class="section"> 141<div class="section">
138<h1><a class="toc-backref" href="#id12" id="package-manager-requirements" name="package-manager-requirements">Package manager requirements</a></h1> 142<h1><a class="toc-backref" href="#id12" id="package-manager-requirements" name="package-manager-requirements">Package manager requirements</a></h1>
139<p>As a package manager is in a state of higher support there are higher 143<p>As a package manager is in a state of higher support there are higher
140requirements to it. The purpose of these requirements is to ensure the unity of 144requirements to it. The purpose of these requirements is to ensure the unity of
141the distribution and the package tree. For this purpose it is needed that there 145the distribution and the package tree. For this purpose it is needed that there
142is only one primary package manager.</p> 146is only one primary package manager. This is from gentoo's perspective. From a
147user perspective it is perfectly possible to use another package
148manager. Candidate primary package managers and secondary package managers are
149also supported in regards to bugs etc.</p>
143<div class="section"> 150<div class="section">
144<h2><a class="toc-backref" href="#id13" id="primary-package-manager-requirements" name="primary-package-manager-requirements">primary package manager requirements</a></h2> 151<h2><a class="toc-backref" href="#id13" id="primary-package-manager-requirements" name="primary-package-manager-requirements">Primary package manager requirements</a></h2>
145<p>The primary package manager is the package manager that sets the standards for 152<p>The primary package manager is the package manager that sets the standards for
146the tree. All ebuilds in the tree must function with the primary package 153the tree. All ebuilds in the tree must function with the primary package
147manager. As the primary package manager sets the standard it does not have to 154manager. As the primary package manager sets the standard it does not have to
148maintain compatibility with other package managers.</p> 155maintain compatibility with other package managers. This does not mean that the
156actual implementation is the standard, but that the maintainers have the ability
157to define new standards, together with the other involved gentoo projects.</p>
149<p>The primary package manager does however have the responsibility that it must be 158<p>The primary package manager does however have the responsibility that it must be
150very stable. The primary package manager must maintain compatibility with old 159very stable. The primary package manager must maintain compatibility with old
151versions of itself for extended periods of time. This compatibilty time is set 160versions of itself for extended periods of time. This compatibility time is set
152by the council. The suggested time would be one year from the point that there 161by the council. The suggested time would be one year from the point that there
153is a compatible stable version for all supported architectures.</p> 162is a compatible stable version for all supported architectures.</p>
154<p>Another compatibilty requirement for the primary package manager is a limited 163<p>Another compatibility requirement for the primary package manager is a limited
155forward compatibility. It must always be possible to transition from the 164forward compatibility. It must always be possible to transition from the
156unstable version of the primary package manager to a stable version. This may be 165unstable version of the primary package manager to a stable version. This may be
157done either by first introducing reading compatibility for a new format and only 166done either by first introducing reading compatibility for a new format and only
158having write support later. Another way would be the provision of a conversion 167having write support later. Another way would be the provision of a conversion
159tool that ensures that the on disk information maintained by the package manager 168tool that ensures that the on disk information maintained by the package manager
160is supported by the stable package manager.</p> 169is supported by the stable package manager.</p>
170<p>The primary package manager maintainers further have the responsibility to allow
171competition. This means that reasonable patches from the maintainers of
172secondary or candidate primary package managers must be applied, given that
173these patches are as independent of that package manager as possible.</p>
161<p>The primary package manager is maintained on official gentoo infrastructure, 174<p>The primary package manager is maintained on official Gentoo infrastructure,
162under control of gentoo developers.</p> 175under control of Gentoo developers.</p>
163</div> 176</div>
164<div class="section"> 177<div class="section">
165<h2><a class="toc-backref" href="#id14" id="candidate-primary-package-manager-requirements" name="candidate-primary-package-manager-requirements">candidate primary package manager requirements</a></h2> 178<h2><a class="toc-backref" href="#id14" id="candidate-primary-package-manager-requirements" name="candidate-primary-package-manager-requirements">Candidate primary package manager requirements</a></h2>
166<p>A candidate primary package manager aims to replace the primary package 179<p>A candidate primary package manager aims to replace the primary package
167manager. The council is responsible for deciding whether this is done. The 180manager. The council is responsible for deciding whether this is done. The
168requirements are there to ensure that it is actually possible to transition a 181requirements are there to ensure that it is actually possible to transition a
169candidate primary package manager into the primary package manager.</p> 182candidate primary package manager into the primary package manager.</p>
170<p>First of all, there must exist a transition path. This means that the on disk 183<p>First of all, there must exist a transition path. This means that the on disk
171data of the primary package manager can be used by (or converted to a format 184data of the primary package manager can be used by (or converted to a format
172usable by) the candidate primary package manager.</p> 185usable by) the candidate primary package manager.</p>
173<p>Second, there must be a test path. It must be possible for the developers to 186<p>Second, there must be a test path. It must be possible for the developers to
174test out the candidate primary package manager on their working systems. This 187test out the candidate primary package manager on their working systems. This
175means that the transition path must exist. This also means that there are no 188means that the transition path must exist. This also means that there are no
176serious obstacles for reverting to the current primary package manager.</p> 189serious obstacles for reverting to the current primary package manager. This
190reverting must also be usable when it is decided that the candidate will not
191become primary package manager, for example because serious design flaws or bugs
192were found. Ideally, the Candidate Primary Package Manager and the Primary
193Package Manager can be installed simultaneously. If not, clear instructions must
194be provided for both ways of transitioning.</p>
177<p>Third, there must exist an ebuild test path. It must be possible for package 195<p>Third, there must exist an ebuild test path. It must be possible for package
178managers to test ebuilds in one tree for both the primary as well as the 196managers to test ebuilds in one tree for both the primary as well as the
179candidate primary package manager. It is not an issue if this requires a special 197candidate primary package manager. It is not an issue if this requires a special
180mode for the candidate primary package manager. It is not an issue either if 198mode for the candidate primary package manager. It is not an issue either if
181compatibilty can be achieved by unmerging the package in the candidate primary 199compatibility can be achieved by having the candidate primary package manager
182package manager.</p> 200unmerge the package.</p>
183<p>Fourth, there must be support. This means that the package manager is actively 201<p>Fourth, there must be support. This means that the package manager is actively
184maintained under control of gentoo. If it is not maintained on gentoo 202maintained under control of Gentoo. If it is not maintained on Gentoo
185infrastructure, the means must be there to move the package manager, with its 203infrastructure, the means must be there to move the package manager, with its
186change history, to gentoo infrastructure. This means that it must be maintained 204change history, to Gentoo infrastructure. This means that it must be maintained
187on a gentoo supported versioning system, or on a version system whose history 205on a Gentoo supported versioning system, or on a version system whose history
188can be converted to a gentoo supported versioning system.</p> 206can be converted to a Gentoo supported versioning system.</p>
207<p>Fifth, release capabilities. There must exist automated tools that use the
208candidate primary package manager to create release media that have similar
209capabilities as those released using the old primary package manager. The exact
210requirements are determined by the Release Engineering project, but should not
211be significantly beyond what is currently implemented using the primary package
212manager.</p>
189</div> 213</div>
190<div class="section"> 214<div class="section">
191<h2><a class="toc-backref" href="#id15" id="secondary-package-manager-requirements" name="secondary-package-manager-requirements">secondary package manager requirements</a></h2> 215<h2><a class="toc-backref" href="#id15" id="secondary-package-manager-requirements" name="secondary-package-manager-requirements">Secondary package manager requirements</a></h2>
192<p>A secondary package manager is a package manager that instead of directly aiming 216<p>A secondary package manager is a package manager that instead of directly aiming
217at replacing the current primary package manager as primary package manager aims
193at replacing portage as primary package manager. As such a secondary package 218to cooperate with the primary package manager. As such a secondary package
194manager does not set the standard on the tree, but follows the standard set by 219manager does not set the standard on the tree, but follows the standard set by
195the primary package manager.</p> 220the primary package manager.</p>
196<p>There are two kinds of secondary package managers. The first kind is formed by 221<p>There are two kinds of secondary package managers. The first kind is formed by
197those that do not maintain their own installed package database, but work with 222those that do not maintain their own installed package database, but work with
198the package database of the primary package manager. While these package 223the package database of the primary package manager. While these package
… …
200remain compatible with the primary package managers. Verification, reference, 225remain compatible with the primary package managers. Verification, reference,
201and deinstallation by the primary package manager must remain functional.</p> 226and deinstallation by the primary package manager must remain functional.</p>
202<p>The second kind is formed by those package managers that maintain their own 227<p>The second kind is formed by those package managers that maintain their own
203package database, or a package database incompatible with the primary package 228package database, or a package database incompatible with the primary package
204manager. To ensure the secondary role of these package managers the support in 229manager. To ensure the secondary role of these package managers the support in
205the tree for these package manager is provided along with restrictions.</p> 230the tree for these package managers is provided along with restrictions.</p>
206<p>The first restriction is that no packages in the tree must rely on the secondary 231<p>The first restriction is that no packages in the tree must rely on the secondary
207package manager. While packages may provide a level of support (while being 232package manager. While packages may provide a level of support (while being
208compatible with the primary package manager) this may not result in a 233compatible with the primary package manager) this may not result in a
209significant increase of features. If this were allowed, this would mean that 234significant increase of features. If this were allowed, this would mean that
210while they technically work with the primary package manager, there would be 235while they technically work with the primary package manager, there would be
211significant incentive to use the secondary package manager. As the use of this 236significant incentive to use the secondary package manager. As the use of this
212secondary package manager disallows the paralel use of the primary package 237secondary package manager disallows the parallel use of the primary package
213manager, this would result in users using the secondary package manager as their 238manager, this would result in users using the secondary package manager as their
214primary package manager.</p> 239primary package manager.</p>
215<p>Users are allowed to make their own choices. However by making the tree favor a 240<p>Users are allowed to make their own choices. However by making the tree favour a
216package manager that is not the primary package manager, this will lead to the 241package manager that is not the primary package manager, this will lead to the
217secondary package manager becomming the effective primary package manager. As 242secondary package manager becoming the effective primary package manager. As
218this will be a decision by default instead of a concious choice by the council, 243this will be a decision by default instead of a conscious choice by the council,
219this is an undesirable result.</p> 244this is an undesirable result.</p>
220<p>There is one exclusion for the restriction of packages that only work with or 245<p>There is one exclusion for the restriction of packages that only work with or
221have significant improvements with the secondary package manager. That is 246have significant improvements with the secondary package manager. That is
222packages that by their nature are only usable with this secondary package 247packages that by their nature are only usable with this secondary package
223manager. An example would be a graphical frontend to the secondary package 248manager. An example would be a graphical front-end to the secondary package
224manager.</p> 249manager.</p>
225<p>If a secondary package manager works along the primary package manager, but by 250<p>If a secondary package manager works along the primary package manager, but by
226itself does not have the capabilities of becoming a primary package manager the 251itself does not have the capabilities of becoming a primary package manager the
227risks of choice by default are lower. As a result, the council could choose to 252risks of choice by default are lower. As a result, the council could choose to
228allow the inclusion of packages that work only or significantly better with this 253allow the inclusion of packages that work only or significantly better with this
… …
232wrapper scripts for those packages that are only provided in the RPM 257wrapper scripts for those packages that are only provided in the RPM
233format. Such a decision does imply that the maintainers of the primary package 258format. Such a decision does imply that the maintainers of the primary package
234manager must take this secondary package manager into account.</p> 259manager must take this secondary package manager into account.</p>
235</div> 260</div>
236<div class="section"> 261<div class="section">
237<h2><a class="toc-backref" href="#id16" id="third-party-package-manager-requirements" name="third-party-package-manager-requirements">third party package manager requirements</a></h2> 262<h2><a class="toc-backref" href="#id16" id="third-party-package-manager-requirements" name="third-party-package-manager-requirements">Third party package manager requirements</a></h2>
238<p>A third party package manager is just that. It is a package manager without any 263<p>A third party package manager is just that. It is a package manager without any
239support within gentoo. As there is no control by gentoo over the package manager 264support within Gentoo. As there is no control by Gentoo over the package manager
240this means that there are no requirements on the package manager.</p> 265this means that there are no requirements on the package manager.</p>
241<p>This complete lack of control however also translates to the fact that gentoo 266<p>This complete lack of control however also translates to the fact that Gentoo
242can not make package manager specific changes to support this package 267can not make package manager specific changes to support this package
243manager. Package manager specific means that it is possible to request changes 268manager. Package manager specific means that it is possible to request changes
244that make the tree more independent of the primary package manager. These 269that make the tree more independent of the primary package manager. These
245changes must however be agnostic of the package manager, and only make it easier 270changes must however be agnostic of the package manager, and only make it easier
246to have alternative package managers.</p> 271to have alternative package managers.</p>
247</div> 272</div>
248</div> 273</div>
249<div class="section"> 274<div class="section">
250<h1><a class="toc-backref" href="#id17" id="transition-phases" name="transition-phases">transition phases</a></h1> 275<h1><a class="toc-backref" href="#id17" id="transition-phases" name="transition-phases">Transition phases</a></h1>
251<div class="section"> 276<div class="section">
252<h2><a class="toc-backref" href="#id18" id="primary-package-manager-transition-phase" name="primary-package-manager-transition-phase">primary package manager transition phase</a></h2> 277<h2><a class="toc-backref" href="#id18" id="primary-package-manager-transition-phase" name="primary-package-manager-transition-phase">Primary package manager transition phase</a></h2>
253<p>A candidate primary package manager can be chosen to become primary package 278<p>A candidate primary package manager can be chosen to become primary package
254manager. This can only happen by council decision. This decision can only be 279manager. This can only happen by council decision. This decision can only be
255made when the candiate primary package manager is stable on all stable 280made when the candidate primary package manager is stable on all stable
256architectures. (all architectures except experimental ones).</p> 281architectures. (all architectures except experimental ones). There is a
282incubation period of at least 3 months before a candidate primary package
283manager can become the primary package manager.</p>
257<p>After the decision has been made to replace the primary package manager, the 284<p>After the decision has been made to replace the primary package manager, the
258transition phase starts. The use of the old stable package manager must remain 285transition phase starts. The use of the old stable package manager must remain
259supported for a period of 6 months. This means that core packages must be 286supported for a period of 6 months. This means that core packages must be
260installable by this package manager. Further the possibility to convert the 287installable by this package manager. Further the possibility to convert the
261system automatically to the new primary package manager must be available for at 288system automatically to the new primary package manager must be available for at
… …
270<h2><a class="toc-backref" href="#id19" id="secondary-package-manager-to-candidate-primary-package-manager-transition" name="secondary-package-manager-to-candidate-primary-package-manager-transition">Secondary package manager to candidate primary package manager transition</a></h2> 297<h2><a class="toc-backref" href="#id19" id="secondary-package-manager-to-candidate-primary-package-manager-transition" name="secondary-package-manager-to-candidate-primary-package-manager-transition">Secondary package manager to candidate primary package manager transition</a></h2>
271<p>The transition from secondary package manager to candidate primary package 298<p>The transition from secondary package manager to candidate primary package
272manager is straightforward. The secondary package manager must satisfy all 299manager is straightforward. The secondary package manager must satisfy all
273requirements for a candidate primary package manager. At that point its 300requirements for a candidate primary package manager. At that point its
274maintainers can announce that they are changing the status to candidate primary 301maintainers can announce that they are changing the status to candidate primary
275package manager. This allows a greater support from gentoo in achieving that 302package manager. This allows a greater support from Gentoo in achieving that
276goal.</p> 303goal.</p>
277</div> 304</div>
278<div class="section"> 305<div class="section">
279<h2><a class="toc-backref" href="#id20" id="third-party-to-other-transition" name="third-party-to-other-transition">Third party to other transition</a></h2> 306<h2><a class="toc-backref" href="#id20" id="third-party-to-other-transition" name="third-party-to-other-transition">Third party to other transition</a></h2>
280<p>When a third party package manager wants to transition into one of the other 307<p>When a third party package manager wants to transition into one of the other
… …
311 338
312</div> 339</div>
313<div class="footer"> 340<div class="footer">
314<hr class="footer" /> 341<hr class="footer" />
315<a class="reference" href="glep-0049.txt">View document source</a>. 342<a class="reference" href="glep-0049.txt">View document source</a>.
316Generated on: 2006-05-20 12:50 UTC. 343Generated on: 2006-05-21 10:23 UTC.
317Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 344Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
318 345
319</div> 346</div>
320</body> 347</body>
321</html> 348</html>
Legend:
Removed from v.1.1  
changed lines
  Added in v.1.3
  ViewVC Help
Powered by ViewVC 1.1.13