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

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

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

Revision 1.5 Revision 1.6
… …
30<tbody valign="top"> 30<tbody valign="top">
31<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">42</td> 31<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">42</td>
32</tr> 32</tr>
33<tr class="field"><th class="field-name">Title:</th><td class="field-body">Critical News Reporting</td> 33<tr class="field"><th class="field-name">Title:</th><td class="field-body">Critical News Reporting</td>
34</tr> 34</tr>
35<tr class="field"><th class="field-name">Version:</th><td class="field-body">$Revision: 1.5 $</td> 35<tr class="field"><th class="field-name">Version:</th><td class="field-body">$Revision: 1.6 $</td>
36</tr> 36</tr>
37<tr class="field"><th class="field-name">Author:</th><td class="field-body">Ciaran McCreesh &lt;ciaranm&#32;&#97;t&#32;gentoo.org&gt;</td> 37<tr class="field"><th class="field-name">Author:</th><td class="field-body">Ciaran McCreesh &lt;ciaranm&#32;&#97;t&#32;gentoo.org&gt;</td>
38</tr> 38</tr>
39<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-0042.txt?cvsroot=gentoo">$Date: 2005/12/13 03:21:59 $</a></td> 39<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-0042.txt?cvsroot=gentoo">$Date: 2005/12/18 04:16:44 $</a></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>
43<tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> 43<tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
44</tr> 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> 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> 46</tr>
47<tr class="field"><th class="field-name">Created:</th><td class="field-body">31-Oct-2005</td> 47<tr class="field"><th class="field-name">Created:</th><td class="field-body">31-Oct-2005</td>
48</tr> 48</tr>
49<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">1-Nov-2005, 5-Nov-2005, 7-Nov-2005, 11-Dec-2005, 13-Dec-2005</td> 49<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">1-Nov-2005, 5-Nov-2005, 7-Nov-2005, 11-Dec-2005, 13-Dec-2005, 18-Dec-2005</td>
50</tr> 50</tr>
51</tbody> 51</tbody>
52</table> 52</table>
53<hr /> 53<hr />
54<div class="contents topic" id="contents"> 54<div class="contents topic" id="contents">
… …
57<li><a class="reference" href="#abstract" id="id20" name="id20">Abstract</a></li> 57<li><a class="reference" href="#abstract" id="id20" name="id20">Abstract</a></li>
58<li><a class="reference" href="#motivation" id="id21" name="id21">Motivation</a></li> 58<li><a class="reference" href="#motivation" id="id21" name="id21">Motivation</a></li>
59<li><a class="reference" href="#requirements" id="id22" name="id22">Requirements</a></li> 59<li><a class="reference" href="#requirements" id="id22" name="id22">Requirements</a></li>
60<li><a class="reference" href="#specification" id="id23" name="id23">Specification</a><ul> 60<li><a class="reference" href="#specification" id="id23" name="id23">Specification</a><ul>
61<li><a class="reference" href="#overview" id="id24" name="id24">Overview</a></li> 61<li><a class="reference" href="#overview" id="id24" name="id24">Overview</a></li>
62<li><a class="reference" href="#required-portage-enhancements" id="id25" name="id25">Required Portage Enhancements</a></li>
62<li><a class="reference" href="#news-item-identities" id="id25" name="id25">News Item Identities</a></li> 63<li><a class="reference" href="#news-item-identities" id="id26" name="id26">News Item Identities</a></li>
63<li><a class="reference" href="#news-item-directories" id="id26" name="id26">News Item Directories</a></li> 64<li><a class="reference" href="#news-item-directories" id="id27" name="id27">News Item Directories</a></li>
64<li><a class="reference" href="#news-item-files" id="id27" name="id27">News Item Files</a><ul> 65<li><a class="reference" href="#news-item-files" id="id28" name="id28">News Item Files</a><ul>
65<li><a class="reference" href="#news-item-headers" id="id28" name="id28">News Item Headers</a></li> 66<li><a class="reference" href="#news-item-headers" id="id29" name="id29">News Item Headers</a></li>
66<li><a class="reference" href="#news-item-body" id="id29" name="id29">News Item Body</a></li> 67<li><a class="reference" href="#news-item-body" id="id30" name="id30">News Item Body</a></li>
67<li><a class="reference" href="#example-news-item" id="id30" name="id30">Example News Item</a></li> 68<li><a class="reference" href="#example-news-item" id="id31" name="id31">Example News Item</a></li>
68</ul> 69</ul>
69</li> 70</li>
70<li><a class="reference" href="#news-item-quality-control" id="id31" name="id31">News Item Quality Control</a></li> 71<li><a class="reference" href="#news-item-quality-control" id="id32" name="id32">News Item Quality Control</a></li>
71<li><a class="reference" href="#news-item-distribution" id="id32" name="id32">News Item Distribution</a><ul> 72<li><a class="reference" href="#news-item-distribution" id="id33" name="id33">News Item Distribution</a><ul>
72<li><a class="reference" href="#server-side" id="id33" name="id33">Server Side</a></li> 73<li><a class="reference" href="#server-side" id="id34" name="id34">Server Side</a></li>
73<li><a class="reference" href="#client-side" id="id34" name="id34">Client Side</a></li> 74<li><a class="reference" href="#client-side" id="id35" name="id35">Client Side</a></li>
74</ul> 75</ul>
75</li> 76</li>
76<li><a class="reference" href="#news-item-clients" id="id35" name="id35">News Item Clients</a></li> 77<li><a class="reference" href="#news-item-clients" id="id36" name="id36">News Item Clients</a></li>
77<li><a class="reference" href="#news-item-removal" id="id36" name="id36">News Item Removal</a></li> 78<li><a class="reference" href="#news-item-removal" id="id37" name="id37">News Item Removal</a></li>
78</ul> 79</ul>
79</li> 80</li>
80<li><a class="reference" href="#integration-with-existing-systems" id="id37" name="id37">Integration with Existing Systems</a></li> 81<li><a class="reference" href="#integration-with-existing-systems" id="id38" name="id38">Integration with Existing Systems</a></li>
81<li><a class="reference" href="#backwards-compatibility" id="id38" name="id38">Backwards Compatibility</a></li> 82<li><a class="reference" href="#backwards-compatibility" id="id39" name="id39">Backwards Compatibility</a></li>
82<li><a class="reference" href="#reference-implementation" id="id39" name="id39">Reference Implementation</a><ul> 83<li><a class="reference" href="#reference-implementation" id="id40" name="id40">Reference Implementation</a><ul>
83<li><a class="reference" href="#portage-code" id="id40" name="id40">Portage Code</a></li> 84<li><a class="reference" href="#portage-code" id="id41" name="id41">Portage Code</a></li>
84<li><a class="reference" href="#simple-eselect-news-client" id="id41" name="id41">Simple <tt class="docutils literal"><span class="pre">eselect</span></tt> News Client</a></li> 85<li><a class="reference" href="#simple-eselect-news-client" id="id42" name="id42">Simple <tt class="docutils literal"><span class="pre">eselect</span></tt> News Client</a></li>
85<li><a class="reference" href="#simple-news-to-mail-forwarder" id="id42" name="id42">Simple News to Mail Forwarder</a></li> 86<li><a class="reference" href="#simple-news-to-mail-forwarder" id="id43" name="id43">Simple News to Mail Forwarder</a></li>
86</ul> 87</ul>
87</li> 88</li>
88<li><a class="reference" href="#credits" id="id43" name="id43">Credits</a></li> 89<li><a class="reference" href="#credits" id="id44" name="id44">Credits</a></li>
89<li><a class="reference" href="#example-files" id="id44" name="id44">Example Files</a></li> 90<li><a class="reference" href="#example-files" id="id45" name="id45">Example Files</a></li>
90<li><a class="reference" href="#references" id="id45" name="id45">References</a></li> 91<li><a class="reference" href="#references" id="id46" name="id46">References</a></li>
91<li><a class="reference" href="#copyright" id="id46" name="id46">Copyright</a></li> 92<li><a class="reference" href="#copyright" id="id47" name="id47">Copyright</a></li>
92</ul> 93</ul>
93</div> 94</div>
94<div class="section" id="abstract"> 95<div class="section" id="abstract">
95<h1><a class="toc-backref" href="#id20" name="abstract">Abstract</a></h1> 96<h1><a class="toc-backref" href="#id20" name="abstract">Abstract</a></h1>
96<p>This GLEP proposes a new way of informing users about important updates and news 97<p>This GLEP proposes a new way of informing users about important updates and news
… …
185<p>News items are published and delivered to users as follows:</p> 186<p>News items are published and delivered to users as follows:</p>
186<ol class="arabic simple"> 187<ol class="arabic simple">
187<li>A news item is written. The format to be used is described below.</li> 188<li>A news item is written. The format to be used is described below.</li>
188<li>The news item is reviewed, following the process described in 189<li>The news item is reviewed, following the process described in
189<a class="reference" href="#news-item-quality-control">News Item Quality Control</a>.</li> 190<a class="reference" href="#news-item-quality-control">News Item Quality Control</a>.</li>
190<li>The news item is committed to a CVS (or Subversion <a class="footnote-reference" href="#glep-36" id="id4" name="id4">[10]</a>) repository. 191<li>The news item is committed to a CVS (or Subversion <a class="footnote-reference" href="#glep-36" id="id4" name="id4">[9]</a>) repository.
191From here, it is merged with the rsync tree. This is described in <a class="reference" href="#news-item-distribution">News Item 192From here, it is merged with the rsync tree. This is described in <a class="reference" href="#news-item-distribution">News Item
192Distribution</a>.</li> 193Distribution</a>.</li>
193<li>Users fetch the news item when they sync. This ensures that the news items in 194<li>Users fetch the news item when they sync. This ensures that the news items in
194question are pushed to the user before the user accidentally makes an 195question are pushed to the user before the user accidentally makes an
195unwanted change. No changes to the existing rsync process are required by 196unwanted change. No changes to the existing rsync process are required by
… …
199informing the user that there are unread news items.</li> 200informing the user that there are unread news items.</li>
200<li>The news item is handled by the user's choice of news item reader. See <a class="reference" href="#news-item-clients">News 201<li>The news item is handled by the user's choice of news item reader. See <a class="reference" href="#news-item-clients">News
201Item Clients</a>.</li> 202Item Clients</a>.</li>
202</ol> 203</ol>
203</div> 204</div>
205<div class="section" id="required-portage-enhancements">
206<h2><a class="toc-backref" href="#id25" name="required-portage-enhancements">Required Portage Enhancements</a></h2>
207<p>The following extensions to Portage are required:</p>
208<p>TODO: ferringb wants spaces added to the first item on the list. I don't,
209because it makes repo id -&gt; filename mappings nasty.</p>
210<ul class="simple">
211<li>Every repository (including overlays) will require a unique identifier. It is
212assumed that an identifier will be a string consisting of characters from
213<tt class="docutils literal"><span class="pre">a</span></tt> to <tt class="docutils literal"><span class="pre">z</span></tt>, <tt class="docutils literal"><span class="pre">A</span></tt> to <tt class="docutils literal"><span class="pre">Z</span></tt>, <tt class="docutils literal"><span class="pre">0</span></tt> to <tt class="docutils literal"><span class="pre">9</span></tt>, <tt class="docutils literal"><span class="pre">+</span></tt> (plus), <tt class="docutils literal"><span class="pre">-</span></tt> (hyphen),
214<tt class="docutils literal"><span class="pre">:</span></tt> (colon) and <tt class="docutils literal"><span class="pre">_</span></tt> (underscore).</li>
215<li>Portage must provide a way for external programs to obtain a list of all
216repository identifiers for a given system. It is assumed that this will be in
217the form of a <tt class="docutils literal"><span class="pre">portageq</span></tt> command (e.g. <tt class="docutils literal"><span class="pre">portageq</span> <span class="pre">get_repo_ids</span></tt>).</li>
218<li>Portage must provide a way for external programs to obtain the base path for
219a repository with a given ID. It is assumed that this will be in the form of
220a <tt class="docutils literal"><span class="pre">portageq</span></tt> command (e.g. <tt class="docutils literal"><span class="pre">portageq</span> <span class="pre">get_repo_root</span> <span class="pre">gentoo-x86</span></tt>).</li>
221<li>Portage must extend <tt class="docutils literal"><span class="pre">portageq</span> <span class="pre">has_version</span></tt> to support restrictions to a
222given repository ID.</li>
223<li>Portage must extend <tt class="docutils literal"><span class="pre">portageq</span></tt> to implement a command which returns whether
224or not the profile used for a given repository ID matches a certain base path
225(e.g. <tt class="docutils literal"><span class="pre">portageq</span> <span class="pre">profile_used</span> <span class="pre">default-linux/sparc/sparc64/2004.3</span> <span class="pre">gentoo-x86</span></tt>).</li>
226</ul>
227<p>These extensions are assumed during the following specification.</p>
228</div>
204<div class="section" id="news-item-identities"> 229<div class="section" id="news-item-identities">
205<h2><a class="toc-backref" href="#id25" name="news-item-identities">News Item Identities</a></h2> 230<h2><a class="toc-backref" href="#id26" name="news-item-identities">News Item Identities</a></h2>
206<p>Each news item will have a unique identifier. This identifier will be in the 231<p>Each news item will have a unique identifier. This identifier will be in the
207form <tt class="docutils literal"><span class="pre">yyyy-mm-dd-short-name</span></tt>, where <tt class="docutils literal"><span class="pre">yyyy</span></tt> is the year (e.g. <tt class="docutils literal"><span class="pre">2005</span></tt>), 232form <tt class="docutils literal"><span class="pre">yyyy-mm-dd-short-name</span></tt>, where <tt class="docutils literal"><span class="pre">yyyy</span></tt> is the year (e.g. <tt class="docutils literal"><span class="pre">2005</span></tt>),
208<tt class="docutils literal"><span class="pre">mm</span></tt> is the month (<tt class="docutils literal"><span class="pre">01</span></tt> through <tt class="docutils literal"><span class="pre">12</span></tt>) and dd is the day of the month 233<tt class="docutils literal"><span class="pre">mm</span></tt> is the month (<tt class="docutils literal"><span class="pre">01</span></tt> through <tt class="docutils literal"><span class="pre">12</span></tt>) and dd is the day of the month
209(<tt class="docutils literal"><span class="pre">01</span></tt> through <tt class="docutils literal"><span class="pre">31</span></tt>). The <tt class="docutils literal"><span class="pre">short-name</span></tt> is a very short name describing the 234(<tt class="docutils literal"><span class="pre">01</span></tt> through <tt class="docutils literal"><span class="pre">31</span></tt>). The <tt class="docutils literal"><span class="pre">short-name</span></tt> is a very short name describing the
210news item (e.g. <tt class="docutils literal"><span class="pre">yoursql-updates</span></tt>), consisting only of the characters <tt class="docutils literal"><span class="pre">a-z</span></tt>, 235news item (e.g. <tt class="docutils literal"><span class="pre">yoursql-updates</span></tt>), consisting only of the characters <tt class="docutils literal"><span class="pre">a-z</span></tt>,
211<tt class="docutils literal"><span class="pre">0-9</span></tt>, <tt class="docutils literal"><span class="pre">+</span></tt> (plus), <tt class="docutils literal"><span class="pre">:</span></tt> (colon) and <tt class="docutils literal"><span class="pre">-</span></tt> (hyphen).</p> 236<tt class="docutils literal"><span class="pre">0-9</span></tt>, <tt class="docutils literal"><span class="pre">+</span></tt> (plus), <tt class="docutils literal"><span class="pre">:</span></tt> (colon), <tt class="docutils literal"><span class="pre">-</span></tt> (hyphen) and <tt class="docutils literal"><span class="pre">_</span></tt> (underscore).</p>
212</div> 237</div>
213<div class="section" id="news-item-directories"> 238<div class="section" id="news-item-directories">
214<h2><a class="toc-backref" href="#id26" name="news-item-directories">News Item Directories</a></h2> 239<h2><a class="toc-backref" href="#id27" name="news-item-directories">News Item Directories</a></h2>
215<p>Each news item will be represented by a directory whose name is the same as the 240<p>Each news item will be represented by a directory whose name is the same as the
216news item's identifier.</p> 241news item's identifier.</p>
217<p>The directory will contain a file named <tt class="docutils literal"><span class="pre">yyyy-mm-dd-short-name.en.txt</span></tt>, which 242<p>The directory will contain a file named <tt class="docutils literal"><span class="pre">yyyy-mm-dd-short-name.en.txt</span></tt>, which
218contains the text of the news item, in English, in the format described below.</p> 243contains the text of the news item, in English, in the format described below.</p>
219<p>If a news item is translated, other files named <tt class="docutils literal"><span class="pre">yyyy-mm-dd-short-name.xx.txt</span></tt> 244<p>If a news item is translated, other files named <tt class="docutils literal"><span class="pre">yyyy-mm-dd-short-name.xx.txt</span></tt>
220(where <tt class="docutils literal"><span class="pre">xx</span></tt> is the ISO 639 <a class="footnote-reference" href="#iso-639" id="id5" name="id5">[11]</a> two letter country code) will also be 245(where <tt class="docutils literal"><span class="pre">xx</span></tt> is the ISO 639 <a class="footnote-reference" href="#iso-639" id="id5" name="id5">[11]</a> two letter country code) will also be
221provided. However, only the English version of a news item is authoritative. 246provided. However, only the English version of a news item is authoritative.
222This anglocentricity is justified by precedent <a class="footnote-reference" href="#glep-34" id="id6" name="id6">[9]</a>.</p> 247This anglocentricity is justified by precedent <a class="footnote-reference" href="#glep-34" id="id6" name="id6">[8]</a>.</p>
223</div> 248</div>
224<div class="section" id="news-item-files"> 249<div class="section" id="news-item-files">
225<h2><a class="toc-backref" href="#id27" name="news-item-files">News Item Files</a></h2> 250<h2><a class="toc-backref" href="#id28" name="news-item-files">News Item Files</a></h2>
226<p>A news item file is a text file, encoded using UTF-8 <a class="footnote-reference" href="#rfc-3629" id="id7" name="id7">[14]</a> for 251<p>A news item file is a text file, encoded using UTF-8 <a class="footnote-reference" href="#rfc-3629" id="id7" name="id7">[14]</a> for
227compatibility with and for the same reasons as existing Gentoo documentation 252compatibility with and for the same reasons as existing Gentoo documentation
228<a class="footnote-reference" href="#docs-policy" id="id8" name="id8">[2]</a> and the tree <a class="footnote-reference" href="#glep-31" id="id9" name="id9">[8]</a>.</p> 253<a class="footnote-reference" href="#docs-policy" id="id8" name="id8">[2]</a> and the tree <a class="footnote-reference" href="#glep-31" id="id9" name="id9">[7]</a>.</p>
229<p>News items should be signed with a detached GPG signature:</p> 254<p>News items should be signed with a detached GPG signature:</p>
230<pre class="literal-block"> 255<pre class="literal-block">
231gpg --armour --detach-sign ????-??-??-*.??.txt 256gpg --armour --detach-sign ????-??-??-*.??.txt
232</pre> 257</pre>
233<p>A news item file's content will consist of an <a class="reference" href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> style header <a class="footnote-reference" href="#rfc-822" id="id10" name="id10">[13]</a> 258<p>A news item file's content will consist of an <a class="reference" href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> style header <a class="footnote-reference" href="#rfc-822" id="id10" name="id10">[13]</a>
234followed by the main body of the message as plain text. This GLEP defines 259followed by the main body of the message as plain text. This GLEP defines
235various optional and mandatory headers. Future GLEPs may propose new headers — 260various optional and mandatory headers. Future GLEPs may propose new headers —
236tools handling these news items must ignore any unrecognised header.</p> 261tools handling these news items must ignore any unrecognised header.</p>
237<div class="section" id="news-item-headers"> 262<div class="section" id="news-item-headers">
238<h3><a class="toc-backref" href="#id28" name="news-item-headers">News Item Headers</a></h3> 263<h3><a class="toc-backref" href="#id29" name="news-item-headers">News Item Headers</a></h3>
239<p>The following headers describe the purpose and format of the news item:</p> 264<p>The following headers describe the purpose and format of the news item:</p>
240<dl class="docutils"> 265<dl class="docutils">
241<dt><tt class="docutils literal"><span class="pre">Title:</span></tt></dt> 266<dt><tt class="docutils literal"><span class="pre">Title:</span></tt></dt>
242<dd>A short (maximum 44 characters) descriptive title. Mandatory.</dd> 267<dd>A short (maximum 44 characters) descriptive title. Mandatory.</dd>
243<dt><tt class="docutils literal"><span class="pre">Author:</span></tt></dt> 268<dt><tt class="docutils literal"><span class="pre">Author:</span></tt></dt>
… …
247<dd>For translated news items, the translator's name and email address. Multiple 272<dd>For translated news items, the translator's name and email address. Multiple
248translator headers may be specified if appropriate.</dd> 273translator headers may be specified if appropriate.</dd>
249<dt><tt class="docutils literal"><span class="pre">Content-Type:</span></tt></dt> 274<dt><tt class="docutils literal"><span class="pre">Content-Type:</span></tt></dt>
250<dd>Must be <tt class="docutils literal"><span class="pre">text/plain</span></tt>. Mandatory.</dd> 275<dd>Must be <tt class="docutils literal"><span class="pre">text/plain</span></tt>. Mandatory.</dd>
251<dt><tt class="docutils literal"><span class="pre">Posted:</span></tt></dt> 276<dt><tt class="docutils literal"><span class="pre">Posted:</span></tt></dt>
252<dd>Date of posting, in <tt class="docutils literal"><span class="pre">dd-mmm-yyyy</span></tt> format (e.g. 14-Aug-2001) for 277<dd>Date of posting, in <tt class="docutils literal"><span class="pre">yyyy-mm-dd</span></tt> format (e.g. 2005-12-18) for
253compatibility with GLEP 1 <a class="footnote-reference" href="#glep-1" id="id11" name="id11">[6]</a>. UTC time in <tt class="docutils literal"><span class="pre">hh-mm-ss</span> <span class="pre">+0000</span></tt> format 278compatibility with GLEP 45 <a class="footnote-reference" href="#glep-45" id="id11" name="id11">[10]</a>. Mandatory.</dd>
254may also be included. Mandatory.</dd>
255<dt><tt class="docutils literal"><span class="pre">Revision:</span></tt></dt> 279<dt><tt class="docutils literal"><span class="pre">Revision:</span></tt></dt>
256<dd>Initially 1. Incremented every time a non-trivial change is made. Changes 280<dd>Initially 1. Incremented every time a non-trivial change is made. Changes
257which require a re-read of the news item should instead use a new news item 281which require a re-read of the news item should instead use a new news item
258file. Mandatory.</dd> 282file. Mandatory.</dd>
259<dt><tt class="docutils literal"><span class="pre">News-Item-Format:</span></tt></dt> 283<dt><tt class="docutils literal"><span class="pre">News-Item-Format:</span></tt></dt>
… …
264<p>The following headers are used for filtering:</p> 288<p>The following headers are used for filtering:</p>
265<dl class="docutils"> 289<dl class="docutils">
266<dt><tt class="docutils literal"><span class="pre">Display-If-Installed:</span></tt></dt> 290<dt><tt class="docutils literal"><span class="pre">Display-If-Installed:</span></tt></dt>
267<dd>A dependency atom or simple package name (for example, 291<dd>A dependency atom or simple package name (for example,
268<tt class="docutils literal"><span class="pre">&lt;dev-lang/php-5_alpha</span></tt> or <tt class="docutils literal"><span class="pre">net-www/apache</span></tt>). If the user has the 292<tt class="docutils literal"><span class="pre">&lt;dev-lang/php-5_alpha</span></tt> or <tt class="docutils literal"><span class="pre">net-www/apache</span></tt>). If the user has the
293package specified installed from the repository from which the news item was
269package specified installed, the news item should be displayed.</dd> 294obtained, the news item should be displayed.</dd>
270<dt><tt class="docutils literal"><span class="pre">Display-If-Keyword:</span></tt></dt> 295<dt><tt class="docutils literal"><span class="pre">Display-If-Keyword:</span></tt></dt>
271<dd>A keyword <a class="footnote-reference" href="#glep-22" id="id12" name="id12">[7]</a> name, for example <tt class="docutils literal"><span class="pre">mips</span></tt> or <tt class="docutils literal"><span class="pre">x86-fbsd</span></tt>. If the 296<dd>A keyword <a class="footnote-reference" href="#glep-22" id="id12" name="id12">[6]</a> name, for example <tt class="docutils literal"><span class="pre">mips</span></tt> or <tt class="docutils literal"><span class="pre">x86-fbsd</span></tt>. If the
272user is on the keyword in question, the news item should be displayed.</dd> 297user is on the keyword in question, the news item should be displayed.</dd>
273<dt><tt class="docutils literal"><span class="pre">Display-If-Profile:</span></tt></dt> 298<dt><tt class="docutils literal"><span class="pre">Display-If-Profile:</span></tt></dt>
274<dd>A profile path, for example <tt class="docutils literal"><span class="pre">default-linux/sparc/sparc64/server</span></tt>. Standard 299<dd>A profile path, for example <tt class="docutils literal"><span class="pre">default-linux/sparc/sparc64/server</span></tt>. If the
275shell GLOB wildcards may be used. If the user is using the exact profile in 300user is using the exact profile in question, or a subprofile of this
276question, the news item should be displayed. This header may be used to 301profile, the news item should be displayed. This header may be used to
277replace <tt class="docutils literal"><span class="pre">deprecated</span></tt> files in the future.</dd> 302replace <tt class="docutils literal"><span class="pre">deprecated</span></tt> files in the future.</dd>
278</dl> 303</dl>
279<div class="note"> 304<div class="note">
280<p class="first admonition-title">Note</p> 305<p class="first admonition-title">Note</p>
281<p class="last">When performing package moves, developers must also update any 306<p class="last">When performing package moves, developers must also update any
… …
299likely to occur than &quot;display this news item for people using <tt class="docutils literal"><span class="pre">YourSQL</span></tt>, or 324likely to occur than &quot;display this news item for people using <tt class="docutils literal"><span class="pre">YourSQL</span></tt>, or
300for people on <tt class="docutils literal"><span class="pre">sparc</span></tt> or <tt class="docutils literal"><span class="pre">x86-obsd</span></tt>&quot; or &quot;display these news items for 325for people on <tt class="docutils literal"><span class="pre">sparc</span></tt> or <tt class="docutils literal"><span class="pre">x86-obsd</span></tt>&quot; or &quot;display these news items for
301people who use <tt class="docutils literal"><span class="pre">YourSQL</span></tt> and who are on both <tt class="docutils literal"><span class="pre">sparc</span></tt> and <tt class="docutils literal"><span class="pre">x86-obsd</span></tt>&quot;.</p> 326people who use <tt class="docutils literal"><span class="pre">YourSQL</span></tt> and who are on both <tt class="docutils literal"><span class="pre">sparc</span></tt> and <tt class="docutils literal"><span class="pre">x86-obsd</span></tt>&quot;.</p>
302</div> 327</div>
303<div class="section" id="news-item-body"> 328<div class="section" id="news-item-body">
304<h3><a class="toc-backref" href="#id29" name="news-item-body">News Item Body</a></h3> 329<h3><a class="toc-backref" href="#id30" name="news-item-body">News Item Body</a></h3>
305<p>The header section must be followed by a blank line, then the main body of the 330<p>The header section must be followed by a blank line, then the main body of the
306text.</p> 331text.</p>
307<p>The text body should be wrapped at 72 characters. No fancy formatting or tab 332<p>The text body should be wrapped at 72 characters. No fancy formatting or tab
308characters should be used — the news item may be being displayed directly to a 333characters should be used — the news item may be being displayed directly to a
309terminal. Paragraphs should be separated by a blank line.</p> 334terminal. Paragraphs should be separated by a blank line.</p>
… …
312simply a &quot;read this link&quot; text. It is assumed that the user will have access to 337simply a &quot;read this link&quot; text. It is assumed that the user will have access to
313a web browser <em>somewhere</em>, but not necessarily on the box which is being 338a web browser <em>somewhere</em>, but not necessarily on the box which is being
314administrated — this will be the case on may servers and routers, for example.</p> 339administrated — this will be the case on may servers and routers, for example.</p>
315</div> 340</div>
316<div class="section" id="example-news-item"> 341<div class="section" id="example-news-item">
317<h3><a class="toc-backref" href="#id30" name="example-news-item">Example News Item</a></h3> 342<h3><a class="toc-backref" href="#id31" name="example-news-item">Example News Item</a></h3>
318<p><a class="reference" href="glep-0042-extras/example-news-item.txt">This hypothetical news item</a> <a class="footnote-reference" href="#id18" id="id19" name="id19">[16]</a> could be used for an upgrade to the 343<p><a class="reference" href="glep-0042-extras/example-news-item.txt">This hypothetical news item</a> <a class="footnote-reference" href="#id18" id="id19" name="id19">[16]</a> could be used for an upgrade to the
319<tt class="docutils literal"><span class="pre">YourSQL</span></tt> database format which breaks forward compatibility.</p> 344<tt class="docutils literal"><span class="pre">YourSQL</span></tt> database format which breaks forward compatibility.</p>
320</div> 345</div>
321</div> 346</div>
322<div class="section" id="news-item-quality-control"> 347<div class="section" id="news-item-quality-control">
323<h2><a class="toc-backref" href="#id31" name="news-item-quality-control">News Item Quality Control</a></h2> 348<h2><a class="toc-backref" href="#id32" name="news-item-quality-control">News Item Quality Control</a></h2>
324<p>There have been complaints regarding the comprehensibility of some upgrade 349<p>There have been complaints regarding the comprehensibility of some upgrade
325notices and news items in the past. This is understandable — not every Gentoo 350notices and news items in the past. This is understandable — not every Gentoo
326developer speaks English as a first language. However, for the sake of clarity, 351developer speaks English as a first language. However, for the sake of clarity,
327professionalism and avoiding making us look like prats, it is important that any 352professionalism and avoiding making us look like prats, it is important that any
328language problems be corrected before inflicting a news item upon end users.</p> 353language problems be corrected before inflicting a news item upon end users.</p>
… …
350Thus, the justification should be in the form &quot;this message is important to 375Thus, the justification should be in the form &quot;this message is important to
351YourSQL users because ...&quot;, not &quot;YourSQL is important because ...&quot;.</p> 376YourSQL users because ...&quot;, not &quot;YourSQL is important because ...&quot;.</p>
352</div> 377</div>
353</div> 378</div>
354<div class="section" id="news-item-distribution"> 379<div class="section" id="news-item-distribution">
355<h2><a class="toc-backref" href="#id32" name="news-item-distribution">News Item Distribution</a></h2> 380<h2><a class="toc-backref" href="#id33" name="news-item-distribution">News Item Distribution</a></h2>
356<div class="section" id="server-side"> 381<div class="section" id="server-side">
357<h3><a class="toc-backref" href="#id33" name="server-side">Server Side</a></h3> 382<h3><a class="toc-backref" href="#id34" name="server-side">Server Side</a></h3>
358<p>News items are to be made available via the standard rsync tree. This removes 383<p>News items are to be made available via the standard rsync tree. This removes
359any need for polling of a remote source.</p> 384any need for polling of a remote source.</p>
360<p>A new repository will be created for news items. The type (CVS or Subversion), 385<p>A new repository will be created for news items. The type (CVS or Subversion),
361location and access controls on this repository are beyond the scope of this 386location and access controls on this repository are beyond the scope of this
362GLEP.</p> 387GLEP.</p>
… …
374merging these items is beyond the scope of this GLEP — a similar setup is 399merging these items is beyond the scope of this GLEP — a similar setup is
375already used for merging GLSAs into the rsync tree.</p> 400already used for merging GLSAs into the rsync tree.</p>
376<p>The main rsync tree will <strong>not</strong> use the <tt class="docutils literal"><span class="pre">yyyy/mm/</span></tt> subdirectory layout.</p> 401<p>The main rsync tree will <strong>not</strong> use the <tt class="docutils literal"><span class="pre">yyyy/mm/</span></tt> subdirectory layout.</p>
377</div> 402</div>
378<div class="section" id="client-side"> 403<div class="section" id="client-side">
379<h3><a class="toc-backref" href="#id34" name="client-side">Client Side</a></h3> 404<h3><a class="toc-backref" href="#id35" name="client-side">Client Side</a></h3>
380<p>Whenever relevant unread news items are found, the package manager will create a 405<p>Whenever relevant unread news items are found, the package manager will create a
381file named <tt class="docutils literal"><span class="pre">/var/lib/gentoo/news/news-magic-chicken.unread</span></tt> (if it does not 406file named <tt class="docutils literal"><span class="pre">/var/lib/gentoo/news/news-repoid.unread</span></tt> (if it does not
382already exist) and append the news item identifier (eg 407already exist) and append the news item identifier (eg
383<tt class="docutils literal"><span class="pre">2005-11-01-yoursql-updates</span></tt>) on a new line.</p> 408<tt class="docutils literal"><span class="pre">2005-11-01-yoursql-updates</span></tt>) on a new line.</p>
384<div class="note">
385<p class="first admonition-title">Note</p>
386<p class="last">Future changes to Portage involving support for multiple repositories
387may introduce repository names. In this case, the <tt class="docutils literal"><span class="pre">magic-chicken</span></tt> part of the
388filename should be replaced by a string representation of the repository
389name. Thus, news item clients should use a wildcard rather than hardcoding
390the <tt class="docutils literal"><span class="pre">magic-chicken</span></tt> string.</p>
391</div>
392<p>Notification that new relevant news items will be displayed via the 409<p>Notification that new relevant news items will be displayed via the
393<tt class="docutils literal"><span class="pre">emerge</span></tt> tool in a similar way to the existing &quot;configuration files need 410<tt class="docutils literal"><span class="pre">emerge</span></tt> tool in a similar way to the existing &quot;configuration files need
394updating&quot; messages:</p> 411updating&quot; messages:</p>
395<pre class="literal-block"> 412<pre class="literal-block">
396* Important: there are 5 unread news items. 413* Important: there are 5 unread news items.
… …
405</ul> 422</ul>
406<p>The package manager may use a timestamp check file to avoid having to process 423<p>The package manager may use a timestamp check file to avoid having to process
407news items unnecessarily.</p> 424news items unnecessarily.</p>
408<p>The package manager must keep track of news items that have already been added 425<p>The package manager must keep track of news items that have already been added
409to the unread list to avoid repeatedly marking a deleted news item. This could 426to the unread list to avoid repeatedly marking a deleted news item. This could
410be handled via a <tt class="docutils literal"><span class="pre">news-magic-chicken.skip</span></tt> file, but implementation is not 427be handled via a <tt class="docutils literal"><span class="pre">news-repoid.skip</span></tt> file containing the IDs of news items that
428have already been added to a <tt class="docutils literal"><span class="pre">news-repoid.unread</span></tt> file, but this method is not
411specified by this GLEP.</p> 429required by this GLEP.</p>
412<p>Users who really don't care about news items can use <tt class="docutils literal"><span class="pre">rsync_excludes</span></tt> to 430<p>Users who really don't care about news items can use <tt class="docutils literal"><span class="pre">rsync_excludes</span></tt> to
413filter out the <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory.</p> 431filter out the <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory.</p>
414</div> 432</div>
415</div> 433</div>
416<div class="section" id="news-item-clients"> 434<div class="section" id="news-item-clients">
417<h2><a class="toc-backref" href="#id35" name="news-item-clients">News Item Clients</a></h2> 435<h2><a class="toc-backref" href="#id36" name="news-item-clients">News Item Clients</a></h2>
418<p>Once a news item is marked for reading, third party tools (or traditional core 436<p>Once a news item is marked for reading, third party tools (or traditional core
419Unix tools) can be used to display and view the news files.</p> 437Unix tools) can be used to display and view the news files.</p>
420<p>When a news item is read, its name should be removed from the 438<p>When a news item is read, its name should be removed from the
421<tt class="docutils literal"><span class="pre">news-magic-chicken.unread</span></tt> file. If a news client acts as an interactive 439<tt class="docutils literal"><span class="pre">news-repoid.unread</span></tt> file. If a news client acts as an interactive reader
422reader rather than a gateway, it should then add the name to a 440rather than a gateway, it should then add the name to a <tt class="docutils literal"><span class="pre">news-repoid.read</span></tt>
423<tt class="docutils literal"><span class="pre">news-magic-chicken.read</span></tt> file in the same directory with the same file 441file in the same directory with the same file format.</p>
424format (again, <tt class="docutils literal"><span class="pre">magic-chicken</span></tt> should be a wildcard rather than hardcoded).</p>
425<p>An <tt class="docutils literal"><span class="pre">eselect</span></tt> <a class="footnote-reference" href="#eselect" id="id15" name="id15">[3]</a> module shall be created as the 'suggested' display 442<p>An <tt class="docutils literal"><span class="pre">eselect</span></tt> <a class="footnote-reference" href="#eselect" id="id15" name="id15">[3]</a> module shall be created as the 'suggested' display
426tool; other display tools (for example, a news to email forwarder, which would 443tool; other display tools (for example, a news to email forwarder, which would
427be ideal for users who sync on a <tt class="docutils literal"><span class="pre">cron</span></tt>) are left as options for those who 444be ideal for users who sync on a <tt class="docutils literal"><span class="pre">cron</span></tt>) are left as options for those who
428desire them.</p> 445desire them.</p>
429</div> 446</div>
430<div class="section" id="news-item-removal"> 447<div class="section" id="news-item-removal">
431<h2><a class="toc-backref" href="#id36" name="news-item-removal">News Item Removal</a></h2> 448<h2><a class="toc-backref" href="#id37" name="news-item-removal">News Item Removal</a></h2>
432<p>News items can be removed (by removing the news file from the main tree) when 449<p>News items can be removed (by removing the news file from the main tree) when
433they are no longer relevant, if they are made obsolete by a future news item or 450they are no longer relevant, if they are made obsolete by a future news item or
434after a long period of time. This is the same as the method used for <tt class="docutils literal"><span class="pre">updates</span></tt> 451after a long period of time. This is the same as the method used for <tt class="docutils literal"><span class="pre">updates</span></tt>
435entries.</p> 452entries.</p>
436</div> 453</div>
437</div> 454</div>
438<div class="section" id="integration-with-existing-systems"> 455<div class="section" id="integration-with-existing-systems">
439<h1><a class="toc-backref" href="#id37" name="integration-with-existing-systems">Integration with Existing Systems</a></h1> 456<h1><a class="toc-backref" href="#id38" name="integration-with-existing-systems">Integration with Existing Systems</a></h1>
440<p>It would be simple to convert these news items into the format used for news 457<p>It would be simple to convert these news items into the format used for news
441items on the Gentoo website or posts for the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list.</p> 458items on the Gentoo website or posts for the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list.</p>
442<p>There is an existing automated tool <a class="footnote-reference" href="#forums-glsa" id="id16" name="id16">[4]</a> for posting GLSAs to the 459<p>There is an existing automated tool <a class="footnote-reference" href="#forums-glsa" id="id16" name="id16">[4]</a> for posting GLSAs to the
443forums. A similar tool can be used for these news items.</p> 460forums. A similar tool can be used for these news items.</p>
444</div> 461</div>
445<div class="section" id="backwards-compatibility"> 462<div class="section" id="backwards-compatibility">
446<h1><a class="toc-backref" href="#id38" name="backwards-compatibility">Backwards Compatibility</a></h1> 463<h1><a class="toc-backref" href="#id39" name="backwards-compatibility">Backwards Compatibility</a></h1>
447<p>Backwards compatibility is not a concern here. Existing tools will simply ignore 464<p>Backwards compatibility is not a concern here. Existing tools will simply ignore
448the <tt class="docutils literal"><span class="pre">news/</span></tt> directory.</p> 465the <tt class="docutils literal"><span class="pre">news/</span></tt> directory.</p>
449</div> 466</div>
450<div class="section" id="reference-implementation"> 467<div class="section" id="reference-implementation">
451<h1><a class="toc-backref" href="#id39" name="reference-implementation">Reference Implementation</a></h1> 468<h1><a class="toc-backref" href="#id40" name="reference-implementation">Reference Implementation</a></h1>
452<div class="section" id="portage-code"> 469<div class="section" id="portage-code">
453<h2><a class="toc-backref" href="#id40" name="portage-code">Portage Code</a></h2> 470<h2><a class="toc-backref" href="#id41" name="portage-code">Portage Code</a></h2>
454<p>TODO</p> 471<p>TODO</p>
455</div> 472</div>
456<div class="section" id="simple-eselect-news-client"> 473<div class="section" id="simple-eselect-news-client">
457<h2><a class="toc-backref" href="#id41" name="simple-eselect-news-client">Simple <tt class="docutils literal docutils literal"><span class="pre">eselect</span></tt> News Client</a></h2> 474<h2><a class="toc-backref" href="#id42" name="simple-eselect-news-client">Simple <tt class="docutils literal docutils literal"><span class="pre">eselect</span></tt> News Client</a></h2>
458<p>TODO Removed until the exact format details are figured out.</p> 475<p>TODO Removed until the exact format details are figured out.</p>
459</div> 476</div>
460<div class="section" id="simple-news-to-mail-forwarder"> 477<div class="section" id="simple-news-to-mail-forwarder">
461<h2><a class="toc-backref" href="#id42" name="simple-news-to-mail-forwarder">Simple News to Mail Forwarder</a></h2> 478<h2><a class="toc-backref" href="#id43" name="simple-news-to-mail-forwarder">Simple News to Mail Forwarder</a></h2>
462<p>TODO Removed until the exact format details are figured out.</p> 479<p>TODO Removed until the exact format details are figured out.</p>
463</div> 480</div>
464</div> 481</div>
465<div class="section" id="credits"> 482<div class="section" id="credits">
466<h1><a class="toc-backref" href="#id43" name="credits">Credits</a></h1> 483<h1><a class="toc-backref" href="#id44" name="credits">Credits</a></h1>
467<p>The idea behind notifying users of news updates via Portage comes from Stuart 484<p>The idea behind notifying users of news updates via Portage comes from Stuart
468Herbert <a class="footnote-reference" href="#stuart-blog" id="id17" name="id17">[15]</a>.</p> 485Herbert <a class="footnote-reference" href="#stuart-blog" id="id17" name="id17">[15]</a>.</p>
469<p>Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear, 486<p>Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear,
470Brian Harring, Dan Meltzer, Jason Stubbs, Paul de Vrieze and Alec Warner for 487Brian Harring, Dan Meltzer, Jason Stubbs, Paul de Vrieze and Alec Warner for
471input. Some of the ideas presented here are theirs, others go completely 488input. Some of the ideas presented here are theirs, others go completely
472against their suggestions.</p> 489against their suggestions.</p>
473</div> 490</div>
474<div class="section" id="example-files"> 491<div class="section" id="example-files">
475<h1><a class="toc-backref" href="#id44" name="example-files">Example Files</a></h1> 492<h1><a class="toc-backref" href="#id45" name="example-files">Example Files</a></h1>
476<p>TODO Removed until the exact format details are figured out.</p> 493<p>TODO Removed until the exact format details are figured out.</p>
477</div> 494</div>
478<div class="section" id="references"> 495<div class="section" id="references">
479<h1><a class="toc-backref" href="#id45" name="references">References</a></h1> 496<h1><a class="toc-backref" href="#id46" name="references">References</a></h1>
480<table class="docutils footnote" frame="void" id="bug-11359" rules="none"> 497<table class="docutils footnote" frame="void" id="bug-11359" rules="none">
481<colgroup><col class="label" /><col /></colgroup> 498<colgroup><col class="label" /><col /></colgroup>
482<tbody valign="top"> 499<tbody valign="top">
483<tr><td class="label"><a class="fn-backref" href="#id1" name="bug-11359">[1]</a></td><td>Bugzilla Bug 11359 500<tr><td class="label"><a class="fn-backref" href="#id1" name="bug-11359">[1]</a></td><td>Bugzilla Bug 11359
484&quot;[NEW FEATURE] pkg_postinst/pkg_preinst ewarn/einfo logging&quot;, 501&quot;[NEW FEATURE] pkg_postinst/pkg_preinst ewarn/einfo logging&quot;,
… …
512<tbody valign="top"> 529<tbody valign="top">
513<tr><td class="label"><a name="forums-apache2">[5]</a></td><td><em>(<a class="fn-backref" href="#id2">1</a>, <a class="fn-backref" href="#id3">2</a>)</em> Forums thread &quot;Gentoo Apache2 Config Change Idiocy&quot;, 530<tr><td class="label"><a name="forums-apache2">[5]</a></td><td><em>(<a class="fn-backref" href="#id2">1</a>, <a class="fn-backref" href="#id3">2</a>)</em> Forums thread &quot;Gentoo Apache2 Config Change Idiocy&quot;,
514<a class="reference" href="http://forums.gentoo.org/viewtopic-t-384368.html">http://forums.gentoo.org/viewtopic-t-384368.html</a></td></tr> 531<a class="reference" href="http://forums.gentoo.org/viewtopic-t-384368.html">http://forums.gentoo.org/viewtopic-t-384368.html</a></td></tr>
515</tbody> 532</tbody>
516</table> 533</table>
517<table class="docutils footnote" frame="void" id="glep-1" rules="none">
518<colgroup><col class="label" /><col /></colgroup>
519<tbody valign="top">
520<tr><td class="label"><a class="fn-backref" href="#id11" name="glep-1">[6]</a></td><td>GLEP 1: &quot;GLEP Purpose and Guidelines&quot;, Grant Goodyear,
521<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0001.html">http://www.gentoo.org/proj/en/glep/glep-0001.html</a></td></tr>
522</tbody>
523</table>
524<table class="docutils footnote" frame="void" id="glep-22" rules="none"> 534<table class="docutils footnote" frame="void" id="glep-22" rules="none">
525<colgroup><col class="label" /><col /></colgroup> 535<colgroup><col class="label" /><col /></colgroup>
526<tbody valign="top"> 536<tbody valign="top">
527<tr><td class="label"><a class="fn-backref" href="#id12" name="glep-22">[7]</a></td><td>GLEP 22: &quot;New &quot;keyword&quot; system to incorporate various 537<tr><td class="label"><a class="fn-backref" href="#id12" name="glep-22">[6]</a></td><td>GLEP 22: &quot;New &quot;keyword&quot; system to incorporate various
528userlands/kernels/archs&quot;, Grant Goodyear, 538userlands/kernels/archs&quot;, Grant Goodyear,
529<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0022.html">http://www.gentoo.org/proj/en/glep/glep-0022.html</a></td></tr> 539<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0022.html">http://www.gentoo.org/proj/en/glep/glep-0022.html</a></td></tr>
530</tbody> 540</tbody>
531</table> 541</table>
532<table class="docutils footnote" frame="void" id="glep-31" rules="none"> 542<table class="docutils footnote" frame="void" id="glep-31" rules="none">
533<colgroup><col class="label" /><col /></colgroup> 543<colgroup><col class="label" /><col /></colgroup>
534<tbody valign="top"> 544<tbody valign="top">
535<tr><td class="label"><a class="fn-backref" href="#id9" name="glep-31">[8]</a></td><td>GLEP 31: &quot;Character Sets for Portage Tree Items&quot;, Ciaran 545<tr><td class="label"><a class="fn-backref" href="#id9" name="glep-31">[7]</a></td><td>GLEP 31: &quot;Character Sets for Portage Tree Items&quot;, Ciaran
536McCreesh, 546McCreesh,
537<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0031.html">http://www.gentoo.org/proj/en/glep/glep-0031.html</a></td></tr> 547<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0031.html">http://www.gentoo.org/proj/en/glep/glep-0031.html</a></td></tr>
538</tbody> 548</tbody>
539</table> 549</table>
540<table class="docutils footnote" frame="void" id="glep-34" rules="none"> 550<table class="docutils footnote" frame="void" id="glep-34" rules="none">
541<colgroup><col class="label" /><col /></colgroup> 551<colgroup><col class="label" /><col /></colgroup>
542<tbody valign="top"> 552<tbody valign="top">
543<tr><td class="label"><a class="fn-backref" href="#id6" name="glep-34">[9]</a></td><td>GLEP 34: &quot;Per-Category metadata.xml Files&quot;, Ciaran McCreesh, 553<tr><td class="label"><a class="fn-backref" href="#id6" name="glep-34">[8]</a></td><td>GLEP 34: &quot;Per-Category metadata.xml Files&quot;, Ciaran McCreesh,
544<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0034.html">http://www.gentoo.org/proj/en/glep/glep-0034.html</a></td></tr> 554<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0034.html">http://www.gentoo.org/proj/en/glep/glep-0034.html</a></td></tr>
545</tbody> 555</tbody>
546</table> 556</table>
547<table class="docutils footnote" frame="void" id="glep-36" rules="none"> 557<table class="docutils footnote" frame="void" id="glep-36" rules="none">
548<colgroup><col class="label" /><col /></colgroup> 558<colgroup><col class="label" /><col /></colgroup>
549<tbody valign="top"> 559<tbody valign="top">
550<tr><td class="label"><a class="fn-backref" href="#id4" name="glep-36">[10]</a></td><td>GLEP 36: &quot;Subversion/CVS for Gentoo Hosted Projects&quot;, Aaron 560<tr><td class="label"><a class="fn-backref" href="#id4" name="glep-36">[9]</a></td><td>GLEP 36: &quot;Subversion/CVS for Gentoo Hosted Projects&quot;, Aaron
551Walker, 561Walker,
552<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0036.html">http://www.gentoo.org/proj/en/glep/glep-0036.html</a></td></tr> 562<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0036.html">http://www.gentoo.org/proj/en/glep/glep-0036.html</a></td></tr>
563</tbody>
564</table>
565<table class="docutils footnote" frame="void" id="glep-45" rules="none">
566<colgroup><col class="label" /><col /></colgroup>
567<tbody valign="top">
568<tr><td class="label"><a class="fn-backref" href="#id11" name="glep-45">[10]</a></td><td>GLEP 45: &quot;GLEP date format&quot;, Henrik Brix Andersen,
569<a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0045.html">http://www.gentoo.org/proj/en/glep/glep-0045.html</a></td></tr>
553</tbody> 570</tbody>
554</table> 571</table>
555<table class="docutils footnote" frame="void" id="iso-639" rules="none"> 572<table class="docutils footnote" frame="void" id="iso-639" rules="none">
556<colgroup><col class="label" /><col /></colgroup> 573<colgroup><col class="label" /><col /></colgroup>
557<tbody valign="top"> 574<tbody valign="top">
… …
592<tr><td class="label"><a class="fn-backref" href="#id19" name="id18">[16]</a></td><td><a class="reference" href="glep-0042-extras/example-news-item.txt">glep-0042-extras/example-news-item.txt</a></td></tr> 609<tr><td class="label"><a class="fn-backref" href="#id19" name="id18">[16]</a></td><td><a class="reference" href="glep-0042-extras/example-news-item.txt">glep-0042-extras/example-news-item.txt</a></td></tr>
593</tbody> 610</tbody>
594</table> 611</table>
595</div> 612</div>
596<div class="section" id="copyright"> 613<div class="section" id="copyright">
597<h1><a class="toc-backref" href="#id46" name="copyright">Copyright</a></h1> 614<h1><a class="toc-backref" href="#id47" name="copyright">Copyright</a></h1>
598<p>This document has been placed in the public domain.</p> 615<p>This document has been placed in the public domain.</p>
599<!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : --> 616<!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : -->
600</div> 617</div>
601 618
602</div> 619</div>
603<div class="footer"> 620<div class="footer">
604<hr class="footer" /> 621<hr class="footer" />
605<a class="reference" href="glep-0042.txt">View document source</a>. 622<a class="reference" href="glep-0042.txt">View document source</a>.
606Generated on: 2005-12-13 03:21 UTC. 623Generated on: 2005-12-18 04:15 UTC.
607Generated 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. 624Generated 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.
608 625
609</div> 626</div>
610</body> 627</body>
611</html> 628</html>
Legend:
Removed from v.1.5  
changed lines
  Added in v.1.6
  ViewVC Help
Powered by ViewVC 1.1.13