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

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

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

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

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

  ViewVC Help
Powered by ViewVC 1.1.20