/[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.2 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">2215</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-20 16:18:10 +0200 (Sat, 20 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>
141<div class="section"> 141<div class="section">
142<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>
143<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
144requirements 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
145the 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
146is 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>
147<div class="section"> 150<div class="section">
148<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>
149<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
150the 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
151manager. 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
152maintain 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>
153<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
154very stable. The primary package manager must maintain compatibility with old 159very stable. The primary package manager must maintain compatibility with old
155versions of itself for extended periods of time. This compatibility time is set 160versions of itself for extended periods of time. This compatibility time is set
156by 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
157is a compatible stable version for all supported architectures.</p> 162is a compatible stable version for all supported architectures.</p>
160unstable 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
161done 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
162having 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
163tool 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
164is 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>
165<p>The primary package manager is maintained on official Gentoo infrastructure, 174<p>The primary package manager is maintained on official Gentoo infrastructure,
166under control of Gentoo developers.</p> 175under control of Gentoo developers.</p>
167</div> 176</div>
168<div class="section"> 177<div class="section">
169<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>
216remain compatible with the primary package managers. Verification, reference, 225remain compatible with the primary package managers. Verification, reference,
217and deinstallation by the primary package manager must remain functional.</p> 226and deinstallation by the primary package manager must remain functional.</p>
218<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
219package database, or a package database incompatible with the primary package 228package database, or a package database incompatible with the primary package
220manager. 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
221the tree for these package manager is provided along with restrictions.</p> 230the tree for these package managers is provided along with restrictions.</p>
222<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
223package manager. While packages may provide a level of support (while being 232package manager. While packages may provide a level of support (while being
224compatible with the primary package manager) this may not result in a 233compatible with the primary package manager) this may not result in a
225significant increase of features. If this were allowed, this would mean that 234significant increase of features. If this were allowed, this would mean that
226while they technically work with the primary package manager, there would be 235while they technically work with the primary package manager, there would be
265<div class="section"> 274<div class="section">
266<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>
267<div class="section"> 276<div class="section">
268<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>
269<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
270manager. 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
271made when the candidate primary package manager is stable on all stable 280made when the candidate primary package manager is stable on all stable
272architectures. (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>
273<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
274transition 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
275supported 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
276installable by this package manager. Further the possibility to convert the 287installable by this package manager. Further the possibility to convert the
277system 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
327 338
328</div> 339</div>
329<div class="footer"> 340<div class="footer">
330<hr class="footer" /> 341<hr class="footer" />
331<a class="reference" href="glep-0049.txt">View document source</a>. 342<a class="reference" href="glep-0049.txt">View document source</a>.
332Generated on: 2006-05-20 14:20 UTC. 343Generated on: 2006-05-21 10:23 UTC.
333Generated 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.
334 345
335</div> 346</div>
336</body> 347</body>
337</html> 348</html>

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

  ViewVC Help
Powered by ViewVC 1.1.20