/[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.1 Revision 1.5
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">1.1</td> 35<tr class="field"><th class="field-name">Version:</th><td class="field-body">$Revision: 1.5 $</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">2005/11/05 03:32:09</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/13 03:21:59 $</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-October-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-Date:</th><td class="field-body">1-November-2005, 5-November-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</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">
55<p class="topic-title first"><a name="contents">Contents</a></p> 55<p class="topic-title first"><a name="contents">Contents</a></p>
56<ul class="simple"> 56<ul class="simple">
57<li><a class="reference" href="#abstract" id="id14" name="id14">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="id15" name="id15">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="id16" name="id16">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="id17" name="id17">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="id18" name="id18">Overview</a></li> 61<li><a class="reference" href="#overview" id="id24" name="id24">Overview</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-directories" id="id26" name="id26">News Item Directories</a></li>
62<li><a class="reference" href="#news-item-file-format" id="id19" name="id19">News Item File Format</a><ul> 64<li><a class="reference" href="#news-item-files" id="id27" name="id27">News Item Files</a><ul>
63<li><a class="reference" href="#news-item-headers" id="id20" name="id20">News Item Headers</a></li> 65<li><a class="reference" href="#news-item-headers" id="id28" name="id28">News Item Headers</a></li>
64<li><a class="reference" href="#news-item-body" id="id21" name="id21">News Item Body</a></li> 66<li><a class="reference" href="#news-item-body" id="id29" name="id29">News Item Body</a></li>
65<li><a class="reference" href="#example-news-item" id="id22" name="id22">Example News Item</a></li> 67<li><a class="reference" href="#example-news-item" id="id30" name="id30">Example News Item</a></li>
66</ul> 68</ul>
67</li> 69</li>
68<li><a class="reference" href="#news-item-quality-control" id="id23" name="id23">News Item Quality Control</a></li> 70<li><a class="reference" href="#news-item-quality-control" id="id31" name="id31">News Item Quality Control</a></li>
69<li><a class="reference" href="#news-item-distribution" id="id24" name="id24">News Item Distribution</a><ul> 71<li><a class="reference" href="#news-item-distribution" id="id32" name="id32">News Item Distribution</a><ul>
70<li><a class="reference" href="#server-side" id="id25" name="id25">Server Side</a></li> 72<li><a class="reference" href="#server-side" id="id33" name="id33">Server Side</a></li>
71<li><a class="reference" href="#client-side" id="id26" name="id26">Client Side</a></li> 73<li><a class="reference" href="#client-side" id="id34" name="id34">Client Side</a></li>
72</ul> 74</ul>
73</li> 75</li>
74<li><a class="reference" href="#news-item-clients" id="id27" name="id27">News Item Clients</a></li> 76<li><a class="reference" href="#news-item-clients" id="id35" name="id35">News Item Clients</a></li>
75<li><a class="reference" href="#news-item-removal" id="id28" name="id28">News Item Removal</a></li> 77<li><a class="reference" href="#news-item-removal" id="id36" name="id36">News Item Removal</a></li>
76</ul> 78</ul>
77</li> 79</li>
78<li><a class="reference" href="#integration-with-existing-systems" id="id29" name="id29">Integration with Existing Systems</a></li> 80<li><a class="reference" href="#integration-with-existing-systems" id="id37" name="id37">Integration with Existing Systems</a></li>
79<li><a class="reference" href="#backwards-compatibility" id="id30" name="id30">Backwards Compatibility</a></li> 81<li><a class="reference" href="#backwards-compatibility" id="id38" name="id38">Backwards Compatibility</a></li>
80<li><a class="reference" href="#reference-implementation" id="id31" name="id31">Reference Implementation</a><ul> 82<li><a class="reference" href="#reference-implementation" id="id39" name="id39">Reference Implementation</a><ul>
81<li><a class="reference" href="#portage-code" id="id32" name="id32">Portage Code</a></li> 83<li><a class="reference" href="#portage-code" id="id40" name="id40">Portage Code</a></li>
82<li><a class="reference" href="#simple-eselect-news-client" id="id33" name="id33">Simple <tt class="docutils literal"><span class="pre">eselect</span></tt> News Client</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>
83<li><a class="reference" href="#simple-news-to-mail-forwarder" id="id34" name="id34">Simple News to Mail Forwarder</a></li> 85<li><a class="reference" href="#simple-news-to-mail-forwarder" id="id42" name="id42">Simple News to Mail Forwarder</a></li>
84</ul> 86</ul>
85</li> 87</li>
86<li><a class="reference" href="#credits" id="id35" name="id35">Credits</a></li> 88<li><a class="reference" href="#credits" id="id43" name="id43">Credits</a></li>
89<li><a class="reference" href="#example-files" id="id44" name="id44">Example Files</a></li>
87<li><a class="reference" href="#references" id="id36" name="id36">References</a></li> 90<li><a class="reference" href="#references" id="id45" name="id45">References</a></li>
88<li><a class="reference" href="#copyright" id="id37" name="id37">Copyright</a></li> 91<li><a class="reference" href="#copyright" id="id46" name="id46">Copyright</a></li>
89</ul> 92</ul>
90</div> 93</div>
91<div class="section" id="abstract"> 94<div class="section" id="abstract">
92<h1><a class="toc-backref" href="#id14" name="abstract">Abstract</a></h1> 95<h1><a class="toc-backref" href="#id20" name="abstract">Abstract</a></h1>
93<p>This GLEP proposes a new way of informing users about important updates and news 96<p>This GLEP proposes a new way of informing users about important updates and news
94regarding tree-related items.</p> 97regarding tree-related items.</p>
95</div> 98</div>
96<div class="section" id="motivation"> 99<div class="section" id="motivation">
97<h1><a class="toc-backref" href="#id15" name="motivation">Motivation</a></h1> 100<h1><a class="toc-backref" href="#id21" name="motivation">Motivation</a></h1>
98<p>There are currently several ways of getting news out to our users, none of them 101<p>Although most package updates are clean and require little user action,
99particularly effective:</p> 102occasionally an upgrade requires user intervention during the upgrade process.
103Recent examples of the latter include the <tt class="docutils literal"><span class="pre">gcc-3.4</span></tt> stabilisation on <tt class="docutils literal"><span class="pre">x86</span></tt>
104and the <tt class="docutils literal"><span class="pre">mysql-4.1</span></tt> database format changes.</p>
105<p>There are currently several ways of delivering important news items to our
106users, none of them particularly effective:</p>
100<ul class="simple"> 107<ul class="simple">
101<li>Gentoo Weekly News</li> 108<li>Gentoo Weekly News</li>
102<li>The <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list</li> 109<li>The <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt>, <tt class="docutils literal"><span class="pre">gentoo-user</span></tt> and <tt class="docutils literal"><span class="pre">gentoo-dev</span></tt> mailing lists</li>
103<li>The Gentoo Forums</li> 110<li>The Gentoo Forums</li>
104<li>The main Gentoo website</li> 111<li>The main Gentoo website</li>
105<li>RSS feeds of Gentoo news</li> 112<li>RSS feeds of Gentoo news</li>
113<li><tt class="docutils literal"><span class="pre">einfo</span></tt> and <tt class="docutils literal"><span class="pre">ewarn</span></tt> messages in <tt class="docutils literal"><span class="pre">pkg_setup</span></tt> or <tt class="docutils literal"><span class="pre">pkg_postinst</span></tt></li>
106</ul> 114</ul>
107<p>A more reliable way of getting news of critical updates out to users is required 115<p>A more reliable way of getting news of critical updates out to users is required
108to avoid repeats of the various recent upgrade debacles. This GLEP proposes a 116to avoid repeats of the various recent upgrade debacles. This GLEP proposes a
109solution based around pushing news items out to the user via the <tt class="docutils literal"><span class="pre">rsync</span></tt> tree.</p> 117solution based around pushing news items out to the user via the <tt class="docutils literal"><span class="pre">rsync</span></tt> tree.</p>
118<div class="important">
119<p class="first admonition-title">Important</p>
120<p class="last">This GLEP does not seek to replace or modify <tt class="docutils literal"><span class="pre">einfo</span></tt> messages
121which are displayed post-install. That is a separate issue which is handled
122by <tt class="docutils literal"><span class="pre">elog</span></tt> <a class="footnote-reference" href="#bug-11359" id="id1" name="id1">[1]</a>.</p>
123</div>
110</div> 124</div>
111<div class="section" id="requirements"> 125<div class="section" id="requirements">
112<h1><a class="toc-backref" href="#id16" name="requirements">Requirements</a></h1> 126<h1><a class="toc-backref" href="#id22" name="requirements">Requirements</a></h1>
113<p>An adequate solution must meet all of the following requirements:</p> 127<p>An adequate solution must meet all of the following requirements:</p>
114<dl class="docutils"> 128<dl class="docutils">
115<dt>Preemptive</dt> 129<dt>Preemptive</dt>
116<dd>Users should be told of changes <em>before</em> they break the user's system, 130<dd>Users should be told of changes <em>before</em> they break a system, not after the
117after the damage has already been done.</dd> 131damage has already been done. Ideally, the system administrator would be
132given ample warning to plan difficult upgrades and changes, rather than only
133being told just before action is necessary.</dd>
118<dt>No user subscription required</dt> 134<dt>No user subscription required</dt>
119<dd>It has already been demonstrated <a class="footnote-reference" href="#forums-whining" id="id1" name="id1">[4]</a> that many users do not 135<dd>It has already been demonstrated <a class="footnote-reference" href="#forums-apache2" id="id2" name="id2">[5]</a> that many users do not
120read the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list or <tt class="docutils literal"><span class="pre">RSS</span></tt> feeds. A solution which 136read the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list or <tt class="docutils literal"><span class="pre">RSS</span></tt> feeds. A solution which
121requires subscription has no advantage over current methods.</dd> 137requires subscription has no advantage over current methods.</dd>
122<dt>No user monitoring required</dt> 138<dt>No user monitoring required</dt>
123<dd>It has already been demonstrated <a class="footnote-reference" href="#forums-whining" id="id2" name="id2">[4]</a> that many users do not 139<dd>It has already been demonstrated <a class="footnote-reference" href="#forums-apache2" id="id3" name="id3">[5]</a> that many users do not
124read news items posted to the Gentoo website, or do not read news items 140read news items posted to the Gentoo website, or do not read news items
125until it is too late. A solution that relies upon active monitoring of a 141until it is too late. A solution that relies upon active monitoring of a
126particular source has no advantage over current methods.</dd> 142particular source has no advantage over current methods.</dd>
127<dt>Relevant</dt> 143<dt>Relevant</dt>
128<dd>System administrators who do not use a particular package should not have to 144<dd>System administrators who do not use a particular package should not have to
129read news items which affect purely that package. Some news items may be of 145read news items which affect purely that package. Some news items may be of
130relevance to most or all users, but those that are not should not be forced 146relevance to most or all users, but those that are not should not be forced
131upon users unnecessarily.</dd> 147upon users unnecessarily.</dd>
132<dt>Lightweight</dt> 148<dt>Lightweight</dt>
133<dd>It is not reasonable to expect all users to have an MTA, web browser, email 149<dd>It is not reasonable to expect all users to have an MTA, web browser, email
134client, cron daemon or text processing suite available on their system.</dd> 150client, cron daemon or text processing suite available on their system.
151Users must not be forced to install unreasonable extra software to be able
152to read news items.</dd>
135<dt>No privacy violations</dt> 153<dt>No privacy violations</dt>
136<dd>Users of the solution should not be required to provide information about 154<dd>Users of the solution should not be required to provide information about
137their systems (for example, IP addresses or installed packages).</dd> 155their systems (for example, IP addresses or installed packages).</dd>
138<dt>Multiple delivery method support</dt> 156<dt>Multiple delivery method support</dt>
139<dd>Some users may wish to view news items via email, some via a terminal and 157<dd>Some users may wish to view news items via email, some via a terminal and
140some via a web browser. A solution should either support all of these 158some via a web browser. A solution should either support all of these
141methods or (better still) make it trivial to write clients for displaying 159methods or (better still) make it simple to write clients for displaying
142news items in different ways.</dd> 160news items in different ways.</dd>
143</dl> 161</dl>
144<p>The following characteristics would be desirable:</p> 162<p>The following characteristics would be desirable:</p>
145<dl class="docutils"> 163<dl class="docutils">
146<dt>Internationalisable</dt> 164<dt>Internationalisable</dt>
147<dd>Being able to provide messages in multiple languages may be beneficial.</dd> 165<dd>Being able to provide messages in multiple languages may be beneficial.</dd>
148<dt>Quality control</dt> 166<dt>Quality control</dt>
149<dd>There should be some way to ensure that badly written or irrelevant messages 167<dd>There should be some way to ensure that badly written or irrelevant messages
150are not sent out, for example by inexperienced developers, those whose 168are not sent out, for example by inexperienced developers or those whose
151English language skills are below par or morons.</dd> 169English language skills are below par.</dd>
152<dt>Simple for developers</dt> 170<dt>Simple for developers</dt>
153<dd>Posting news items should be as simple as is reasonably possible.</dd> 171<dd>Posting news items should be as simple as is reasonably possible.</dd>
154<dt>Simple for users</dt> 172<dt>Simple for users</dt>
155<dd>Reading relevant news items should be as simple as is reasonably possible.</dd> 173<dd>Reading relevant news items should be as simple as is reasonably possible.</dd>
156<dt>Compatibility with existing and future news sources</dt> 174<dt>Compatibility with existing and future news sources</dt>
159excessive difficulty. Similarly, easy interoperation with any future news 177excessive difficulty. Similarly, easy interoperation with any future news
160sources should not be precluded.</dd> 178sources should not be precluded.</dd>
161</dl> 179</dl>
162</div> 180</div>
163<div class="section" id="specification"> 181<div class="section" id="specification">
164<h1><a class="toc-backref" href="#id17" name="specification">Specification</a></h1> 182<h1><a class="toc-backref" href="#id23" name="specification">Specification</a></h1>
165<div class="section" id="overview"> 183<div class="section" id="overview">
166<h2><a class="toc-backref" href="#id18" name="overview">Overview</a></h2> 184<h2><a class="toc-backref" href="#id24" name="overview">Overview</a></h2>
167<p>News items are published and delivered to users as follows:</p> 185<p>News items are published and delivered to users as follows:</p>
168<ol class="arabic simple"> 186<ol class="arabic simple">
169<li>A news item is written. The format to be used is described in 187<li>A news item is written. The format to be used is described below.</li>
170<a class="reference" href="#news-item-file-format">News Item File Format</a>.</li>
171<li>The news item is reviewed, following the process described in 188<li>The news item is reviewed, following the process described in
172<a class="reference" href="#news-item-quality-control">News Item Quality Control</a>.</li> 189<a class="reference" href="#news-item-quality-control">News Item Quality Control</a>.</li>
173<li>The news item is committed to a CVS (or Subversion <a class="footnote-reference" href="#glep-36" id="id3" name="id3">[8]</a>) repository. 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.
174From here, it is merged with the rsync tree. This is described in <a class="reference" href="#news-item-distribution">News Item 191From here, it is merged with the rsync tree. This is described in <a class="reference" href="#news-item-distribution">News Item
175Distribution</a>.</li> 192Distribution</a>.</li>
176<li>The news item is merged with the rsync tree. Implementation details of this
177point are beyond the scope of this GLEP; existing solutions are in place
178for merging GLSAs to the tree.</li>
179<li>Users fetch the news item when they sync. This ensures that the news items in 193<li>Users fetch the news item when they sync. This ensures that the news items in
180question are pushed to the user before the user accidentally makes an 194question are pushed to the user before the user accidentally makes an
181unwanted change. No changes to the existing rsync process are required by 195unwanted change. No changes to the existing rsync process are required by
182this GLEP.</li> 196this GLEP.</li>
183<li>Portage filters the news item and, if it is relevant, installs it in a 197<li>The package manager filters the news item and, if it is relevant, marks the
184special location to be read by a news item reader. Messages are also 198news item for reading. The package manager should also display a notice
185displayed to inform the user that news is available.</li> 199informing the user that there are unread news items.</li>
186<li>The news item is handled by the user's choice of news item reader. See <a class="reference" href="#news-item-clients">News 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
187Item Clients</a>.</li> 201Item Clients</a>.</li>
188</ol> 202</ol>
189</div> 203</div>
204<div class="section" id="news-item-identities">
205<h2><a class="toc-backref" href="#id25" 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
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>),
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
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
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>,
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>
212</div>
213<div class="section" id="news-item-directories">
214<h2><a class="toc-backref" href="#id26" 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
216news 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
218contains 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>
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
221provided. 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>
223</div>
190<div class="section" id="news-item-file-format"> 224<div class="section" id="news-item-files">
191<h2><a class="toc-backref" href="#id19" name="news-item-file-format">News Item File Format</a></h2> 225<h2><a class="toc-backref" href="#id27" name="news-item-files">News Item Files</a></h2>
192<p>Each news item will be represented by a single text file. This file will be 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
193encoded using UTF-8 for compatibility with and for the same reason as existing 227compatibility with and for the same reasons as existing Gentoo documentation
194Gentoo documentation <a class="footnote-reference" href="#docs-policy" id="id4" name="id4">[1]</a> and tree <a class="footnote-reference" href="#glep-31" id="id5" name="id5">[6]</a> practices.</p> 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>
195<p>The news item will be named in the form <tt class="docutils literal"><span class="pre">yyyy-mm-dd-item-name.en.txt</span></tt>, where 229<p>News items should be signed with a detached GPG signature:</p>
196<tt class="docutils literal"><span class="pre">item-name</span></tt> is a very short name (e.g. <tt class="docutils literal"><span class="pre">apache-updates</span></tt>) and <tt class="docutils literal"><span class="pre">en</span></tt> is the 230<pre class="literal-block">
197two letter ISO 639 <a class="footnote-reference" href="#iso-639" id="id6" name="id6">[9]</a> language code for the news item. The short name 231gpg --armour --detach-sign ????-??-??-*.??.txt
198must consist only of characters <tt class="docutils literal"><span class="pre">a-z</span></tt>, <tt class="docutils literal"><span class="pre">A-Z</span></tt>, <tt class="docutils literal"><span class="pre">0-9</span></tt> and <tt class="docutils literal"><span class="pre">-</span></tt> (hyphen).</p> 232</pre>
199<p>News items may be signed using GPG. If this is done, a detached signature should
200be used.</p>
201<p>The directory and file name rules are designed specifically to allow easy
202sorting by date.</p>
203<p>An English (<tt class="docutils literal"><span class="pre">en</span></tt>) version must be available for all news items. Other
204languages may be provided either by the original author or by other translators
205who have commit access. This anglocentricity is justified on the grounds that
206nobody objected to it with GLEP 34 <a class="footnote-reference" href="#glep-34" id="id7" name="id7">[7]</a>.</p>
207<p>A news item's content will consist of an <a class="reference" href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> <a class="footnote-reference" href="#rfc-822" id="id8" name="id8">[11]</a> style header 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>
208followed by the main body of the message as plain text. This GLEP defines 234followed by the main body of the message as plain text. This GLEP defines
209various optional and mandatory headers. Future GLEPs may propose new headers -- 235various optional and mandatory headers. Future GLEPs may propose new headers
210tools handling these news items must ignore any unrecognised header.</p> 236tools handling these news items must ignore any unrecognised header.</p>
211<div class="section" id="news-item-headers"> 237<div class="section" id="news-item-headers">
212<h3><a class="toc-backref" href="#id20" name="news-item-headers">News Item Headers</a></h3> 238<h3><a class="toc-backref" href="#id28" name="news-item-headers">News Item Headers</a></h3>
213<p>The following headers describe the purpose and format of the news item:</p> 239<p>The following headers describe the purpose and format of the news item:</p>
214<dl class="docutils"> 240<dl class="docutils">
215<dt><tt class="docutils literal"><span class="pre">Title:</span></tt></dt> 241<dt><tt class="docutils literal"><span class="pre">Title:</span></tt></dt>
216<dd>A short (maximum 44 characters) descriptive title. Mandatory.</dd> 242<dd>A short (maximum 44 characters) descriptive title. Mandatory.</dd>
217<dt><tt class="docutils literal"><span class="pre">Author:</span></tt></dt> 243<dt><tt class="docutils literal"><span class="pre">Author:</span></tt></dt>
218<dd>Author's name and email address, in the form <tt class="docutils literal"><span class="pre">Real</span> <span class="pre">Name</span> <span class="pre">&lt;email&#64;address&gt;</span></tt>. 244<dd>Author's name and email address, in the form <tt class="docutils literal"><span class="pre">Real</span> <span class="pre">Name</span> <span class="pre">&lt;email&#64;address&gt;</span></tt>.
219Mandatory, multiple author fields may be specified if appropriate.</dd> 245Mandatory; multiple author headers may be specified if appropriate.</dd>
220<dt><tt class="docutils literal"><span class="pre">Translator:</span></tt></dt> 246<dt><tt class="docutils literal"><span class="pre">Translator:</span></tt></dt>
221<dd>For translated news items, the translator's name and email address.</dd> 247<dd>For translated news items, the translator's name and email address. Multiple
248translator headers may be specified if appropriate.</dd>
222<dt><tt class="docutils literal"><span class="pre">Content-Type:</span></tt></dt> 249<dt><tt class="docutils literal"><span class="pre">Content-Type:</span></tt></dt>
223<dd>Must be <tt class="docutils literal"><span class="pre">text/plain</span></tt>. Mandatory.</dd> 250<dd>Must be <tt class="docutils literal"><span class="pre">text/plain</span></tt>. Mandatory.</dd>
224<dt><tt class="docutils literal"><span class="pre">Posted:</span></tt></dt> 251<dt><tt class="docutils literal"><span class="pre">Posted:</span></tt></dt>
225<dd>Date of posting, in <tt class="docutils literal"><span class="pre">dd-mmm-yyyy</span></tt> format (e.g. 14-Aug-2001). UTC time in 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
226<tt class="docutils literal"><span class="pre">hh-mm-ss</span> <span class="pre">+0000</span></tt> format may also be included. This field is mandatory.</dd> 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
254may also be included. Mandatory.</dd>
227<dt><tt class="docutils literal"><span class="pre">Version:</span></tt></dt> 255<dt><tt class="docutils literal"><span class="pre">Revision:</span></tt></dt>
228<dd>Initially 1. Incremented every time a non-trivial change is made. Changes 256<dd>Initially 1. Incremented every time a non-trivial change is made. Changes
229which require a re-read of the news item should instead use a new news item 257which require a re-read of the news item should instead use a new news item
230file.</dd> 258file. Mandatory.</dd>
231<dt><tt class="docutils literal"><span class="pre">News-Item-Format:</span></tt></dt> 259<dt><tt class="docutils literal"><span class="pre">News-Item-Format:</span></tt></dt>
232<dd>Must be <tt class="docutils literal"><span class="pre">1.0</span></tt>. Future revisions to the format may increment the minor 260<dd>Must be <tt class="docutils literal"><span class="pre">1.0</span></tt>. Future revisions to the format may increment the minor
233number for backwards-compatible changes, or the major number for major 261number for backwards-compatible changes, or the major number for major
234changes.</dd> 262changes.</dd>
235</dl> 263</dl>
236<p>The following headers are used for filtering. If none of these headers are 264<p>The following headers are used for filtering:</p>
237specified, the news item is displayed for all users. Otherwise, the news item is
238displayed if <em>at least one</em> header matches.</p>
239<dl class="docutils"> 265<dl class="docutils">
240<dt><tt class="docutils literal"><span class="pre">Display-If-Installed:</span></tt></dt> 266<dt><tt class="docutils literal"><span class="pre">Display-If-Installed:</span></tt></dt>
241<dd>A dependency atom or simple package name (for example, 267<dd>A dependency atom or simple package name (for example,
242<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 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
243package specified installed, the news item should be displayed.</dd> 269package specified installed, the news item should be displayed.</dd>
244<dt><tt class="docutils literal"><span class="pre">Display-If-Keyword:</span></tt></dt> 270<dt><tt class="docutils literal"><span class="pre">Display-If-Keyword:</span></tt></dt>
245<dd>A keyword <a class="footnote-reference" href="#glep-22" id="id9" name="id9">[5]</a> name, for example <tt class="docutils literal"><span class="pre">mips</span></tt>. If the user is on the arch 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
246in question, the news item should be displayed.</dd> 272user is on the keyword in question, the news item should be displayed.</dd>
247<dt><tt class="docutils literal"><span class="pre">Display-If-Profile:</span></tt></dt> 273<dt><tt class="docutils literal"><span class="pre">Display-If-Profile:</span></tt></dt>
248<dd>A profile path, for example <tt class="docutils literal"><span class="pre">default-linux/sparc/sparc64/server</span></tt>. If the 274<dd>A profile path, for example <tt class="docutils literal"><span class="pre">default-linux/sparc/sparc64/server</span></tt>. Standard
249user is using the exact profile in question, the news item should be 275shell GLOB wildcards may be used. If the user is using the exact profile in
276question, the news item should be displayed. This header may be used to
250displayed. This header may be used to replace <tt class="docutils literal"><span class="pre">deprecated</span></tt> files in the 277replace <tt class="docutils literal"><span class="pre">deprecated</span></tt> files in the future.</dd>
251future.</dd>
252</dl> 278</dl>
279<div class="note">
280<p class="first admonition-title">Note</p>
281<p class="last">When performing package moves, developers must also update any
282relevant <tt class="docutils literal"><span class="pre">Display-If-Installed</span></tt> headers in news files.</p>
283</div>
284<p>The algorithm used to determine whether a news item is 'relevant' is as
285follows:</p>
286<ul class="simple">
287<li>For each <tt class="docutils literal"><span class="pre">Display-If-</span></tt> header type which occurs at least once:<ul>
288<li>The news item is not relevant if none of the headers of this type are
289successfully matched.</li>
290</ul>
291</li>
292<li>Otherwise the news item is relevant.</li>
293</ul>
294<p>In particular, if no <tt class="docutils literal"><span class="pre">Display-If-</span></tt> header is specified, a news item will be
295relevant for all users.</p>
296<p>This algorithm was chosen because it makes conditions like &quot;display this news
297item for <tt class="docutils literal"><span class="pre">YourSQL</span></tt> users who are on <tt class="docutils literal"><span class="pre">sparc</span></tt> or <tt class="docutils literal"><span class="pre">x86-obsd</span></tt> relatively
298simple to specify — it is believed that these kinds of condition are far more
299likely 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
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>
253</div> 302</div>
254<div class="section" id="news-item-body"> 303<div class="section" id="news-item-body">
255<h3><a class="toc-backref" href="#id21" name="news-item-body">News Item Body</a></h3> 304<h3><a class="toc-backref" href="#id29" name="news-item-body">News Item Body</a></h3>
256<p>The header section must be followed by a blank line, then the main body of the 305<p>The header section must be followed by a blank line, then the main body of the
257text.</p> 306text.</p>
258<p>The text body should be wrapped at 72 characters. No fancy formatting or tab 307<p>The text body should be wrapped at 72 characters. No fancy formatting or tab
259characters should be used -- the news item may be being displayed directly to a 308characters should be used the news item may be being displayed directly to a
260terminal. Paragraphs should be separated by two blank lines.</p> 309terminal. Paragraphs should be separated by a blank line.</p>
261<p>Hyperlinks may be used to refer to further information (for example, an upgrade 310<p>Hyperlinks may be used to refer to further information (for example, an upgrade
262guide). However, the main body of the news item should be descriptive and not 311guide). However, the main body of the news item should be descriptive and not
263simply a &quot;read this link&quot; text. It is assumed that the user will have access to 312simply a &quot;read this link&quot; text. It is assumed that the user will have access to
264a web browser <em>somewhere</em>, but not necessarily on the box which is being 313a web browser <em>somewhere</em>, but not necessarily on the box which is being
265administrated -- this will be the case on may servers and routers, for example.</p> 314administrated this will be the case on may servers and routers, for example.</p>
266</div> 315</div>
267<div class="section" id="example-news-item"> 316<div class="section" id="example-news-item">
268<h3><a class="toc-backref" href="#id22" name="example-news-item">Example News Item</a></h3> 317<h3><a class="toc-backref" href="#id30" name="example-news-item">Example News Item</a></h3>
269<p>The following hypothetical news item could be used for an upgrade to the 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
270<tt class="docutils literal"><span class="pre">YourSQL</span></tt> database format which breaks forward compatibility. It should be 319<tt class="docutils literal"><span class="pre">YourSQL</span></tt> database format which breaks forward compatibility.</p>
271named <tt class="docutils literal"><span class="pre">2005-11/2005-11-01-yoursql-upgrades.en.txt</span></tt>.</p>
272<pre class="literal-block">
273Title: YourSQL Upgrades from 4.0 to 4.1
274Author: Ciaran McCreesh &lt;ciaranm&#64;gentoo.org&gt;
275Content-Type: text/plain
276Posted: 01-Nov-2005
277Display-If-Installed: &lt;dev-db/yoursql-4.1_alpha
278
279YourSQL databases created using YourSQL version 4.0 are incompatible
280with YourSQL version 4.1 or later. There is no reliable way to
281automate the database format conversion, so action from the system
282administrator is required before an upgrade can take place.
283
284Please see the Gentoo YourSQL Upgrade Guide for instructions:
285
286 http://www.gentoo.org/doc/en/yoursql-upgrading.xml
287
288Also see the official YourSQL documentation:
289
290 http://dev.yoursql.com/doc/refman/4.1/en/upgrading-from-4-0.html
291
292After upgrading, you should also recompile any packages which link
293against YourSQL:
294
295 revdep-rebuild --library=libyoursqlclient.so.12
296
297The revdep-rebuild tool is provided by app-portage/gentoolkit.
298</pre>
299</div> 320</div>
300</div> 321</div>
301<div class="section" id="news-item-quality-control"> 322<div class="section" id="news-item-quality-control">
302<h2><a class="toc-backref" href="#id23" name="news-item-quality-control">News Item Quality Control</a></h2> 323<h2><a class="toc-backref" href="#id31" name="news-item-quality-control">News Item Quality Control</a></h2>
303<p>There have been complaints regarding the comprehensibility of some upgrade 324<p>There have been complaints regarding the comprehensibility of some upgrade
304notices and news items in the past. This is understandable -- not every Gentoo 325notices and news items in the past. This is understandable not every Gentoo
305developer speaks English as a first language. However, for the sake of clarity 326developer speaks English as a first language. However, for the sake of clarity,
306and professionalism it is important that any language problems be corrected 327professionalism and avoiding making us look like prats, it is important that any
307before inflicting a news item upon end users.</p> 328language problems be corrected before inflicting a news item upon end users.</p>
308<p>Thus, all proposed news items must be posted to the <tt class="docutils literal"><span class="pre">gentoo-dev</span></tt> or 329<p>Thus, at least 72 hours before a proposed news item is committed, it must be
309<tt class="docutils literal"><span class="pre">gentoo-core</span></tt> mailing list, and <tt class="docutils literal"><span class="pre">Cc:</span></tt>ed to <tt class="docutils literal"><span class="pre">pr&#64;gentoo.org</span></tt> at least 72 330posted to the <tt class="docutils literal"><span class="pre">gentoo-dev</span></tt> mailing list and <tt class="docutils literal"><span class="pre">Cc:</span></tt>ed to <tt class="docutils literal"><span class="pre">pr&#64;gentoo.org</span></tt>
310hours before being committed (exceptions may be made in exceptional 331(exceptions may be made in exceptional circumstances). Any complaints — for
311circumstances). Any complaints regarding wording or clarity <strong>must</strong> be 332example regarding wording, clarity or accuracy — <strong>must</strong> be addressed before
312addressed before the news item goes live.</p> 333the news item goes live.</p>
334<div class="note">
335<p class="first admonition-title">Note</p>
336<p class="last">A previous draft of this GLEP allowed news items to be sent to
337<tt class="docutils literal"><span class="pre">gentoo-core</span></tt> instead of <tt class="docutils literal"><span class="pre">gentoo-dev</span></tt>. It is possible that a situation
338may arise where this will be necessary (for example, a security update which
339must break backwards compatibility and which cannot be revealed to the public
340before a given date).</p>
341</div>
313<p>News items must only be for <strong>important</strong> changes that may cause serious upgrade 342<p>News items must only be for <strong>important</strong> changes that may cause serious upgrade
314or compatibility problems. Ordinary upgrade messages and non-critical news items 343or compatibility problems. Ordinary upgrade messages and non-critical news items
315should remain in <tt class="docutils literal"><span class="pre">einfo</span></tt> notices. The importance of the message to its 344should remain in <tt class="docutils literal"><span class="pre">einfo</span></tt> notices. The importance of the message to its
316intended audience should be justified with the proposal.</p> 345intended audience should be justified with the proposal.</p>
317<div class="important"> 346<div class="important">
321Thus, the justification should be in the form &quot;this message is important to 350Thus, the justification should be in the form &quot;this message is important to
322YourSQL users because ...&quot;, not &quot;YourSQL is important because ...&quot;.</p> 351YourSQL users because ...&quot;, not &quot;YourSQL is important because ...&quot;.</p>
323</div> 352</div>
324</div> 353</div>
325<div class="section" id="news-item-distribution"> 354<div class="section" id="news-item-distribution">
326<h2><a class="toc-backref" href="#id24" name="news-item-distribution">News Item Distribution</a></h2> 355<h2><a class="toc-backref" href="#id32" name="news-item-distribution">News Item Distribution</a></h2>
327<div class="section" id="server-side"> 356<div class="section" id="server-side">
328<h3><a class="toc-backref" href="#id25" name="server-side">Server Side</a></h3> 357<h3><a class="toc-backref" href="#id33" name="server-side">Server Side</a></h3>
329<p>News items are to be made available via the Portage tree. This removes any 358<p>News items are to be made available via the standard rsync tree. This removes
330need for polling of a remote source.</p> 359any need for polling of a remote source.</p>
331<p>A new repository will be created for news items. The type (CVS or Subversion), 360<p>A new repository will be created for news items. The type (CVS or Subversion),
332location and access controls on this repository are beyond the scope of this 361location and access controls on this repository are beyond the scope of this
333GLEP.</p> 362GLEP.</p>
334<div class="note"> 363<div class="note">
335<p class="first admonition-title">Note</p> 364<p class="first admonition-title">Note</p>
336<p class="last">A previous draft of this GLEP instead used the main <tt class="docutils literal"><span class="pre">gentoo-x86</span></tt> 365<p class="last">A previous draft of this GLEP instead used the main <tt class="docutils literal"><span class="pre">gentoo-x86</span></tt>
337tree. This was changed following advice from Infrastructure 366tree. This was changed following advice from Infrastructure
338<a class="footnote-reference" href="#ramereth-repo" id="id10" name="id10">[10]</a>. Both solutions have the same end result.</p> 367<a class="footnote-reference" href="#ramereth-repo" id="id14" name="id14">[12]</a>. Both solutions have the same end result.</p>
339</div> 368</div>
340<p>This repository will contain directories named <tt class="docutils literal"><span class="pre">yyyy-mm/</span></tt>, where <tt class="docutils literal"><span class="pre">yyyy</span></tt> is 369<p>This repository will contain directories named <tt class="docutils literal"><span class="pre">yyyy/mm/</span></tt>, where <tt class="docutils literal"><span class="pre">yyyy</span></tt> is
341the current year and <tt class="docutils literal"><span class="pre">mm</span></tt> is the current month number (01 for January through 370the current year and <tt class="docutils literal"><span class="pre">mm</span></tt> is the current month number (01 for January through
34212 for December). This separation will help keep news items more manageable.</p> 37112 for December). This separation will help keep news items more manageable.</p>
343<p>The contents of this repository will automatically be merged with the main rsync 372<p>The contents of this repository will automatically be merged with the main rsync
344tree, placing the items under a top-level <tt class="docutils literal"><span class="pre">news/</span></tt> directory. The method used 373tree, placing the items in a <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory. The method used for
345for merging these items is beyond the scope of this GLEP -- a similar setup is 374merging these items is beyond the scope of this GLEP a similar setup is
346already used for merging GLSAs into the rsync tree.</p> 375already 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>
377</div>
378<div class="section" id="client-side">
379<h3><a class="toc-backref" href="#id34" name="client-side">Client Side</a></h3>
380<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
382already 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>
347<div class="note"> 384<div class="note">
348<p class="first admonition-title">Note</p> 385<p class="first admonition-title">Note</p>
349<p class="last">The <tt class="docutils literal"><span class="pre">profiles/</span></tt> directory will <em>not</em> be used. This fits in with 386<p class="last">Future changes to Portage involving support for multiple repositories
350the Portage team's future plans for <tt class="docutils literal"><span class="pre">profiles/</span></tt> and <tt class="docutils literal"><span class="pre">metadata/</span></tt> 387may introduce repository names. In this case, the <tt class="docutils literal"><span class="pre">magic-chicken</span></tt> part of the
351separation.</p> 388filename should be replaced by a string representation of the repository
352</div> 389name. Thus, news item clients should use a wildcard rather than hardcoding
353</div>
354<div class="section" id="client-side">
355<h3><a class="toc-backref" href="#id26" name="client-side">Client Side</a></h3>
356<p>Whenever relevant unread news items are found, <tt class="docutils literal"><span class="pre">emerge</span></tt> will copy or symlink
357the news file into <tt class="docutils literal"><span class="pre">/var/lib/gentoo/news/</span></tt>.</p> 390the <tt class="docutils literal"><span class="pre">magic-chicken</span></tt> string.</p>
391</div>
358<p>Notification that new relevant news items will be displayed via the 392<p>Notification that new relevant news items will be displayed via the
359<tt class="docutils literal"><span class="pre">emerge</span></tt> tool in a similar way to the existing &quot;configuration files need 393<tt class="docutils literal"><span class="pre">emerge</span></tt> tool in a similar way to the existing &quot;configuration files need
360updating&quot; messages:</p> 394updating&quot; messages:</p>
361<pre class="literal-block"> 395<pre class="literal-block">
362* Important: 3 config files in /etc need updating.
363* Type emerge --help config to learn how to update config files.
364
365* Important: there are 5 unread news items. 396* Important: there are 5 unread news items.
366* Type emerge --help news to learn how to read news files. 397* Type emerge --help news to learn how to read news files.
367</pre> 398</pre>
368<p>The unread news message will also be displayed immediately after an 399<p>Checks for new news messages should be displayed:</p>
400<ul class="simple">
369<tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">sync</span></tt>.</p> 401<li>After an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">sync</span></tt></li>
370<p>Portage may also warn of unread news items using, for example, a red flashy 402<li>After an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">--pretend</span></tt></li>
371before actions such as merging a package.</p> 403<li>Before an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">&lt;target&gt;</span></tt> (which may also include a red warning message)</li>
372<p>Portage must keep track of news items which have already been installed to avoid 404<li>Before an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">--ask</span> <span class="pre">&lt;target&gt;</span></tt> sequence</li>
373repeatedly reinstalling a deleted news item.</p> 405</ul>
406<p>The package manager may use a timestamp check file to avoid having to process
407news items unnecessarily.</p>
408<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
410be handled via a <tt class="docutils literal"><span class="pre">news-magic-chicken.skip</span></tt> file, but implementation is not
411specified by this GLEP.</p>
374<p>Users who really don't care about news items can use <tt class="docutils literal"><span class="pre">rsync_excludes</span></tt> to 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
375filter out the <tt class="docutils literal"><span class="pre">news/</span></tt> directory.</p> 413filter out the <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory.</p>
376</div> 414</div>
377</div> 415</div>
378<div class="section" id="news-item-clients"> 416<div class="section" id="news-item-clients">
379<h2><a class="toc-backref" href="#id27" name="news-item-clients">News Item Clients</a></h2> 417<h2><a class="toc-backref" href="#id35" name="news-item-clients">News Item Clients</a></h2>
380<p>Once a news item is 'installed', third party tools (or a traditional Unix pager 418<p>Once a news item is marked for reading, third party tools (or traditional core
381and <tt class="docutils literal"><span class="pre">rm</span></tt>) can be used to display and view the news files. An <tt class="docutils literal"><span class="pre">eselect</span></tt> 419Unix tools) can be used to display and view the news files.</p>
382<a class="footnote-reference" href="#eselect" id="id11" name="id11">[2]</a> module shall be created as the 'suggested' display tool; other 420<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
422reader rather than a gateway, it should then add the name to a
423<tt class="docutils literal"><span class="pre">news-magic-chicken.read</span></tt> file in the same directory with the same file
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
383display tools (for example, a news to email forwarder, which would be ideal for 426tool; other display tools (for example, a news to email forwarder, which would
384users who sync on a cron) are left as options for those who desire them -- the 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
385simple file format make this relatively simple.</p> 428desire them.</p>
386</div> 429</div>
387<div class="section" id="news-item-removal"> 430<div class="section" id="news-item-removal">
388<h2><a class="toc-backref" href="#id28" name="news-item-removal">News Item Removal</a></h2> 431<h2><a class="toc-backref" href="#id36" name="news-item-removal">News Item Removal</a></h2>
389<p>News items can be removed (by removing the news file from the main tree) when 432<p>News items can be removed (by removing the news file from the main tree) when
390they are no longer relevant, if they are made obsolete by a future news item or 433they are no longer relevant, if they are made obsolete by a future news item or
391after a long period of time. This is the same as the method used for <tt class="docutils literal"><span class="pre">updates</span></tt> 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>
392entries.</p> 435entries.</p>
393</div> 436</div>
394</div> 437</div>
395<div class="section" id="integration-with-existing-systems"> 438<div class="section" id="integration-with-existing-systems">
396<h1><a class="toc-backref" href="#id29" name="integration-with-existing-systems">Integration with Existing Systems</a></h1> 439<h1><a class="toc-backref" href="#id37" name="integration-with-existing-systems">Integration with Existing Systems</a></h1>
397<p>It would be trivial to convert these news items into the format used for news 440<p>It would be simple to convert these news items into the format used for news
398items on the Gentoo website or posts for the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list.</p> 441items on the Gentoo website or posts for the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list.</p>
399<p>There is an existing automated tool <a class="footnote-reference" href="#forums-glsa" id="id12" name="id12">[3]</a> for posting GLSAs to the 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
400forums. A similar tool can be used for these news items.</p> 443forums. A similar tool can be used for these news items.</p>
401</div> 444</div>
402<div class="section" id="backwards-compatibility"> 445<div class="section" id="backwards-compatibility">
403<h1><a class="toc-backref" href="#id30" name="backwards-compatibility">Backwards Compatibility</a></h1> 446<h1><a class="toc-backref" href="#id38" name="backwards-compatibility">Backwards Compatibility</a></h1>
404<p>Backwards compatibility is not a concern here. Existing tools will simply ignore 447<p>Backwards compatibility is not a concern here. Existing tools will simply ignore
405the <tt class="docutils literal"><span class="pre">news/</span></tt> directory.</p> 448the <tt class="docutils literal"><span class="pre">news/</span></tt> directory.</p>
406</div> 449</div>
407<div class="section" id="reference-implementation"> 450<div class="section" id="reference-implementation">
408<h1><a class="toc-backref" href="#id31" name="reference-implementation">Reference Implementation</a></h1> 451<h1><a class="toc-backref" href="#id39" name="reference-implementation">Reference Implementation</a></h1>
409<div class="section" id="portage-code"> 452<div class="section" id="portage-code">
410<h2><a class="toc-backref" href="#id32" name="portage-code">Portage Code</a></h2> 453<h2><a class="toc-backref" href="#id40" name="portage-code">Portage Code</a></h2>
411<p>TODO</p> 454<p>TODO</p>
412</div> 455</div>
413<div class="section" id="simple-eselect-news-client"> 456<div class="section" id="simple-eselect-news-client">
414<h2><a class="toc-backref" href="#id33" name="simple-eselect-news-client">Simple <tt class="docutils literal docutils literal"><span class="pre">eselect</span></tt> News Client</a></h2> 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>
415<p>A demonstration <tt class="docutils literal"><span class="pre">eselect</span></tt> news display script follows:</p> 458<p>TODO Removed until the exact format details are figured out.</p>
416<pre class="literal-block">
417# Copyright 1999-2005 Gentoo Foundation
418# Distributed under the terms of the GNU General Public License v2
419# $Id: glep-0042.html,v 1.1 2005/11/05 03:33:17 g2boojum Exp $
420
421DESCRIPTION=&quot;Read important Gentoo news items&quot;
422MAINTAINER=&quot;ciaranm&#64;gentoo.org&quot;
423SVN_DATE='$Date: 2005/11/05 03:33:17 $'
424VERSION=$(svn_date_to_version &quot;${SVN_DATE}&quot; )
425
426get_news_item_list() {
427 [[ -d &quot;${ROOT}/var/lib/gentoo/news&quot; ]] || return
428 (
429 local news
430 for news in &quot;${ROOT}/var/lib/gentoo/news/&quot;*.txt ; do
431 echo $(basename ${news%%.*} )
432 done
433 ) | sort -u
434}
435
436get_filename() {
437 local best_lang=${LANG%%_*} lang= filename=&quot;${1}&quot;
438 [[ -e &quot;/${filename}&quot; ]] || for lang in &quot;${best_lang}&quot; &quot;en&quot; ; do
439 filename=&quot;${ROOT}/var/lib/gentoo/news/${1}.${lang}.txt&quot;
440 [[ -e &quot;${filename}&quot; ]] &amp;&amp; break
441 done
442 [[ -e &quot;${filename}&quot; ]] &amp;&amp; echo &quot;${filename}&quot; || die -q &quot;Can't find '${1}'&quot;
443}
444
445get_all_filenames() {
446 if [[ -z &quot;${1}&quot; ]] ; then
447 echo &quot;${ROOT}/var/lib/gentoo/news/&quot;*.??&quot;.txt&quot;
448 else
449 echo &quot;${ROOT}/var/lib/gentoo/news/${1}.&quot;??&quot;.txt&quot;
450 fi
451}
452
453get_headers() {
454 sed -e '/^$/Q' &lt; $(get_filename &quot;${1}&quot; )
455}
456
457get_body() {
458 sed -e '1,/^$/d' &lt; $(get_filename &quot;${1}&quot; )
459}
460
461get_title() {
462 get_headers &quot;${1}&quot; | sed -n -e '/^[Tt]itle: /s/^[^:]\+:[ \t]*//p'
463}
464
465### list action
466
467## {{{ list stuff
468describe_list() {
469 echo &quot;List available news items&quot;
470}
471
472do_list() {
473 write_list_start &quot;Available news items:&quot;
474 local empty=yes n=1
475 for news in $(get_news_item_list ) ; do
476 write_numbered_list_entry ${n} &quot;$(highlight $(get_title ${news} ) ) (${news})&quot;
477 n=$(( n + 1 ))
478 done
479}
480## }}}
481
482## {{{ show stuff
483describe_show(){
484 echo &quot;Show a news item&quot;
485}
486
487do_show() {
488 [[ -z &quot;${1}&quot; ]] &amp;&amp; die -q &quot;You didn't tell me which news item to read&quot;
489
490 local target=${1} filename=
491 if is_number &quot;${target}&quot; &amp;&amp; [[ ${target} -ge 1 ]] ; then
492 targets=( $(get_news_item_list ) )
493 target=${targets[$(( ${target} - 1 ))]}
494 fi
495
496 (
497 get_headers &quot;${target}&quot; | grep -v '^Display-If-\|Content-Type:'
498 echo
499 get_body &quot;${target}&quot;
500 ) | ${PAGER:-cat}
501}
502## }}}
503
504# {{{ delete stuff
505describe_delete() {
506 echo &quot;Delete a news item&quot;
507}
508
509do_delete() {
510 [[ -z &quot;${1}&quot; ]] &amp;&amp; die -q &quot;You didn't tell me which news item to delete&quot;
511
512 for target in $&#64; ; do
513 if is_number &quot;${target}&quot; &amp;&amp; [[ ${target} -ge 1 ]] ; then
514 targets=( $(get_news_item_list ) )
515 target=${targets[$(( ${target} - 1 ))]}
516 fi
517
518 rm $(get_all_filenames &quot;${target}&quot; ) || die -q &quot;Couldn't delete ${target}&quot;
519 done
520}
521# }}}
522
523# {{{ delete-all
524describe_delete-all() {
525 echo &quot;Delete all news items&quot;
526}
527
528do_delete-all() {
529 rm $(get_all_filenames ) || die -q &quot;Couldn't delete news items&quot;
530}
531# }}}
532</pre>
533</div> 459</div>
534<div class="section" id="simple-news-to-mail-forwarder"> 460<div class="section" id="simple-news-to-mail-forwarder">
535<h2><a class="toc-backref" href="#id34" name="simple-news-to-mail-forwarder">Simple News to Mail Forwarder</a></h2> 461<h2><a class="toc-backref" href="#id42" name="simple-news-to-mail-forwarder">Simple News to Mail Forwarder</a></h2>
536<p>A demonstration shell script which delivers news items via email follows:</p> 462<p>TODO Removed until the exact format details are figured out.</p>
537<pre class="literal-block">
538#!/bin/bash
539
540to_address=&quot;root&#64;localhost&quot;
541mail=&quot;mailx&quot;
542best_lang=&quot;${LANG%%_*}&quot;
543
544for news in /var/lib/gentoo/news/*.*.txt ; do
545 [[ -z &quot;${best_lang}&quot; ]] || news=&quot;${news%%.*}.${best_lang}.txt&quot;
546 [[ -f &quot;${news}&quot; ]] || news=&quot;${news%%.*}.en.txt&quot;
547 [[ -f &quot;${news}&quot; ]] || continue
548 title=$(sed -n -e '/^Title:/ { s,^[^:]\+:[ \t]\+,,p ; q }' &lt; ${news} )
549 sed -e '1,/^$/ { /^Display-If\|Content-Type/d }' &lt; &quot;${news}&quot; | \
550 ${mail} -s &quot;Gentoo news: ${title}&quot; &quot;${to_address}&quot; &amp;&amp; \
551 for file in ${news%%.*}.*.txt ; do rm &quot;${file}&quot; ; done
552done
553</pre>
554</div> 463</div>
555</div> 464</div>
556<div class="section" id="credits"> 465<div class="section" id="credits">
557<h1><a class="toc-backref" href="#id35" name="credits">Credits</a></h1> 466<h1><a class="toc-backref" href="#id43" name="credits">Credits</a></h1>
558<p>The idea behind notifying users of news updates via Portage comes from Stuart 467<p>The idea behind notifying users of news updates via Portage comes from Stuart
559Herbert <a class="footnote-reference" href="#stuart-blog" id="id13" name="id13">[12]</a>.</p> 468Herbert <a class="footnote-reference" href="#stuart-blog" id="id17" name="id17">[15]</a>.</p>
560<p>Thanks to Lance Albertson, Donnie Berkholz, Grant Goodyear, Brian Harring, Dan 469<p>Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear,
561Meltzer, Paul de Vrieze and Alec Warner for input. Some of the ideas presented 470Brian Harring, Dan Meltzer, Jason Stubbs, Paul de Vrieze and Alec Warner for
562here are theirs, others go completely against their suggestions.</p> 471input. Some of the ideas presented here are theirs, others go completely
472against their suggestions.</p>
473</div>
474<div class="section" id="example-files">
475<h1><a class="toc-backref" href="#id44" name="example-files">Example Files</a></h1>
476<p>TODO Removed until the exact format details are figured out.</p>
563</div> 477</div>
564<div class="section" id="references"> 478<div class="section" id="references">
565<h1><a class="toc-backref" href="#id36" name="references">References</a></h1> 479<h1><a class="toc-backref" href="#id45" name="references">References</a></h1>
480<table class="docutils footnote" frame="void" id="bug-11359" rules="none">
481<colgroup><col class="label" /><col /></colgroup>
482<tbody valign="top">
483<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;,
485<a class="reference" href="https://bugs.gentoo.org/show_bug.cgi?id=11359">https://bugs.gentoo.org/show_bug.cgi?id=11359</a></td></tr>
486</tbody>
487</table>
566<table class="docutils footnote" frame="void" id="docs-policy" rules="none"> 488<table class="docutils footnote" frame="void" id="docs-policy" rules="none">
567<colgroup><col class="label" /><col /></colgroup> 489<colgroup><col class="label" /><col /></colgroup>
568<tbody valign="top"> 490<tbody valign="top">
569<tr><td class="label"><a class="fn-backref" href="#id4" name="docs-policy">[1]</a></td><td>Gentoo XML Guide, Daniel Robbins et al., 491<tr><td class="label"><a class="fn-backref" href="#id8" name="docs-policy">[2]</a></td><td>Gentoo XML Guide, Daniel Robbins et al.,
570<a class="reference" href="http://www.gentoo.org/doc/en/xml-guide.xml">http://www.gentoo.org/doc/en/xml-guide.xml</a></td></tr> 492<a class="reference" href="http://www.gentoo.org/doc/en/xml-guide.xml">http://www.gentoo.org/doc/en/xml-guide.xml</a></td></tr>
571</tbody> 493</tbody>
572</table> 494</table>
573<table class="docutils footnote" frame="void" id="eselect" rules="none"> 495<table class="docutils footnote" frame="void" id="eselect" rules="none">
574<colgroup><col class="label" /><col /></colgroup> 496<colgroup><col class="label" /><col /></colgroup>
575<tbody valign="top"> 497<tbody valign="top">
576<tr><td class="label"><a class="fn-backref" href="#id11" name="eselect">[2]</a></td><td>eselect modular framework for configuration and 498<tr><td class="label"><a class="fn-backref" href="#id15" name="eselect">[3]</a></td><td>eselect modular framework for configuration and
577administration utilities, 499administration utilities,
578<a class="reference" href="http://www.gentoo.org/proj/en/eselect/index.xml">http://www.gentoo.org/proj/en/eselect/index.xml</a></td></tr> 500<a class="reference" href="http://www.gentoo.org/proj/en/eselect/index.xml">http://www.gentoo.org/proj/en/eselect/index.xml</a></td></tr>
579</tbody> 501</tbody>
580</table> 502</table>
581<table class="docutils footnote" frame="void" id="forums-glsa" rules="none"> 503<table class="docutils footnote" frame="void" id="forums-glsa" rules="none">
582<colgroup><col class="label" /><col /></colgroup> 504<colgroup><col class="label" /><col /></colgroup>
583<tbody valign="top"> 505<tbody valign="top">
584<tr><td class="label"><a class="fn-backref" href="#id12" name="forums-glsa">[3]</a></td><td>Forums user GLSA, 506<tr><td class="label"><a class="fn-backref" href="#id16" name="forums-glsa">[4]</a></td><td>Forums user GLSA,
585<a class="reference" href="http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=55648">http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=55648</a></td></tr> 507<a class="reference" href="http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=55648">http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=55648</a></td></tr>
586</tbody> 508</tbody>
587</table> 509</table>
588<table class="docutils footnote" frame="void" id="forums-whining" rules="none"> 510<table class="docutils footnote" frame="void" id="forums-apache2" rules="none">
589<colgroup><col class="label" /><col /></colgroup> 511<colgroup><col class="label" /><col /></colgroup>
590<tbody valign="top"> 512<tbody valign="top">
591<tr><td class="label"><a name="forums-whining">[4]</a></td><td><em>(<a class="fn-backref" href="#id1">1</a>, <a class="fn-backref" href="#id2">2</a>)</em> Forums thread &quot;Gentoo Apache2 Config Change Idiocy&quot;, 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;,
592<a class="reference" href="http://forums.gentoo.org/viewtopic-t-384368.html">http://forums.gentoo.org/viewtopic-t-384368.html</a></td></tr> 514<a class="reference" href="http://forums.gentoo.org/viewtopic-t-384368.html">http://forums.gentoo.org/viewtopic-t-384368.html</a></td></tr>
593</tbody> 515</tbody>
594</table> 516</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>
595<table class="docutils footnote" frame="void" id="glep-22" rules="none"> 524<table class="docutils footnote" frame="void" id="glep-22" rules="none">
596<colgroup><col class="label" /><col /></colgroup> 525<colgroup><col class="label" /><col /></colgroup>
597<tbody valign="top"> 526<tbody valign="top">
598<tr><td class="label"><a class="fn-backref" href="#id9" name="glep-22">[5]</a></td><td>GLEP 22: &quot;New &quot;keyword&quot; system to incorporate various 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
599userlands/kernels/archs&quot;, Grant Goodyear, 528userlands/kernels/archs&quot;, Grant Goodyear,
600<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> 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>
601</tbody> 530</tbody>
602</table> 531</table>
603<table class="docutils footnote" frame="void" id="glep-31" rules="none"> 532<table class="docutils footnote" frame="void" id="glep-31" rules="none">
604<colgroup><col class="label" /><col /></colgroup> 533<colgroup><col class="label" /><col /></colgroup>
605<tbody valign="top"> 534<tbody valign="top">
606<tr><td class="label"><a class="fn-backref" href="#id5" name="glep-31">[6]</a></td><td>GLEP 31: &quot;Character Sets for Portage Tree Items&quot;, Ciaran 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
607McCreesh, 536McCreesh,
608<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> 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>
609</tbody> 538</tbody>
610</table> 539</table>
611<table class="docutils footnote" frame="void" id="glep-34" rules="none"> 540<table class="docutils footnote" frame="void" id="glep-34" rules="none">
612<colgroup><col class="label" /><col /></colgroup> 541<colgroup><col class="label" /><col /></colgroup>
613<tbody valign="top"> 542<tbody valign="top">
614<tr><td class="label"><a class="fn-backref" href="#id7" name="glep-34">[7]</a></td><td>GLEP 34: &quot;Per-Category metadata.xml Files&quot;, Ciaran McCreesh, 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,
615<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> 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>
616</tbody> 545</tbody>
617</table> 546</table>
618<table class="docutils footnote" frame="void" id="glep-36" rules="none"> 547<table class="docutils footnote" frame="void" id="glep-36" rules="none">
619<colgroup><col class="label" /><col /></colgroup> 548<colgroup><col class="label" /><col /></colgroup>
620<tbody valign="top"> 549<tbody valign="top">
621<tr><td class="label"><a class="fn-backref" href="#id3" name="glep-36">[8]</a></td><td>GLEP 36: &quot;Subversion/CVS for Gentoo Hosted Projects&quot;, Aaron 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
622Walker, 551Walker,
623<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> 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>
624</tbody> 553</tbody>
625</table> 554</table>
626<table class="docutils footnote" frame="void" id="iso-639" rules="none"> 555<table class="docutils footnote" frame="void" id="iso-639" rules="none">
627<colgroup><col class="label" /><col /></colgroup> 556<colgroup><col class="label" /><col /></colgroup>
628<tbody valign="top"> 557<tbody valign="top">
629<tr><td class="label"><a class="fn-backref" href="#id6" name="iso-639">[9]</a></td><td>ISO 639 &quot;Code for the representation of names of languages&quot;</td></tr> 558<tr><td class="label"><a class="fn-backref" href="#id5" name="iso-639">[11]</a></td><td>ISO 639 &quot;Code for the representation of names of languages&quot;</td></tr>
630</tbody> 559</tbody>
631</table> 560</table>
632<table class="docutils footnote" frame="void" id="ramereth-repo" rules="none"> 561<table class="docutils footnote" frame="void" id="ramereth-repo" rules="none">
633<colgroup><col class="label" /><col /></colgroup> 562<colgroup><col class="label" /><col /></colgroup>
634<tbody valign="top"> 563<tbody valign="top">
635<tr><td class="label"><a class="fn-backref" href="#id10" name="ramereth-repo">[10]</a></td><td>&quot;Re: [gentoo-dev] GLEP ??: Critical News Reporting&quot;, Lance 564<tr><td class="label"><a class="fn-backref" href="#id14" name="ramereth-repo">[12]</a></td><td>&quot;Re: [gentoo-dev] GLEP ??: Critical News Reporting&quot;, Lance
636Albertson, 565Albertson,
637<a class="reference" href="http://marc.theaimsgroup.com/?l=gentoo-dev&amp;m=113111585907703&amp;w=2">http://marc.theaimsgroup.com/?l=gentoo-dev&amp;m=113111585907703&amp;w=2</a></td></tr> 566<a class="reference" href="http://marc.theaimsgroup.com/?l=gentoo-dev&amp;m=113111585907703&amp;w=2">http://marc.theaimsgroup.com/?l=gentoo-dev&amp;m=113111585907703&amp;w=2</a></td></tr>
638</tbody> 567</tbody>
639</table> 568</table>
640<table class="docutils footnote" frame="void" id="rfc-822" rules="none"> 569<table class="docutils footnote" frame="void" id="rfc-822" rules="none">
641<colgroup><col class="label" /><col /></colgroup> 570<colgroup><col class="label" /><col /></colgroup>
642<tbody valign="top"> 571<tbody valign="top">
643<tr><td class="label"><a class="fn-backref" href="#id8" name="rfc-822">[11]</a></td><td><a class="reference" href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> &quot;Standard for the format of ARPA Internet text messages&quot;</td></tr> 572<tr><td class="label"><a class="fn-backref" href="#id10" name="rfc-822">[13]</a></td><td><a class="reference" href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> &quot;Standard for the format of ARPA Internet text messages&quot;</td></tr>
573</tbody>
574</table>
575<table class="docutils footnote" frame="void" id="rfc-3629" rules="none">
576<colgroup><col class="label" /><col /></colgroup>
577<tbody valign="top">
578<tr><td class="label"><a class="fn-backref" href="#id7" name="rfc-3629">[14]</a></td><td><a class="reference" href="http://www.faqs.org/rfcs/rfc3629.html">RFC 3629</a>: &quot;UTF-8, a transformation format of ISO 10646&quot;
579<a class="reference" href="http://www.ietf.org/rfc/rfc3629.txt">http://www.ietf.org/rfc/rfc3629.txt</a></td></tr>
644</tbody> 580</tbody>
645</table> 581</table>
646<table class="docutils footnote" frame="void" id="stuart-blog" rules="none"> 582<table class="docutils footnote" frame="void" id="stuart-blog" rules="none">
647<colgroup><col class="label" /><col /></colgroup> 583<colgroup><col class="label" /><col /></colgroup>
648<tbody valign="top"> 584<tbody valign="top">
649<tr><td class="label"><a class="fn-backref" href="#id13" name="stuart-blog">[12]</a></td><td>&quot;Favouring an automatic news mechanism&quot;, Stuart Herbert, 585<tr><td class="label"><a class="fn-backref" href="#id17" name="stuart-blog">[15]</a></td><td>&quot;Favouring an automatic news mechanism&quot;, Stuart Herbert,
650<a class="reference" href="http://stu.gnqs.org/diary/gentoo.php/2005/10/28/favouring_an_automatic_news_mechanism">http://stu.gnqs.org/diary/gentoo.php/2005/10/28/favouring_an_automatic_news_mechanism</a></td></tr> 586<a class="reference" href="http://stu.gnqs.org/diary/gentoo.php/2005/10/28/favouring_an_automatic_news_mechanism">http://stu.gnqs.org/diary/gentoo.php/2005/10/28/favouring_an_automatic_news_mechanism</a></td></tr>
651</tbody> 587</tbody>
652</table> 588</table>
589<table class="docutils footnote" frame="void" id="id18" rules="none">
590<colgroup><col class="label" /><col /></colgroup>
591<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>
593</tbody>
594</table>
653</div> 595</div>
654<div class="section" id="copyright"> 596<div class="section" id="copyright">
655<h1><a class="toc-backref" href="#id37" name="copyright">Copyright</a></h1> 597<h1><a class="toc-backref" href="#id46" name="copyright">Copyright</a></h1>
656<p>This document has been placed in the public domain.</p> 598<p>This document has been placed in the public domain.</p>
657<!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : --> 599<!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : -->
658</div> 600</div>
659 601
660</div> 602</div>
661<div class="footer"> 603<div class="footer">
662<hr class="footer" /> 604<hr class="footer" />
663<a class="reference" href="glep-0042.txt">View document source</a>. 605<a class="reference" href="glep-0042.txt">View document source</a>.
664Generated on: 2005-11-05 03:32 UTC. 606Generated on: 2005-12-13 03:21 UTC.
665Generated 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. 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.
666 608
667</div> 609</div>
668</body> 610</body>
669</html> 611</html>

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20