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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.6 - (hide annotations) (download) (as text)
Wed Apr 7 22:12:52 2010 UTC (4 years, 3 months ago) by robbat2
Branch: MAIN
Changes since 1.5: +11 -254 lines
File MIME type: text/html
Sync to 1.5 of glep-0055.txt (no embedded styles now).

1 peper 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 antarus 1.2
5 peper 1.1 <head>
6     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
7 robbat2 1.6 <meta name="generator" content="Docutils 0.6: http://docutils.sourceforge.net/" />
8 peper 1.1 <title>GLEP 55 -- Use EAPI-suffixed ebuilds (.ebuild-EAPI)</title>
9 robbat2 1.6 <link rel="stylesheet" href="tools/glep.css" type="text/css" /></head>
10 peper 1.1 <body bgcolor="white">
11     <table class="navigation" cellpadding="0" cellspacing="0"
12     width="100%" border="0">
13     <tr><td class="navicon" width="150" height="35">
14     <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
15     <img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
16     border="0" width="150" height="35" /></a></td>
17     <td class="textlinks" align="left">
18     [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
19 antarus 1.2 [<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>]
20 peper 1.1 [<b><a href="http://www.gentoo.org/proj/en/glep/glep-0055.txt">GLEP Source</a></b>]
21     </td></tr></table>
22     <table class="rfc2822 docutils field-list" frame="void" rules="none">
23     <col class="field-name" />
24     <col class="field-body" />
25     <tbody valign="top">
26     <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">55</td>
27     </tr>
28     <tr class="field"><th class="field-name">Title:</th><td class="field-body">Use EAPI-suffixed ebuilds (.ebuild-EAPI)</td>
29     </tr>
30 robbat2 1.6 <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.5</td>
31 peper 1.1 </tr>
32 robbat2 1.6 <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference external" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0055.txt?cvsroot=gentoo">2009/05/17 20:56:53</a></td>
33 peper 1.1 </tr>
34     <tr class="field"><th class="field-name">Author:</th><td class="field-body">Piotr JaroszyƄski &lt;peper&#32;&#97;t&#32;gentoo.org&gt;</td>
35     </tr>
36     <tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td>
37     </tr>
38     <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
39     </tr>
40 peper 1.3 <tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference external" href="glep-0002.html">text/x-rst</a></td>
41 peper 1.1 </tr>
42     <tr class="field"><th class="field-name">Created:</th><td class="field-body">17-Dec-2007</td>
43     </tr>
44 peper 1.3 <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">17-Dec-2007, 22-Dec-2007, 17-May-2009</td>
45 peper 1.1 </tr>
46     </tbody>
47     </table>
48     <hr />
49 peper 1.3 <div class="contents topic" id="contents">
50     <p class="topic-title first">Contents</p>
51 peper 1.1 <ul class="simple">
52 peper 1.3 <li><a class="reference internal" href="#abstract" id="id3">Abstract</a></li>
53     <li><a class="reference internal" href="#problem" id="id4">Problem</a></li>
54     <li><a class="reference internal" href="#current-behaviour" id="id5">Current behaviour</a><ul>
55     <li><a class="reference internal" href="#incompatible-change-of-inherit-e-g-make-it-look-in-the-package-dir-too" id="id6">Incompatible change of inherit (e.g. make it look in the package dir too)</a></li>
56     <li><a class="reference internal" href="#new-global-scope-function" id="id7">New global scope function</a></li>
57     <li><a class="reference internal" href="#new-version-format" id="id8">New version format</a></li>
58 peper 1.4 <li><a class="reference internal" href="#use-newer-bash-features" id="id9">Use newer bash features</a></li>
59 peper 1.3 </ul>
60     </li>
61 peper 1.4 <li><a class="reference internal" href="#abstract-solution" id="id10">Abstract solution</a></li>
62     <li><a class="reference internal" href="#proposed-solution" id="id11">Proposed solution</a></li>
63     <li><a class="reference internal" href="#specification" id="id12">Specification</a></li>
64     <li><a class="reference internal" href="#summary-of-ideas" id="id13">Summary of ideas</a><ul>
65     <li><a class="reference internal" href="#eapi-suffixed-ebuilds-proposed-solution" id="id14">EAPI-suffixed ebuilds (proposed solution)</a></li>
66     <li><a class="reference internal" href="#eapi-in-the-filename-with-one-time-extension-change" id="id15">EAPI in the filename with one-time extension change</a></li>
67     <li><a class="reference internal" href="#easily-fetchable-eapi-inside-the-ebuild" id="id16">Easily fetchable EAPI inside the ebuild</a></li>
68     <li><a class="reference internal" href="#easily-fetchable-eapi-inside-the-ebuild-and-one-time-extension-change" id="id17">Easily fetchable EAPI inside the ebuild and one-time extension change</a></li>
69     <li><a class="reference internal" href="#use-different-subdirectories-for-different-eapis-i-e-cat-pkg-eapix" id="id18">Use different subdirectories for different EAPIs, i.e. cat/pkg/eapiX/</a></li>
70 peper 1.3 </ul>
71     </li>
72 peper 1.4 <li><a class="reference internal" href="#references" id="id19">References</a></li>
73     <li><a class="reference internal" href="#copyright" id="id20">Copyright</a></li>
74 peper 1.1 </ul>
75     </div>
76     <blockquote>
77     <p>&quot;A little learning is a dangerous thing; drink deep, or taste not the Pierian
78     spring: there shallow draughts intoxicate the brain, and drinking largely
79     sobers us again.&quot;</p>
80     <p class="attribution">&mdash;Alexander Pope, An Essay on Criticism</p>
81     </blockquote>
82 peper 1.3 <div class="section" id="abstract">
83     <h1><a class="toc-backref" href="#id3">Abstract</a></h1>
84 peper 1.1 <p>This GLEP proposes usage of EAPI-suffixed file extensions for ebuilds (for
85     example, foo-1.2.3.ebuild-1).</p>
86     </div>
87 peper 1.3 <div class="section" id="problem">
88     <h1><a class="toc-backref" href="#id4">Problem</a></h1>
89 peper 1.1 <p>The current way of specifying the EAPI in ebuilds is flawed. In order to get the
90     EAPI the package manager needs to source the ebuild, which itself needs the EAPI
91     in the first place. Otherwise it imposes a serious limitation, namely every ebuild,
92     using any of the future EAPIs, will have to be source'able by old package
93 antarus 1.2 managers and hence there is no way to do any of the following:</p>
94 peper 1.1 <blockquote>
95     <ul class="simple">
96 antarus 1.2 <li>Change the behaviour of inherit in any way (for example, to extend or change
97 peper 1.1 eclass functionality).</li>
98     <li>Add new global scope functions in any sane way.</li>
99     <li>Extend versioning rules in an EAPI - for example, addition of the scm
100 peper 1.3 suffix - GLEP54 <a class="footnote-reference" href="#glep54" id="id1">[1]</a> or allowing more sensible version formats like
101     <tt class="docutils literal"><span class="pre">1-rc1</span></tt>, <tt class="docutils literal"><span class="pre">1-alpha</span></tt> etc. to match upstream more closely.</li>
102 peper 1.4 <li>Use newer bash features.</li>
103 peper 1.1 </ul>
104     </blockquote>
105     </div>
106 peper 1.3 <div class="section" id="current-behaviour">
107     <h1><a class="toc-backref" href="#id5">Current behaviour</a></h1>
108     <p>Following subsections show what happens if you introduce any of the mentioned
109     changes in an ebuild and try to install it with portage 2.1.6.13.</p>
110     <div class="section" id="incompatible-change-of-inherit-e-g-make-it-look-in-the-package-dir-too">
111     <h2><a class="toc-backref" href="#id6">Incompatible change of inherit (e.g. make it look in the package dir too)</a></h2>
112     <p><tt class="docutils literal"><span class="pre">sys-apps/foo-1.ebuild</span></tt>:</p>
113     <pre class="literal-block">
114     EAPI=&quot;5&quot;
115     inherit &quot;foo&quot;
116    
117     DESCRIPTION=&quot;&quot;
118     HOMEPAGE=&quot;&quot;
119     SRC_URI=&quot;&quot;
120     ...
121     </pre>
122     <p>Result:</p>
123     <pre class="literal-block">
124     *
125     * ERROR: sys-apps/foo-1 failed.
126     * Call stack:
127     * ebuild.sh, line 1879: Called _source_ebuild
128     * ebuild.sh, line 1818: Called source '/var/lib/gentoo/repositories/peper/sys-apps/foo/foo-1.ebuild'
129     * foo-1.ebuild, line 6: Called inherit 'foo'
130     * ebuild.sh, line 1218: Called die
131     * The specific snippet of code:
132     * [ ! -e &quot;$location&quot; ] &amp;&amp; die &quot;${1}.eclass could not be found by inherit()&quot;
133     * The die message:
134     * foo.eclass could not be found by inherit()
135     *
136     * If you need support, post the topmost build error, and the call stack if relevant.
137     * This ebuild is from an overlay: '/var/lib/gentoo/repositories/peper/'
138     *
139    
140     !!! All ebuilds that could satisfy &quot;sys-apps/foo&quot; have been masked.
141     !!! One of the following masked packages is required to complete your request:
142     - sys-apps/foo-1 (masked by: corruption)
143     </pre>
144 robbat2 1.6 <p>Current portage looks for eclasses only in the <tt class="docutils literal">eclass</tt> directory of a
145 peper 1.3 repository. This results in a fatal error and ebuild being masked by corruption
146     - might be pretty confusing to users.</p>
147     </div>
148     <div class="section" id="new-global-scope-function">
149     <h2><a class="toc-backref" href="#id7">New global scope function</a></h2>
150     <p><tt class="docutils literal"><span class="pre">sys-apps/foo-1.ebuild</span></tt>:</p>
151     <pre class="literal-block">
152     EAPI=&quot;5&quot;
153     new_global_scope_function &quot;foo&quot;
154    
155     DESCRIPTION=&quot;&quot;
156     HOMEPAGE=&quot;&quot;
157     SRC_URI=&quot;&quot;
158     ...
159     </pre>
160     <p>Result:</p>
161     <pre class="literal-block">
162     /var/lib/gentoo/repositories/peper/sys-apps/foo/foo-1.ebuild: line 7: new_global_scope_function: command not found
163    
164     !!! All ebuilds that could satisfy &quot;sys-apps/foo&quot; have been masked.
165     !!! One of the following masked packages is required to complete your request:
166     - sys-apps/foo-1 (masked by: EAPI 5)
167    
168     The current version of portage supports EAPI '2'. You must upgrade to a
169     newer version of portage before EAPI masked packages can be installed.
170     </pre>
171     <p>Not that bad as user is advised to upgrade portage.</p>
172     </div>
173     <div class="section" id="new-version-format">
174     <h2><a class="toc-backref" href="#id8">New version format</a></h2>
175     <p><tt class="docutils literal"><span class="pre">sys-apps/foo-2-rc1.ebuild</span></tt>:</p>
176     <pre class="literal-block">
177     Invalid ebuild name: /var/lib/gentoo/repositories/peper/sys-apps/foo/foo-2-rc1.ebuild
178    
179     emerge: there are no ebuilds to satisfy &quot;sys-apps/foo&quot;
180     </pre>
181     <p>Not the best error message, especially if there are lots of them.</p>
182     </div>
183 peper 1.4 <div class="section" id="use-newer-bash-features">
184     <h2><a class="toc-backref" href="#id9">Use newer bash features</a></h2>
185 robbat2 1.6 <p><tt class="docutils literal">|&amp;</tt> is a new type of redirection added in bash-4. It cannot be used even in
186 peper 1.4 local scope as bash still parses the whole ebuild.</p>
187     <p><tt class="docutils literal"><span class="pre">sys-apps/foo-1.ebuild</span></tt>:</p>
188     <pre class="literal-block">
189     EAPI=&quot;5&quot;
190    
191     foo() {
192     echo &quot;foo&quot; |&amp; cat
193     }
194     </pre>
195     <p>Result:</p>
196     <pre class="literal-block">
197     /var/lib/gentoo/repositories/peper/sys-apps/foo/foo-1.ebuild: line 8: syntax error near unexpected token `&amp;'
198     /var/lib/gentoo/repositories/peper/sys-apps/foo/foo-1.ebuild: line 8: ` echo &quot;foo&quot; |&amp; cat'
199     *
200     * ERROR: sys-apps/foo-1 failed.
201     * Call stack:
202     * ebuild.sh, line 1879: Called _source_ebuild
203     * ebuild.sh, line 1818: Called die
204     * The specific snippet of code:
205     * source &quot;${EBUILD}&quot; || die &quot;error sourcing ebuild&quot;
206     * The die message:
207     * error sourcing ebuild
208     *
209     * If you need support, post the topmost build error, and the call stack if relevant.
210     * This ebuild is from an overlay: '/var/lib/gentoo/repositories/peper/'
211     * ... done!
212    
213     !!! All ebuilds that could satisfy &quot;sys-apps/foo&quot; have been masked.
214     !!! One of the following masked packages is required to complete your request:
215     - sys-apps/foo-1 (masked by: corruption)
216     </pre>
217     <p>Again, not the best error.</p>
218     </div>
219 peper 1.3 </div>
220     <div class="section" id="abstract-solution">
221 peper 1.4 <h1><a class="toc-backref" href="#id10">Abstract solution</a></h1>
222 peper 1.1 <p>A solution to this problem has to lift those limitations and the only way to do
223     it is to make the EAPI of an ebuild available to the package managers in a way
224     that doesn't require them to source the ebuild. Another important requirement is
225     for the solution to be backward compatible, which has the pleasant side-effect
226     of making the solution applicable in the Gentoo tree right away. Opposed to
227     waiting an arbitrary amount of time, which is never long enough anyway, as the
228 peper 1.3 issues listed on the common portage problems page - <a class="footnote-reference" href="#portageproblems" id="id2">[2]</a> - show.</p>
229 peper 1.1 </div>
230 peper 1.3 <div class="section" id="proposed-solution">
231 peper 1.4 <h1><a class="toc-backref" href="#id11">Proposed solution</a></h1>
232 peper 1.1 <p>The proposed solution is to use EAPI-suffixed file extensions for ebuilds. This
233     allows package managers to trivially read the EAPI from the ebuild filename. It
234 antarus 1.2 is also backwards compatible, because currently ebuilds are recognised by the
235 robbat2 1.6 <tt class="docutils literal">.ebuild</tt> file extension and hence EAPI-suffixed ebuilds are simply ignored by
236 peper 1.1 the package managers.</p>
237     </div>
238 peper 1.3 <div class="section" id="specification">
239 peper 1.4 <h1><a class="toc-backref" href="#id12">Specification</a></h1>
240 robbat2 1.6 <p>Ebuild filename extension syntax: <tt class="docutils literal"><span class="pre">ebuild[-&lt;EAPI&gt;]</span></tt>, where <tt class="docutils literal">[]</tt> denotes an
241     optional part, and <tt class="docutils literal">&lt;EAPI&gt;</tt> is the EAPI of the ebuild.</p>
242 peper 1.3 <p>The EAPI used by the ebuild is the EAPI included in the filename if it is set.
243     Otherwise the EAPI set inside the ebuild is used, which defaults to 0 (this is
244     the current behaviour).</p>
245 peper 1.1 <p>Ebuilds with unsupported EAPIs are masked.</p>
246 peper 1.3 <p>It should be considered an error to set the EAPI both in the filename and in the
247     ebuild.</p>
248 peper 1.1 <p>Examples:</p>
249     <blockquote>
250     <ul>
251     <li><dl class="first docutils">
252     <dt><tt class="docutils literal"><span class="pre">pkg-1.ebuild</span></tt>, no EAPI set inside the ebuild</dt>
253 peper 1.3 <dd><p class="first last">EAPI defaults to 0.</p>
254 peper 1.1 </dd>
255     </dl>
256     </li>
257     <li><dl class="first docutils">
258     <dt><tt class="docutils literal"><span class="pre">pkg-2.ebuild-1</span></tt>, no EAPI set inside the ebuild</dt>
259 peper 1.3 <dd><p class="first last">EAPI 1 is used.</p>
260 peper 1.1 </dd>
261     </dl>
262     </li>
263     <li><dl class="first docutils">
264 peper 1.3 <dt><tt class="docutils literal"><span class="pre">pkg-3.ebuild-1</span></tt>, <tt class="docutils literal"><span class="pre">EAPI=&quot;1&quot;</span></tt></dt>
265     <dd><p class="first last">EAPI set in both places - error.</p>
266 peper 1.1 </dd>
267     </dl>
268     </li>
269     </ul>
270     </blockquote>
271     <p>Note that it is still not permitted to have more than one ebuild with equal
272     category, package name, and version. Although it would have the advantage of
273 antarus 1.2 allowing authors to provide backwards compatible ebuilds, it would introduce
274     problems too. The first is the requirement to have strict EAPI ordering, the
275     second is ensuring that all the ebuilds for a single category/package-version
276     are equivalent, i.e. installing any of them has exactly the same effect on a
277     given system.</p>
278 peper 1.5 <p>Also note that it is not a new restriction. It is already possible to illegally
279 robbat2 1.6 have multiple versions with different EAPIs as e.g. <tt class="docutils literal">1.0 == 1.00 == <span class="pre">1.00-r0</span></tt>
280 peper 1.5 and hence you could have <tt class="docutils literal"><span class="pre">foo-1.0.ebuild</span></tt> with EAPI X and <tt class="docutils literal"><span class="pre">foo-1.00.ebuild</span></tt>
281     with EAPI Y.</p>
282 peper 1.1 </div>
283 peper 1.3 <div class="section" id="summary-of-ideas">
284 peper 1.4 <h1><a class="toc-backref" href="#id13">Summary of ideas</a></h1>
285 peper 1.3 <div class="section" id="eapi-suffixed-ebuilds-proposed-solution">
286 peper 1.4 <h2><a class="toc-backref" href="#id14">EAPI-suffixed ebuilds (proposed solution)</a></h2>
287 peper 1.3 <dl class="docutils">
288     <dt>Properties:</dt>
289     <dd><ul class="first last simple">
290     <li>Can be used right away: yes</li>
291     <li>Hurts performance: no</li>
292     </ul>
293     </dd>
294     </dl>
295     <p>Some say it is clear and simple, others that it is ugly and unintuitive.</p>
296     </div>
297     <div class="section" id="eapi-in-the-filename-with-one-time-extension-change">
298 peper 1.4 <h2><a class="toc-backref" href="#id15">EAPI in the filename with one-time extension change</a></h2>
299 peper 1.3 <p>One of the proposed filename formats:
300     <tt class="docutils literal"><span class="pre">&lt;PKG&gt;-&lt;VER&gt;.eapi-&lt;EAPI&gt;.eb</span></tt></p>
301     <dl class="docutils">
302     <dt>Properties:</dt>
303 peper 1.1 <dd><ul class="first last simple">
304 peper 1.3 <li>Can be used right away: yes</li>
305     <li>Hurts performance: no</li>
306 peper 1.1 </ul>
307     </dd>
308     </dl>
309 peper 1.3 <p>This is equivalent to the proposed solution.</p>
310     <p>Some say it is better because the extension is static.</p>
311     </div>
312     <div class="section" id="easily-fetchable-eapi-inside-the-ebuild">
313 peper 1.4 <h2><a class="toc-backref" href="#id16">Easily fetchable EAPI inside the ebuild</a></h2>
314 peper 1.3 <dl class="docutils">
315     <dt>Properties:</dt>
316 peper 1.1 <dd><ul class="first last simple">
317 peper 1.3 <li>Can be used right away: no</li>
318     <li>Hurts performance: yes</li>
319 peper 1.1 </ul>
320     </dd>
321     </dl>
322 peper 1.3 <p>Cannot be used right away as it would trigger the errors shown in Current
323     behaviour section for old package managers.</p>
324     <p>Performance decrease comes from the fact that with version format changes in the
325     picture package managers need EAPI to parse the ebuild's version. That means that merely
326     picking the best version of a package requires loading EAPI (from cache or the
327     ebuild) for each available ebuild.</p>
328 peper 1.5 <p>Here is more or less how the package manager figures out the best available
329     version for a package with N versions available.</p>
330     <blockquote>
331     <ul class="simple">
332     <li>EAPI in the filename<ul>
333     <li>Read the directory containing the package - readdir()</li>
334     <li>For each ebuild, read its EAPI and using that parse its version - no I/O</li>
335     <li>Sort the versions - no I/O</li>
336     <li>Going down from the highest to the lowest version<ul>
337     <li>Get the metadata from cache - 2 x stat() + read()</li>
338     <li>break if the version is visible</li>
339     </ul>
340     </li>
341     </ul>
342     </li>
343     <li>EAPI in the ebuild<ul>
344     <li>Read the directory containing the package - readdir()</li>
345     <li>For each ebuild load its metadata from cache to get its EAPI - N x (2 x stat() + read())</li>
346     <li>Sort the versions - no I/O</li>
347     <li>Going down from the highest to the lowest version<ul>
348     <li>(metadata is already loaded) - no I/O</li>
349     <li>break if the version is visible - no I/O</li>
350     </ul>
351     </li>
352     </ul>
353     </li>
354     </ul>
355     </blockquote>
356     <p>The difference is in for how many versions the package manager needs to hit
357     cache. With EAPI in the ebuild it needs to do that for all versions, with EAPI
358     in the filename it depends on versions visibility.
359     For example, package foo has versions 1, 2, 3, 4, 5 and 6. 6 is masked, 5 is
360     ~arch and 1,2,3 and 4 are arch. Say, the user accepts only arch for this
361     package. With EAPI in the filename it will read metadata only for versions
362     6, 5 and 4. With EAPI in the ebuild it needs to load metadata for all versions.</p>
363     <p>It's hard to say what's the avarage case, but surely the worst case scenario
364     (when only the lowest version is visible) is uncommon.</p>
365 peper 1.3 </div>
366     <div class="section" id="easily-fetchable-eapi-inside-the-ebuild-and-one-time-extension-change">
367 peper 1.4 <h2><a class="toc-backref" href="#id17">Easily fetchable EAPI inside the ebuild and one-time extension change</a></h2>
368 peper 1.3 <dl class="docutils">
369     <dt>Properties:</dt>
370 peper 1.1 <dd><ul class="first last simple">
371 peper 1.3 <li>Can be used right away: yes</li>
372     <li>Hurts performance: yes</li>
373 peper 1.1 </ul>
374     </dd>
375     </dl>
376 peper 1.3 <p>Performance decrease as described in the previous section.</p>
377     <p>Some say it is clear and simple, others that it is confusing and unintuitive,
378     because of the arbitrary format restrictions in what is a bash script otherwise.</p>
379     </div>
380     <div class="section" id="use-different-subdirectories-for-different-eapis-i-e-cat-pkg-eapix">
381 peper 1.4 <h2><a class="toc-backref" href="#id18">Use different subdirectories for different EAPIs, i.e. cat/pkg/eapiX/</a></h2>
382 peper 1.3 <dl class="docutils">
383     <dt>Properties:</dt>
384     <dd><ul class="first last simple">
385     <li>Can be used right away: yes</li>
386     <li>Hurts performance: yes</li>
387 peper 1.1 </ul>
388 peper 1.3 </dd>
389     </dl>
390     <p>Performance decrease comes from the fact that it adds several more directory
391     reads.</p>
392     <p>Some say that it makes it much harder for maintainers to see what they have.</p>
393     </div>
394 peper 1.1 </div>
395 peper 1.3 <div class="section" id="references">
396 peper 1.4 <h1><a class="toc-backref" href="#id19">References</a></h1>
397 peper 1.1 <table class="docutils footnote" frame="void" id="glep54" rules="none">
398     <colgroup><col class="label" /><col /></colgroup>
399     <tbody valign="top">
400 peper 1.3 <tr><td class="label"><a class="fn-backref" href="#id1">[1]</a></td><td>GLEP 54, scm package version suffix
401     (<a class="reference external" href="http://glep.gentoo.org/glep-0054.html">http://glep.gentoo.org/glep-0054.html</a>)</td></tr>
402 peper 1.1 </tbody>
403     </table>
404     <table class="docutils footnote" frame="void" id="portageproblems" rules="none">
405     <colgroup><col class="label" /><col /></colgroup>
406     <tbody valign="top">
407 peper 1.3 <tr><td class="label"><a class="fn-backref" href="#id2">[2]</a></td><td>Common portage problems
408     (<a class="reference external" href="http://www.gentoo.org/proj/en/portage/doc/common-problems.xml">http://www.gentoo.org/proj/en/portage/doc/common-problems.xml</a>)</td></tr>
409 peper 1.1 </tbody>
410     </table>
411     </div>
412 peper 1.3 <div class="section" id="copyright">
413 peper 1.4 <h1><a class="toc-backref" href="#id20">Copyright</a></h1>
414 peper 1.1 <p>This document has been placed in the public domain.</p>
415     <!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : -->
416     </div>
417    
418     </div>
419     <div class="footer">
420     <hr class="footer" />
421 peper 1.3 <a class="reference external" href="glep-0055.txt">View document source</a>.
422 robbat2 1.6 Generated on: 2010-04-07 22:12 UTC.
423 peper 1.3 Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
424 peper 1.1
425     </div>
426     </body>
427     </html>

  ViewVC Help
Powered by ViewVC 1.1.20