/[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.4 Revision 1.7
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.4 $</td> 35<tr class="field"><th class="field-name">Version:</th><td class="field-body">$Revision: 1.7 $</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/11 01:38:18 $</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: 2006/01/05 15:10:45 $</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</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, 5-Jan-2006</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
99<div class="section" id="motivation"> 100<div class="section" id="motivation">
100<h1><a class="toc-backref" href="#id21" name="motivation">Motivation</a></h1> 101<h1><a class="toc-backref" href="#id21" name="motivation">Motivation</a></h1>
101<p>Although most package updates are clean and require little user action, 102<p>Although most package updates are clean and require little user action,
102occasionally an upgrade requires user intervention during the upgrade process. 103occasionally 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> 104Recent 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-5</span></tt> database format changes.</p> 105and 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 106<p>There are currently several ways of delivering important news items to our
106users, none of them particularly effective:</p> 107users, none of them particularly effective:</p>
107<ul class="simple"> 108<ul class="simple">
108<li>Gentoo Weekly News</li> 109<li>Gentoo Weekly News</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> 110<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>
110<li>The Gentoo Forums</li> 111<li>The Gentoo Forums</li>
111<li>The main Gentoo website</li> 112<li>The main Gentoo website</li>
112<li>RSS feeds of Gentoo news</li> 113<li>RSS feeds of Gentoo news</li>
114<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>
113</ul> 115</ul>
114<p>A more reliable way of getting news of critical updates out to users is required 116<p>A more reliable way of getting news of critical updates out to users is required
115to avoid repeats of the various recent upgrade debacles. This GLEP proposes a 117to avoid repeats of the various recent upgrade debacles. This GLEP proposes a
116solution based around pushing news items out to the user via the <tt class="docutils literal"><span class="pre">rsync</span></tt> tree.</p> 118solution based around pushing news items out to the user via the <tt class="docutils literal"><span class="pre">rsync</span></tt> tree.</p>
117<div class="important"> 119<div class="important">
184<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>
185<ol class="arabic simple"> 187<ol class="arabic simple">
186<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>
187<li>The news item is reviewed, following the process described in 189<li>The news item is reviewed, following the process described in
188<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>
189<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.
190From 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
191Distribution</a>.</li> 193Distribution</a>.</li>
192<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
193question are pushed to the user before the user accidentally makes an 195question are pushed to the user before the user accidentally makes an
194unwanted change. No changes to the existing rsync process are required by 196unwanted change. No changes to the existing rsync process are required by
198informing the user that there are unread news items.</li> 200informing the user that there are unread news items.</li>
199<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
200Item Clients</a>.</li> 202Item Clients</a>.</li>
201</ol> 203</ol>
202</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<ul class="simple">
209<li>Every repository (including overlays) will require a unique identifier. It is
210assumed that an identifier will be a string consisting of characters from
211<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)
212<tt class="docutils literal"><span class="pre">_</span></tt> (underscore).</li>
213<li>Portage must provide a way for external programs to obtain a list of all
214repository identifiers for a given system. It is assumed that this will be in
215the 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>
216<li>Portage must provide a way for external programs to obtain the base path for
217a repository with a given ID. It is assumed that this will be in the form of
218a <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>
219<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
220given repository ID.</li>
221<li>Portage must extend <tt class="docutils literal"><span class="pre">portageq</span></tt> to implement a command which returns whether
222or not the profile used for a given repository ID matches a certain base path
223(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>
224</ul>
225<p>These extensions are assumed during the following specification.</p>
226</div>
203<div class="section" id="news-item-identities"> 227<div class="section" id="news-item-identities">
204<h2><a class="toc-backref" href="#id25" name="news-item-identities">News Item Identities</a></h2> 228<h2><a class="toc-backref" href="#id26" name="news-item-identities">News Item Identities</a></h2>
205<p>Each news item will have a unique identifier. This identifier will be in the 229<p>Each news item will have a unique identifier. This identifier will be in the
206form <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>), 230form <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>),
207<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 231<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
208(<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 232(<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
209news 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>, 233news 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>,
210<tt class="docutils literal"><span class="pre">0-9</span></tt> and <tt class="docutils literal"><span class="pre">-</span></tt> (hyphen).</p> 234<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> (hyphen) and <tt class="docutils literal"><span class="pre">_</span></tt> (underscore).</p>
211</div> 235</div>
212<div class="section" id="news-item-directories"> 236<div class="section" id="news-item-directories">
213<h2><a class="toc-backref" href="#id26" name="news-item-directories">News Item Directories</a></h2> 237<h2><a class="toc-backref" href="#id27" name="news-item-directories">News Item Directories</a></h2>
214<p>Each news item will be represented by a directory whose name is the same as the 238<p>Each news item will be represented by a directory whose name is the same as the
215news item's identifier.</p> 239news item's identifier.</p>
216<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 240<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
217contains the text of the news item, in English, in the format described below.</p> 241contains the text of the news item, in English, in the format described below.</p>
218<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> 242<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>
219(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 243(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
220provided. However, only the English version of a news item is authoritative. 244provided. However, only the English version of a news item is authoritative.
221This anglocentricity is justified by precedent <a class="footnote-reference" href="#glep-34" id="id6" name="id6">[9]</a>.</p> 245This anglocentricity is justified by precedent <a class="footnote-reference" href="#glep-34" id="id6" name="id6">[8]</a>.</p>
222</div> 246</div>
223<div class="section" id="news-item-files"> 247<div class="section" id="news-item-files">
224<h2><a class="toc-backref" href="#id27" name="news-item-files">News Item Files</a></h2> 248<h2><a class="toc-backref" href="#id28" name="news-item-files">News Item Files</a></h2>
225<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 249<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
226compatibility with and for the same reasons as existing Gentoo documentation 250compatibility with and for the same reasons as existing Gentoo documentation
227<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> 251<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>
228<p>News items should be signed with a detached GPG signature:</p> 252<p>News items must be signed with a detached GPG signature.:</p>
229<pre class="literal-block"> 253<pre class="literal-block">
230gpg --armour --detach-sign ????-??-??-*.??.txt 254gpg --armour --detach-sign ????-??-??-*.??.txt
231</pre> 255</pre>
256<p>This GLEP does not specify the type or strength of signature to be used, nor
257does it discuss how, if at all, a centralised keychain will be provided. These
258issues should be handled as part of the signing policy discussions.</p>
232<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> 259<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>
233followed by the main body of the message as plain text. This GLEP defines 260followed by the main body of the message as plain text. This GLEP defines
234various optional and mandatory headers. Future GLEPs may propose new headers — 261various optional and mandatory headers. Future GLEPs may propose new headers —
235tools handling these news items must ignore any unrecognised header.</p> 262tools handling these news items must ignore any unrecognised header.</p>
236<div class="section" id="news-item-headers"> 263<div class="section" id="news-item-headers">
237<h3><a class="toc-backref" href="#id28" name="news-item-headers">News Item Headers</a></h3> 264<h3><a class="toc-backref" href="#id29" name="news-item-headers">News Item Headers</a></h3>
238<p>The following headers describe the purpose and format of the news item:</p> 265<p>The following headers describe the purpose and format of the news item:</p>
239<dl class="docutils"> 266<dl class="docutils">
240<dt><tt class="docutils literal"><span class="pre">Title:</span></tt></dt> 267<dt><tt class="docutils literal"><span class="pre">Title:</span></tt></dt>
241<dd>A short (maximum 44 characters) descriptive title. Mandatory.</dd> 268<dd>A short (maximum 44 characters) descriptive title. Mandatory.</dd>
242<dt><tt class="docutils literal"><span class="pre">Author:</span></tt></dt> 269<dt><tt class="docutils literal"><span class="pre">Author:</span></tt></dt>
246<dd>For translated news items, the translator's name and email address. Multiple 273<dd>For translated news items, the translator's name and email address. Multiple
247translator headers may be specified if appropriate.</dd> 274translator headers may be specified if appropriate.</dd>
248<dt><tt class="docutils literal"><span class="pre">Content-Type:</span></tt></dt> 275<dt><tt class="docutils literal"><span class="pre">Content-Type:</span></tt></dt>
249<dd>Must be <tt class="docutils literal"><span class="pre">text/plain</span></tt>. Mandatory.</dd> 276<dd>Must be <tt class="docutils literal"><span class="pre">text/plain</span></tt>. Mandatory.</dd>
250<dt><tt class="docutils literal"><span class="pre">Posted:</span></tt></dt> 277<dt><tt class="docutils literal"><span class="pre">Posted:</span></tt></dt>
251<dd>Date of posting, in <tt class="docutils literal"><span class="pre">dd-mmm-yyyy</span></tt> format (e.g. 14-Aug-2001) for 278<dd>Date of posting, in <tt class="docutils literal"><span class="pre">yyyy-mm-dd</span></tt> format (e.g. 2005-12-18) for
252compatibility 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 279compatibility with GLEP 45 <a class="footnote-reference" href="#glep-45" id="id11" name="id11">[10]</a>. Mandatory.</dd>
253may also be included. Mandatory.</dd>
254<dt><tt class="docutils literal"><span class="pre">Revision:</span></tt></dt> 280<dt><tt class="docutils literal"><span class="pre">Revision:</span></tt></dt>
255<dd>Initially 1. Incremented every time a non-trivial change is made. Changes 281<dd>Initially 1. Should be incremented every time a change is made to the news
256which require a re-read of the news item should instead use a new news item 282item. Changes that require a re-read of the news item (i.e., most changes
283that are not spelling or formatting related) should instead use a new news
257file. Mandatory.</dd> 284item. Mandatory.</dd>
258<dt><tt class="docutils literal"><span class="pre">News-Item-Format:</span></tt></dt> 285<dt><tt class="docutils literal"><span class="pre">News-Item-Format:</span></tt></dt>
259<dd>Must be <tt class="docutils literal"><span class="pre">1.0</span></tt>. Future revisions to the format may increment the minor 286<dd>Must be <tt class="docutils literal"><span class="pre">1.0</span></tt>. Future revisions to the format may increment the minor
260number for backwards-compatible changes, or the major number for major 287number for backwards-compatible changes, or the major number for major
261changes.</dd> 288changes.</dd>
262</dl> 289</dl>
263<p>The following headers are used for filtering:</p> 290<p>The following headers are used for filtering:</p>
264<dl class="docutils"> 291<dl class="docutils">
265<dt><tt class="docutils literal"><span class="pre">Display-If-Installed:</span></tt></dt> 292<dt><tt class="docutils literal"><span class="pre">Display-If-Installed:</span></tt></dt>
266<dd>A dependency atom or simple package name (for example, 293<dd>A dependency atom (for example, <tt class="docutils literal"><span class="pre">&lt;dev-lang/php-5_alpha</span></tt> or
267<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 294<tt class="docutils literal"><span class="pre">net-www/apache</span></tt>). If the user has the package specified installed from
268package specified installed, the news item should be displayed.</dd> 295the repository from which the news item was obtained, the news item should
296be displayed.</dd>
269<dt><tt class="docutils literal"><span class="pre">Display-If-Keyword:</span></tt></dt> 297<dt><tt class="docutils literal"><span class="pre">Display-If-Keyword:</span></tt></dt>
270<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 298<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
271user is on the keyword in question, the news item should be displayed.</dd> 299user is on the keyword in question, the news item should be displayed.</dd>
272<dt><tt class="docutils literal"><span class="pre">Display-If-Profile:</span></tt></dt> 300<dt><tt class="docutils literal"><span class="pre">Display-If-Profile:</span></tt></dt>
273<dd>A profile path, for example <tt class="docutils literal"><span class="pre">default-linux/sparc/sparc64/server</span></tt>. Standard 301<dd>A profile path, for example <tt class="docutils literal"><span class="pre">default-linux/sparc/sparc64/server</span></tt>. If the
274shell GLOB wildcards may be used. If the user is using the exact profile in 302user is using the exact profile in question, or a subprofile of this
275question, the news item should be displayed. This header may be used to 303profile, the news item should be displayed. This header may be used to
276replace <tt class="docutils literal"><span class="pre">deprecated</span></tt> files in the future.</dd> 304replace <tt class="docutils literal"><span class="pre">deprecated</span></tt> files in the future.</dd>
277</dl> 305</dl>
278<div class="note"> 306<div class="note">
279<p class="first admonition-title">Note</p> 307<p class="first admonition-title">Note</p>
280<p class="last">When performing package moves, developers must also update any 308<p class="last">When performing package moves, developers must also update any
298likely to occur than &quot;display this news item for people using <tt class="docutils literal"><span class="pre">YourSQL</span></tt>, or 326likely to occur than &quot;display this news item for people using <tt class="docutils literal"><span class="pre">YourSQL</span></tt>, or
299for 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 327for 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
300people 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> 328people 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>
301</div> 329</div>
302<div class="section" id="news-item-body"> 330<div class="section" id="news-item-body">
303<h3><a class="toc-backref" href="#id29" name="news-item-body">News Item Body</a></h3> 331<h3><a class="toc-backref" href="#id30" name="news-item-body">News Item Body</a></h3>
304<p>The header section must be followed by a blank line, then the main body of the 332<p>The header section must be followed by a blank line, then the main body of the
305text.</p> 333text.</p>
306<p>The text body should be wrapped at 72 characters. No fancy formatting or tab 334<p>The text body should be wrapped at 72 characters. No fancy formatting or tab
307characters should be used — the news item may be being displayed directly to a 335characters should be used — the news item may be being displayed directly to a
308terminal. Paragraphs should be separated by a blank line.</p> 336terminal. Paragraphs should be separated by a blank line.</p>
309<p>Hyperlinks may be used to refer to further information (for example, an upgrade 337<p>Hyperlinks may be used to refer to further information (for example, an upgrade
310guide). However, the main body of the news item should be descriptive and not 338guide). However, the main body of the news item should be descriptive and not
311simply a &quot;read this link&quot; text. It is assumed that the user will have access to 339simply a &quot;read this link&quot; text. It is assumed that the user will have access to
312a web browser <em>somewhere</em>, but not necessarily on the box which is being 340a web browser <em>somewhere</em>, but not necessarily on the box which is being
313administrated — this will be the case on may servers and routers, for example.</p> 341administrated — this will be the case on many servers and routers, for example.</p>
314</div> 342</div>
315<div class="section" id="example-news-item"> 343<div class="section" id="example-news-item">
316<h3><a class="toc-backref" href="#id30" name="example-news-item">Example News Item</a></h3> 344<h3><a class="toc-backref" href="#id31" name="example-news-item">Example News Item</a></h3>
317<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 345<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
318<tt class="docutils literal"><span class="pre">YourSQL</span></tt> database format which breaks forward compatibility.</p> 346<tt class="docutils literal"><span class="pre">YourSQL</span></tt> database format which breaks forward compatibility.</p>
319</div> 347</div>
320</div> 348</div>
321<div class="section" id="news-item-quality-control"> 349<div class="section" id="news-item-quality-control">
322<h2><a class="toc-backref" href="#id31" name="news-item-quality-control">News Item Quality Control</a></h2> 350<h2><a class="toc-backref" href="#id32" name="news-item-quality-control">News Item Quality Control</a></h2>
323<p>There have been complaints regarding the comprehensibility of some upgrade 351<p>There have been complaints regarding the comprehensibility of some upgrade
324notices and news items in the past. This is understandable — not every Gentoo 352notices and news items in the past. This is understandable — not every Gentoo
325developer speaks English as a first language. However, for the sake of clarity, 353developer speaks English as a first language. However, for the sake of clarity,
326professionalism and avoiding making us look like prats, it is important that any 354professionalism and avoiding making us look like prats, it is important that any
327language problems be corrected before inflicting a news item upon end users.</p> 355language problems be corrected before inflicting a news item upon end users.</p>
328<p>Thus, at least 72 hours before a proposed news item is committed, it must be 356<p>Thus, at least 72 hours before a proposed news item is committed, it must be
329posted 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> 357posted 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>
330(exceptions may be made in exceptional circumstances). Any complaints — for 358(exceptions may be made in exceptional circumstances). Any complaints — for
331example regarding wording, clarity or accuracy — <strong>must</strong> be addressed before 359example regarding wording, clarity or accuracy — <strong>must</strong> be addressed before
332the news item goes live.</p> 360the news item goes live.</p>
333<div class="note">
334<p class="first admonition-title">Note</p>
335<p class="last">A previous draft of this GLEP allowed news items to be sent to
336<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
337may arise where this will be necessary (for example, a security update which
338must break backwards compatibility and which cannot be revealed to the public
339before a given date).</p>
340</div>
341<p>News items must only be for <strong>important</strong> changes that may cause serious upgrade 361<p>News items must only be for <strong>important</strong> changes that may cause serious upgrade
342or compatibility problems. Ordinary upgrade messages and non-critical news items 362or compatibility problems. Ordinary upgrade messages and non-critical news items
343should remain in <tt class="docutils literal"><span class="pre">einfo</span></tt> notices. The importance of the message to its 363should remain in <tt class="docutils literal"><span class="pre">einfo</span></tt> notices. The importance of the message to its
344intended audience should be justified with the proposal.</p> 364intended audience should be justified with the proposal.</p>
345<div class="important"> 365<div class="important">
349Thus, the justification should be in the form &quot;this message is important to 369Thus, the justification should be in the form &quot;this message is important to
350YourSQL users because ...&quot;, not &quot;YourSQL is important because ...&quot;.</p> 370YourSQL users because ...&quot;, not &quot;YourSQL is important because ...&quot;.</p>
351</div> 371</div>
352</div> 372</div>
353<div class="section" id="news-item-distribution"> 373<div class="section" id="news-item-distribution">
354<h2><a class="toc-backref" href="#id32" name="news-item-distribution">News Item Distribution</a></h2> 374<h2><a class="toc-backref" href="#id33" name="news-item-distribution">News Item Distribution</a></h2>
355<div class="section" id="server-side"> 375<div class="section" id="server-side">
356<h3><a class="toc-backref" href="#id33" name="server-side">Server Side</a></h3> 376<h3><a class="toc-backref" href="#id34" name="server-side">Server Side</a></h3>
357<p>News items are to be made available via the standard rsync tree. This removes 377<p>News items are to be made available via the standard rsync tree. This removes
358any need for polling of a remote source.</p> 378any need for polling of a remote source.</p>
359<p>A new repository will be created for news items. The type (CVS or Subversion), 379<p>A new repository will be created for news items. The type (CVS or Subversion),
360location and access controls on this repository are beyond the scope of this 380location and access controls on this repository are beyond the scope of this
361GLEP.</p> 381GLEP.</p>
368<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 388<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
369the current year and <tt class="docutils literal"><span class="pre">mm</span></tt> is the current month number (01 for January through 389the current year and <tt class="docutils literal"><span class="pre">mm</span></tt> is the current month number (01 for January through
37012 for December). This separation will help keep news items more manageable.</p> 39012 for December). This separation will help keep news items more manageable.</p>
371<p>The contents of this repository will automatically be merged with the main rsync 391<p>The contents of this repository will automatically be merged with the main rsync
372tree, placing the items in a <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory. The method used for 392tree, placing the items in a <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory. The method used for
373merging these items is beyond the scope of this GLEP — a similar setup is 393merging these items and the frequency at which it will occur is beyond the scope
374already used for merging GLSAs into the rsync tree.</p> 394of this GLEP; a similar setup is already used for merging GLSAs into the rsync
395tree.</p>
375<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> 396<p>The main rsync tree will <strong>not</strong> use the <tt class="docutils literal"><span class="pre">yyyy/mm/</span></tt> subdirectory layout. The
397news item directories will all be immediately under the <tt class="docutils literal"><span class="pre">metadata/news/</span></tt>
398directory.</p>
376</div> 399</div>
377<div class="section" id="client-side"> 400<div class="section" id="client-side">
378<h3><a class="toc-backref" href="#id34" name="client-side">Client Side</a></h3> 401<h3><a class="toc-backref" href="#id35" name="client-side">Client Side</a></h3>
379<p>Whenever relevant unread news items are found, the package manager will create a 402<p>Whenever relevant unread news items are found, the package manager will create a
380file named <tt class="docutils literal"><span class="pre">/var/lib/portage/news/news.unread</span></tt> (if it does not already exist) 403file named <tt class="docutils literal"><span class="pre">/var/lib/gentoo/news/news-${repoid}.unread</span></tt> (if it does not
404already exist) and append the news item identifier (eg
381and append the news item identifier (eg <tt class="docutils literal"><span class="pre">2005-11-01-yoursql-updates</span></tt>) on a new 405<tt class="docutils literal"><span class="pre">2005-11-01-yoursql-updates</span></tt>) on a new line.</p>
382line.</p> 406<p>All news item related files should be root owned and in the <tt class="docutils literal"><span class="pre">portage</span></tt> group
383<div class="note"> 407with the group write (and, for directories, execute) bits set. News files should
384<p class="first admonition-title">Note</p> 408be world readable.</p>
385<p class="last">Future changes to Portage involving support for multiple repositories
386may require one news list per repository. Assuming repositories have some
387kind of unique identifier, this file could be named <tt class="docutils literal"><span class="pre">news-repoid.unread</span></tt>.</p>
388</div>
389<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
390<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
391updating&quot; messages:</p> 411updating&quot; messages:</p>
392<pre class="literal-block"> 412<pre class="literal-block">
393* Important: there are 5 unread news items. 413* Important: there are 5 unread news items.
397<ul class="simple"> 417<ul class="simple">
398<li>After an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">sync</span></tt></li> 418<li>After an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">sync</span></tt></li>
399<li>After an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">--pretend</span></tt></li> 419<li>After an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">--pretend</span></tt></li>
400<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> 420<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>
401</ul> 421</ul>
422<p>The package manager does not need to know how to launch the user's choice of
423news client. This is consistent with the way configuration file updates are
424handled.</p>
402<p>The package manager may use a timestamp check file to avoid having to process 425<p>The package manager may use a timestamp check file to avoid having to process
403news items unnecessarily.</p> 426news items unnecessarily.</p>
404<p>The package manager must keep track of news items that have already been added 427<p>The package manager must keep track of news items that have already been added
405to the unread list to avoid repeatedly marking a deleted news item. This could 428to the unread list to avoid repeatedly marking a deleted news item. This could
406be handled via a <tt class="docutils literal"><span class="pre">news.skip</span></tt> file, but implementation is not specified by this 429be handled via a <tt class="docutils literal"><span class="pre">news-${repoid}.skip</span></tt> file containing the IDs of news items
407GLEP.</p> 430that have already been added to a <tt class="docutils literal"><span class="pre">news-${repoid}.unread</span></tt> file, but this
431method is not required by this GLEP.</p>
408<p>Users who really don't care about news items can use <tt class="docutils literal"><span class="pre">rsync_excludes</span></tt> to 432<p>Users who really don't care about news items can use <tt class="docutils literal"><span class="pre">rsync_excludes</span></tt> to
409filter out the <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory.</p> 433filter out the <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory.</p>
410</div> 434</div>
411</div> 435</div>
412<div class="section" id="news-item-clients"> 436<div class="section" id="news-item-clients">
413<h2><a class="toc-backref" href="#id35" name="news-item-clients">News Item Clients</a></h2> 437<h2><a class="toc-backref" href="#id36" name="news-item-clients">News Item Clients</a></h2>
414<p>Once a news item is marked for reading, third party tools (or traditional core 438<p>Once a news item is marked for reading, third party tools (or traditional core
415Unix tools) can be used to display and view the news files.</p> 439Unix tools) can be used to display and view the news files.</p>
416<p>When a news item is read, its name should be removed from the <tt class="docutils literal"><span class="pre">news.unread</span></tt> 440<p>When a news item is read, its name should be removed from the
417file. News clients may add the name to a <tt class="docutils literal"><span class="pre">news.read</span></tt> file in the same 441<tt class="docutils literal"><span class="pre">news-repoid.unread</span></tt> file. If a news client acts as an interactive reader
442rather than a gateway, it should then add the name to a <tt class="docutils literal"><span class="pre">news-repoid.read</span></tt>
418directory with the same file format.</p> 443file in the same directory with the same file format.</p>
419<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 444<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
420tool; other display tools (for example, a news to email forwarder, which would 445tool; other display tools (for example, a news to email forwarder, which would
421be ideal for users who sync on a <tt class="docutils literal"><span class="pre">cron</span></tt>) are left as options for those who 446be ideal for users who sync on a <tt class="docutils literal"><span class="pre">cron</span></tt>) are left as options for those who
422desire them.</p> 447desire them.</p>
423</div> 448</div>
424<div class="section" id="news-item-removal"> 449<div class="section" id="news-item-removal">
425<h2><a class="toc-backref" href="#id36" name="news-item-removal">News Item Removal</a></h2> 450<h2><a class="toc-backref" href="#id37" name="news-item-removal">News Item Removal</a></h2>
426<p>News items can be removed (by removing the news file from the main tree) when 451<p>News items can be removed (by removing the news file from the main tree) when
427they are no longer relevant, if they are made obsolete by a future news item or 452they are no longer relevant, if they are made obsolete by a future news item or
428after a long period of time. This is the same as the method used for <tt class="docutils literal"><span class="pre">updates</span></tt> 453after a long period of time. This is the same as the method used for <tt class="docutils literal"><span class="pre">updates</span></tt>
429entries.</p> 454entries.</p>
430</div> 455</div>
431</div> 456</div>
432<div class="section" id="integration-with-existing-systems"> 457<div class="section" id="integration-with-existing-systems">
433<h1><a class="toc-backref" href="#id37" name="integration-with-existing-systems">Integration with Existing Systems</a></h1> 458<h1><a class="toc-backref" href="#id38" name="integration-with-existing-systems">Integration with Existing Systems</a></h1>
434<p>It would be simple to convert these news items into the format used for news 459<p>It would be simple to convert these news items into the format used for news
435items on the Gentoo website or posts for the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list.</p> 460items on the Gentoo website or posts for the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list.</p>
436<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 461<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
437forums. A similar tool can be used for these news items.</p> 462forums. A similar tool can be used for these news items.</p>
438</div> 463</div>
439<div class="section" id="backwards-compatibility"> 464<div class="section" id="backwards-compatibility">
440<h1><a class="toc-backref" href="#id38" name="backwards-compatibility">Backwards Compatibility</a></h1> 465<h1><a class="toc-backref" href="#id39" name="backwards-compatibility">Backwards Compatibility</a></h1>
441<p>Backwards compatibility is not a concern here. Existing tools will simply ignore 466<p>Backwards compatibility is not a concern here. Existing tools will simply ignore
442the <tt class="docutils literal"><span class="pre">news/</span></tt> directory.</p> 467the <tt class="docutils literal"><span class="pre">news/</span></tt> directory.</p>
443</div> 468</div>
444<div class="section" id="reference-implementation"> 469<div class="section" id="reference-implementation">
445<h1><a class="toc-backref" href="#id39" name="reference-implementation">Reference Implementation</a></h1> 470<h1><a class="toc-backref" href="#id40" name="reference-implementation">Reference Implementation</a></h1>
446<div class="section" id="portage-code"> 471<div class="section" id="portage-code">
447<h2><a class="toc-backref" href="#id40" name="portage-code">Portage Code</a></h2> 472<h2><a class="toc-backref" href="#id41" name="portage-code">Portage Code</a></h2>
448<p>TODO</p> 473<p>TODO</p>
449</div> 474</div>
450<div class="section" id="simple-eselect-news-client"> 475<div class="section" id="simple-eselect-news-client">
451<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> 476<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>
452<p>TODO Removed until the exact format details are figured out.</p> 477<p>TODO Removed until the exact format details are figured out.</p>
453</div> 478</div>
454<div class="section" id="simple-news-to-mail-forwarder"> 479<div class="section" id="simple-news-to-mail-forwarder">
455<h2><a class="toc-backref" href="#id42" name="simple-news-to-mail-forwarder">Simple News to Mail Forwarder</a></h2> 480<h2><a class="toc-backref" href="#id43" name="simple-news-to-mail-forwarder">Simple News to Mail Forwarder</a></h2>
456<p>TODO Removed until the exact format details are figured out.</p> 481<p>TODO Removed until the exact format details are figured out.</p>
457</div> 482</div>
458</div> 483</div>
459<div class="section" id="credits"> 484<div class="section" id="credits">
460<h1><a class="toc-backref" href="#id43" name="credits">Credits</a></h1> 485<h1><a class="toc-backref" href="#id44" name="credits">Credits</a></h1>
461<p>The idea behind notifying users of news updates via Portage comes from Stuart 486<p>The idea behind notifying users of news updates via Portage comes from Stuart
462Herbert <a class="footnote-reference" href="#stuart-blog" id="id17" name="id17">[15]</a>.</p> 487Herbert <a class="footnote-reference" href="#stuart-blog" id="id17" name="id17">[15]</a>.</p>
463<p>Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear, 488<p>Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear,
464Brian Harring, Dan Meltzer, Jason Stubbs, Paul de Vrieze and Alec Warner for 489Brian Harring, Marius Mauch, Dan Meltzer, Jason Stubbs, Paul de Vrieze and Alec
465input. Some of the ideas presented here are theirs, others go completely 490Warner for input. Some of the ideas presented here are theirs, others go
466against their suggestions.</p> 491completely against their suggestions.</p>
467</div> 492</div>
468<div class="section" id="example-files"> 493<div class="section" id="example-files">
469<h1><a class="toc-backref" href="#id44" name="example-files">Example Files</a></h1> 494<h1><a class="toc-backref" href="#id45" name="example-files">Example Files</a></h1>
470<p>TODO Removed until the exact format details are figured out.</p> 495<p>TODO Removed until the exact format details are figured out.</p>
471</div> 496</div>
472<div class="section" id="references"> 497<div class="section" id="references">
473<h1><a class="toc-backref" href="#id45" name="references">References</a></h1> 498<h1><a class="toc-backref" href="#id46" name="references">References</a></h1>
474<table class="docutils footnote" frame="void" id="bug-11359" rules="none"> 499<table class="docutils footnote" frame="void" id="bug-11359" rules="none">
475<colgroup><col class="label" /><col /></colgroup> 500<colgroup><col class="label" /><col /></colgroup>
476<tbody valign="top"> 501<tbody valign="top">
477<tr><td class="label"><a class="fn-backref" href="#id1" name="bug-11359">[1]</a></td><td>Bugzilla Bug 11359 502<tr><td class="label"><a class="fn-backref" href="#id1" name="bug-11359">[1]</a></td><td>Bugzilla Bug 11359
478&quot;[NEW FEATURE] pkg_postinst/pkg_preinst ewarn/einfo logging&quot;, 503&quot;[NEW FEATURE] pkg_postinst/pkg_preinst ewarn/einfo logging&quot;,
506<tbody valign="top"> 531<tbody valign="top">
507<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;, 532<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;,
508<a class="reference" href="http://forums.gentoo.org/viewtopic-t-384368.html">http://forums.gentoo.org/viewtopic-t-384368.html</a></td></tr> 533<a class="reference" href="http://forums.gentoo.org/viewtopic-t-384368.html">http://forums.gentoo.org/viewtopic-t-384368.html</a></td></tr>
509</tbody> 534</tbody>
510</table> 535</table>
511<table class="docutils footnote" frame="void" id="glep-1" rules="none">
512<colgroup><col class="label" /><col /></colgroup>
513<tbody valign="top">
514<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,
515<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>
516</tbody>
517</table>
518<table class="docutils footnote" frame="void" id="glep-22" rules="none"> 536<table class="docutils footnote" frame="void" id="glep-22" rules="none">
519<colgroup><col class="label" /><col /></colgroup> 537<colgroup><col class="label" /><col /></colgroup>
520<tbody valign="top"> 538<tbody valign="top">
521<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 539<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
522userlands/kernels/archs&quot;, Grant Goodyear, 540userlands/kernels/archs&quot;, Grant Goodyear,
523<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> 541<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>
524</tbody> 542</tbody>
525</table> 543</table>
526<table class="docutils footnote" frame="void" id="glep-31" rules="none"> 544<table class="docutils footnote" frame="void" id="glep-31" rules="none">
527<colgroup><col class="label" /><col /></colgroup> 545<colgroup><col class="label" /><col /></colgroup>
528<tbody valign="top"> 546<tbody valign="top">
529<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 547<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
530McCreesh, 548McCreesh,
531<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> 549<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>
532</tbody> 550</tbody>
533</table> 551</table>
534<table class="docutils footnote" frame="void" id="glep-34" rules="none"> 552<table class="docutils footnote" frame="void" id="glep-34" rules="none">
535<colgroup><col class="label" /><col /></colgroup> 553<colgroup><col class="label" /><col /></colgroup>
536<tbody valign="top"> 554<tbody valign="top">
537<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, 555<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,
538<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> 556<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>
539</tbody> 557</tbody>
540</table> 558</table>
541<table class="docutils footnote" frame="void" id="glep-36" rules="none"> 559<table class="docutils footnote" frame="void" id="glep-36" rules="none">
542<colgroup><col class="label" /><col /></colgroup> 560<colgroup><col class="label" /><col /></colgroup>
543<tbody valign="top"> 561<tbody valign="top">
544<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 562<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
545Walker, 563Walker,
546<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> 564<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>
565</tbody>
566</table>
567<table class="docutils footnote" frame="void" id="glep-45" rules="none">
568<colgroup><col class="label" /><col /></colgroup>
569<tbody valign="top">
570<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,
571<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>
547</tbody> 572</tbody>
548</table> 573</table>
549<table class="docutils footnote" frame="void" id="iso-639" rules="none"> 574<table class="docutils footnote" frame="void" id="iso-639" rules="none">
550<colgroup><col class="label" /><col /></colgroup> 575<colgroup><col class="label" /><col /></colgroup>
551<tbody valign="top"> 576<tbody valign="top">
586<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> 611<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>
587</tbody> 612</tbody>
588</table> 613</table>
589</div> 614</div>
590<div class="section" id="copyright"> 615<div class="section" id="copyright">
591<h1><a class="toc-backref" href="#id46" name="copyright">Copyright</a></h1> 616<h1><a class="toc-backref" href="#id47" name="copyright">Copyright</a></h1>
592<p>This document has been placed in the public domain.</p> 617<p>This document has been placed in the public domain.</p>
593<!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : --> 618<!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : -->
594</div> 619</div>
595 620
596</div> 621</div>
597<div class="footer"> 622<div class="footer">
598<hr class="footer" /> 623<hr class="footer" />
599<a class="reference" href="glep-0042.txt">View document source</a>. 624<a class="reference" href="glep-0042.txt">View document source</a>.
600Generated on: 2005-12-11 01:37 UTC. 625Generated on: 2006-01-05 15:09 UTC.
601Generated 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. 626Generated 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.
602 627
603</div> 628</div>
604</body> 629</body>
605</html> 630</html>

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.7

  ViewVC Help
Powered by ViewVC 1.1.20