Contents of /xml/htdocs/proj/en/glep/glep-0040.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.2 - (hide annotations) (download) (as text)
Thu Sep 15 21:04:13 2005 UTC (13 years, 3 months ago) by g2boojum
Branch: MAIN
Changes since 1.1: +34 -29 lines
File MIME type: text/html

1 g2boojum 1.1 <?xml version="1.0" encoding="utf-8" ?>
2     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3     <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4     <!--
5     This HTML is auto-generated. DO NOT EDIT THIS FILE! If you are writing a new
6     PEP, see http://www.python.org/peps/pep-0001.html for instructions and links
8     -->
9     <head>
10     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
11     <meta name="generator" content="Docutils 0.3.9: http://docutils.sourceforge.net/" />
12     <title>GLEP 40 -- Standardizing "arch" keywording across all archs.</title>
13     <link rel="stylesheet" href="tools/glep.css" type="text/css" />
14     </head>
15     <body bgcolor="white">
16     <table class="navigation" cellpadding="0" cellspacing="0"
17     width="100%" border="0">
18     <tr><td class="navicon" width="150" height="35">
19     <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
20     <img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
21     border="0" width="150" height="35" /></a></td>
22     <td class="textlinks" align="left">
23     [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
24     [<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>]
25     [<b><a href="./glep-0040.txt">GLEP Source</a></b>]
26     </td></tr></table>
27     <table class="rfc2822 docutils field-list" frame="void" rules="none">
28     <col class="field-name" />
29     <col class="field-body" />
30     <tbody valign="top">
31     <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">40</td>
32     </tr>
33     <tr class="field"><th class="field-name">Title:</th><td class="field-body">Standardizing &quot;arch&quot; keywording across all archs.</td>
34     </tr>
35 g2boojum 1.2 <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.2</td>
36 g2boojum 1.1 </tr>
37 g2boojum 1.2 <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/xml/htdocs/proj/en/glep/glep-0040.txt?cvsroot=gentoo">2005/09/15 21:02:11</a></td>
38 g2boojum 1.1 </tr>
39     <tr class="field"><th class="field-name">Author:</th><td class="field-body">Grant Goodyear &lt;g2boojum&#32;&#97;t&#32;gentoo.org&gt;</td>
40     </tr>
41 g2boojum 1.2 <tr class="field"><th class="field-name">Status:</th><td class="field-body">Approved</td>
42 g2boojum 1.1 </tr>
43     <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
44     </tr>
45     <tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="http://www.python.org/peps/glep-0012.html">text/x-rst</a></td>
46     </tr>
47     <tr class="field"><th class="field-name">Created:</th><td class="field-body">3-Sep-2005</td>
48     </tr>
49 g2boojum 1.2 <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">6-Sep-2005 15-Sep-2005</td>
50 g2boojum 1.1 </tr>
51     </tbody>
52     </table>
53     <hr />
54     <div class="contents topic" id="contents">
55     <p class="topic-title first"><a name="contents">Contents</a></p>
56     <ul class="simple">
57 g2boojum 1.2 <li><a class="reference" href="#status" id="id10" name="id10">Status</a></li>
58     <li><a class="reference" href="#credits" id="id11" name="id11">Credits</a></li>
59     <li><a class="reference" href="#abstract" id="id12" name="id12">Abstract</a></li>
60     <li><a class="reference" href="#motivation" id="id13" name="id13">Motivation</a></li>
61     <li><a class="reference" href="#specification" id="id14" name="id14">Specification</a><ul>
62     <li><a class="reference" href="#stabling-guidelines-for-all-archs" id="id15" name="id15">Stabling guidelines for all archs</a></li>
63     <li><a class="reference" href="#x86-arch-team" id="id16" name="id16">x86 arch team</a></li>
64 g2boojum 1.1 </ul>
65     </li>
66 g2boojum 1.2 <li><a class="reference" href="#rationale" id="id17" name="id17">Rationale</a></li>
67     <li><a class="reference" href="#implementation" id="id18" name="id18">Implementation</a></li>
68     <li><a class="reference" href="#alternative-ideas" id="id19" name="id19">Alternative Ideas</a></li>
69     <li><a class="reference" href="#backwards-compatibility" id="id20" name="id20">Backwards Compatibility</a></li>
70     <li><a class="reference" href="#id1" id="id21" name="id21">References</a></li>
71     <li><a class="reference" href="#copyright" id="id22" name="id22">Copyright</a></li>
72 g2boojum 1.1 </ul>
73     </div>
74 g2boojum 1.2 <div class="section" id="status">
75     <h1><a class="toc-backref" href="#id10" name="status">Status</a></h1>
76     <p>Approved by the Gentoo Council on 15 September 2005.</p>
77     </div>
78 g2boojum 1.1 <div class="section" id="credits">
79 g2boojum 1.2 <h1><a class="toc-backref" href="#id11" name="credits">Credits</a></h1>
80 g2boojum 1.1 <p>This GLEP originated from a rather contentious <a class="reference" href="http://tinyurl.com/bp859">discussion</a> <a class="footnote-reference" href="#id2" id="id3" name="id3">[1]</a> on gentoo-dev
81     about combining the x86 and amd64 keywords. This GLEP attempts to get at the
82     heart of that discontent. The proposed stable-keyword guidelines have been
83     lifted verbatim from <a class="reference" href="http://dev.gentoo.org/~plasmaroo/devmanual">The Doc</a> <a class="footnote-reference" href="#id4" id="id5" name="id5">[2]</a>.</p>
84     </div>
85     <div class="section" id="abstract">
86 g2boojum 1.2 <h1><a class="toc-backref" href="#id12" name="abstract">Abstract</a></h1>
87 g2boojum 1.1 <p>It is time for x86 to no longer be an exception to the standard
88     keywording guidelines. Thus, an x86 arch team should be responsible
89     for moving packages from ~x86 to x86.</p>
90     </div>
91     <div class="section" id="motivation">
92 g2boojum 1.2 <h1><a class="toc-backref" href="#id13" name="motivation">Motivation</a></h1>
93 g2boojum 1.1 <p>The original, informal x86 keywording policy, where almost any x86 dev (which
94     were the vast majority of devs) who used a package could mark it stable, arose
95     from a time when there were relatively few Gentoo devs. Adding packages to
96     the tree was the principal concern, as opposed to maintaining existing
97     packages. QA considerations have since modified that policy slightly, and now
98     it is the package maintainers who should mark an x86 package stable. Of
99     course, that policy presumes that package maintainers are generally x86 devs,
100     which is slowly becoming less and less true.</p>
101     <p>This policy for x86 is quite different from how every other arch marks
102     packages stable. For the non-x86 archs, each arch has a specific &quot;arch team&quot;
103     which is responsible for moving packages from <tt class="docutils literal"><span class="pre">~arch</span></tt> to <tt class="docutils literal"><span class="pre">arch</span></tt>, although
104     vapier notes that &quot;arch teams generally defer to maintainers (and rightly so)
105     as to <em>when</em> newer versions should go stable.&quot; This approach has worked quite
106     well for the non-x86 archs, and this GLEP asserts that the same approach would
107     benefit x86 as well.</p>
108     </div>
109     <div class="section" id="specification">
110 g2boojum 1.2 <h1><a class="toc-backref" href="#id14" name="specification">Specification</a></h1>
111 g2boojum 1.1 <div class="section" id="stabling-guidelines-for-all-archs">
112 g2boojum 1.2 <h2><a class="toc-backref" href="#id15" name="stabling-guidelines-for-all-archs">Stabling guidelines for all archs</a></h2>
113 g2boojum 1.1 <p>For a package to move to stable, the following guidelines must be met:</p>
114     <ul class="simple">
115     <li>The package has spent a reasonable amount of time in <tt class="docutils literal"><span class="pre">~arch</span></tt> first.
116     Thirty days is the usual figure, although this is clearly only a guideline.
117     For critical packages, a much longer duration is expected. For small
118     packages which have only minor changes between versions, a shorter period
119     is sometimes appropriate.</li>
120     <li>The package must not have any non-<tt class="docutils literal"><span class="pre">arch</span></tt> dependencies.</li>
121     <li>The package must not have any severe outstanding bugs or issues.</li>
122     <li>The package must be widely tested.</li>
123     <li>If the package is a library, it should be known not to break any package
124     which depends upon it.</li>
125     <li>The relevant <tt class="docutils literal"><span class="pre">arch</span></tt> team must agree to it.</li>
126     </ul>
127     </div>
128     <div class="section" id="x86-arch-team">
129 g2boojum 1.2 <h2><a class="toc-backref" href="#id16" name="x86-arch-team">x86 arch team</a></h2>
130 g2boojum 1.1 <p>A robust x86 arch team needs to be created. The <a class="reference" href="mailto:x86&#64;gentoo.org">x86&#64;gentoo.org</a> alias already
131     exists, and it merely needs to be used. This team, with the aid of potential
132     non-dev <tt class="docutils literal"><span class="pre">arch</span> <span class="pre">testers</span></tt>, has the responsibility of stabling all x86 packages.
133     Current x86 devs who wish to mark their own packages stable must therefore
134     either be members of or make individual arrangements with the x86 arch team.</p>
135     </div>
136     </div>
137     <div class="section" id="rationale">
138 g2boojum 1.2 <h1><a class="toc-backref" href="#id17" name="rationale">Rationale</a></h1>
139 g2boojum 1.1 <p>There will be a considerable one-time cost involved in establishing a robust
140     x86 arch team--a good number of bodies (the amd64 atch team has 19 active devs
141     and 12 active non-dev arch testers) need to be recruited to be part of the
142     new arch team, and convincing devs that it is in their best interests to work
143     in a new fashion is likely to be even harder. Certainly the benefit of
144     consistency between the various archs is obvious, but is it worth the cost
145     involved? Here are the arguments for enduring the pain involved:</p>
146     <ul class="simple">
147     <li>Over time, x86 is likely to become a minority arch as 64-bit systems
148     become the norm. The implicit assumptions that underly the current
149     system (that most devs, users, and package maintainers use x86)
150     will become increasingly less valid.</li>
151     <li>Markedly improved QA for x86. Assuming that the author's own is
152     behavior is representative, most x86 devs run <tt class="docutils literal"><span class="pre">~x86</span></tt> systems.
153     Thus, the assumption that devs are good <tt class="docutils literal"><span class="pre">x86</span></tt> testers is not really
154     valid. One obvious consequence is that packages tend to languish in
155     <tt class="docutils literal"><span class="pre">~x86</span></tt> for a very long time, since x86 devs running <tt class="docutils literal"><span class="pre">~x86</span></tt> have little
156     cause to notice that a package has not been marked stable. The much larger
157     effect, though, is that it is rare for <tt class="docutils literal"><span class="pre">x86</span></tt> packages to be stabled in
158     the context of a full <tt class="docutils literal"><span class="pre">x86</span></tt> tree, so the big picture of a stable
159     <em>system</em>, not just a stable package, is lost. This approach of stabling
160     in the context of a full stable <tt class="docutils literal"><span class="pre">arch</span></tt> tree, it has been <a class="reference" href="http://thread.gmane.org/gmane.linux.gentoo.devel/30369">argued</a> <a class="footnote-reference" href="#id6" id="id7" name="id7">[3]</a>, is
161     the fundamental reason why the non-x86 archs have notably better QA
162     than does the x86 arch.</li>
163     </ul>
164     </div>
165     <div class="section" id="implementation">
166 g2boojum 1.2 <h1><a class="toc-backref" href="#id18" name="implementation">Implementation</a></h1>
167 g2boojum 1.1 <p>Creation of a robust x86 team is already underway. The more vital step
168     is the official change in policy, along with a sustained effort to get
169     existing x86 devs to go along with it.</p>
170     </div>
171     <div class="section" id="alternative-ideas">
172 g2boojum 1.2 <h1><a class="toc-backref" href="#id19" name="alternative-ideas">Alternative Ideas</a></h1>
173 g2boojum 1.1 <p><a class="reference" href="http://thread.gmane.org/gmane.linux.gentoo.devel/31060">Stuart</a> <a class="footnote-reference" href="#id8" id="id9" name="id9">[4]</a> has suggested the creation of a new arch keyword: &quot;[-]maint&quot;, which
174     would exist in tandem with the normal arch keywords, thereby making the
175     package maintainer's intention explicit. Ciaranm has responded that by
176     definition a package in <tt class="docutils literal"><span class="pre">~arch</span></tt> is a candidate for <tt class="docutils literal"><span class="pre">arch</span></tt>, so a package's
177     mere presence in the tree (without being in <tt class="docutils literal"><span class="pre">package.mask</span></tt>) should indicate
178     the package maintainer's intention. There was a fair bit of discussion about
179     whether the idea should be a &quot;maint&quot; keyword, or named something else, or an
180     entirely different variable, etcetera, but the basic gist didn't change much.</p>
181     <p>Jstubbs notes that it could be a very good idea if all non-arch devs worked in
182     overlays, but that new portage (gensync) support would be needed to make it
183     truly viable. Stuart pointed out that php5 support was handled just that way.
184     One author's view is that this approach would make the &quot;package in <tt class="docutils literal"><span class="pre">~arch</span></tt>
185     means that it's a de-facto candidate for <tt class="docutils literal"><span class="pre">arch</span></tt>&quot; interpretation even more
186     valid.</p>
187     <p>Ciaranm and weeve have noted that it is occasionally necessary for arch teams
188     to override a package maintainer when it comes to stabling a package. Stuart
189     has asserted that in those cases the arch team should be willing to take on
190     the support burden for that package.</p>
191     </div>
192     <div class="section" id="backwards-compatibility">
193 g2boojum 1.2 <h1><a class="toc-backref" href="#id20" name="backwards-compatibility">Backwards Compatibility</a></h1>
194 g2boojum 1.1 <p>Not really an issue here.</p>
195     </div>
196     <div class="section" id="id1">
197 g2boojum 1.2 <h1><a class="toc-backref" href="#id21" name="id1">References</a></h1>
198 g2boojum 1.1 <table class="docutils footnote" frame="void" id="id2" rules="none">
199     <colgroup><col class="label" /><col /></colgroup>
200     <tbody valign="top">
201     <tr><td class="label"><a class="fn-backref" href="#id3" name="id2">[1]</a></td><td><a class="reference" href="http://tinyurl.com/bp859">http://tinyurl.com/bp859</a></td></tr>
202     </tbody>
203     </table>
204     <table class="docutils footnote" frame="void" id="id4" rules="none">
205     <colgroup><col class="label" /><col /></colgroup>
206     <tbody valign="top">
207     <tr><td class="label"><a class="fn-backref" href="#id5" name="id4">[2]</a></td><td><a class="reference" href="http://dev.gentoo.org/~plasmaroo/devmanual">http://dev.gentoo.org/~plasmaroo/devmanual</a></td></tr>
208     </tbody>
209     </table>
210     <table class="docutils footnote" frame="void" id="id6" rules="none">
211     <colgroup><col class="label" /><col /></colgroup>
212     <tbody valign="top">
213     <tr><td class="label"><a class="fn-backref" href="#id7" name="id6">[3]</a></td><td><a class="reference" href="http://thread.gmane.org/gmane.linux.gentoo.devel/30369">http://thread.gmane.org/gmane.linux.gentoo.devel/30369</a></td></tr>
214     </tbody>
215     </table>
216     <table class="docutils footnote" frame="void" id="id8" rules="none">
217     <colgroup><col class="label" /><col /></colgroup>
218     <tbody valign="top">
219     <tr><td class="label"><a class="fn-backref" href="#id9" name="id8">[4]</a></td><td><a class="reference" href="http://thread.gmane.org/gmane.linux.gentoo.devel/31060">http://thread.gmane.org/gmane.linux.gentoo.devel/31060</a></td></tr>
220     </tbody>
221     </table>
222     </div>
223     <div class="section" id="copyright">
224 g2boojum 1.2 <h1><a class="toc-backref" href="#id22" name="copyright">Copyright</a></h1>
225 g2boojum 1.1 <p>This document has been placed in the public domain.</p>
226     </div>
228     </div>
229     <div class="footer">
230     <hr class="footer" />
231     <a class="reference" href="glep-0040.txt">View document source</a>.
232 g2boojum 1.2 Generated on: 2005-09-15 21:03 UTC.
233 g2boojum 1.1 Generated 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.
235     </div>
236     </body>
237     </html>

  ViewVC Help
Powered by ViewVC 1.1.20