/[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.6 Revision 1.8
6PEP, see http://www.python.org/peps/pep-0001.html for instructions and links 6PEP, see http://www.python.org/peps/pep-0001.html for instructions and links
7to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE! 7to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE!
8--> 8-->
9<head> 9<head>
10 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 10 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
11 <meta name="generator" content="Docutils 0.3.9: http://docutils.sourceforge.net/" /> 11 <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
12 <title>GLEP 42 -- Critical News Reporting</title> 12 <title>GLEP 42 -- Critical News Reporting</title>
13 <link rel="stylesheet" href="tools/glep.css" type="text/css" /> 13 <link rel="stylesheet" href="tools/glep.css" type="text/css" />
14</head> 14</head>
15<body bgcolor="white"> 15<body bgcolor="white">
16<table class="navigation" cellpadding="0" cellspacing="0" 16<table class="navigation" cellpadding="0" cellspacing="0"
19<a href="http://www.gentoo.org/" title="Gentoo Linux Home Page"> 19<a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
20<img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]" 20<img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
21 border="0" width="150" height="35" /></a></td> 21 border="0" width="150" height="35" /></a></td>
22<td class="textlinks" align="left"> 22<td class="textlinks" align="left">
23[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>] 23[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
24[<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>] 24[<b><a href="http://www.gentoo.org/peps">GLEP Index</a></b>]
25[<b><a href="./glep-0042.txt">GLEP Source</a></b>] 25[<b><a href="http://www.gentoo.org/proj/en/glep/glep-0042.txt">GLEP Source</a></b>]
26</td></tr></table> 26</td></tr></table>
27<table class="rfc2822 docutils field-list" frame="void" rules="none"> 27<table class="rfc2822 docutils field-list" frame="void" rules="none">
28<col class="field-name" /> 28<col class="field-name" />
29<col class="field-body" /> 29<col class="field-body" />
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.6 $</td> 35<tr class="field"><th class="field-name">Version:</th><td class="field-body">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/18 04:16:44 $</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.cgi/xml/htdocs/proj/en/glep/glep-0042.txt?cvsroot=gentoo">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="glep-0002.html">text/x-rst</a></td>
46</tr> 46</tr>
47<tr class="field"><th class="field-name">Created:</th><td class="field-body">31-Oct-2005</td> 47<tr class="field"><th class="field-name">Created:</th><td class="field-body">31-Oct-2005</td>
48</tr> 48</tr>
49<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">1-Nov-2005, 5-Nov-2005, 7-Nov-2005, 11-Dec-2005, 13-Dec-2005, 18-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">
55<p class="topic-title first"><a name="contents">Contents</a></p> 55<p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
56<ul class="simple"> 56<ul class="simple">
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>
90<li><a class="reference" href="#example-files" id="id45" name="id45">Example Files</a></li> 90<li><a class="reference" href="#example-files" id="id45" name="id45">Example Files</a></li>
91<li><a class="reference" href="#references" id="id46" name="id46">References</a></li> 91<li><a class="reference" href="#references" id="id46" name="id46">References</a></li>
92<li><a class="reference" href="#copyright" id="id47" name="id47">Copyright</a></li> 92<li><a class="reference" href="#copyright" id="id47" name="id47">Copyright</a></li>
93</ul> 93</ul>
94</div> 94</div>
95<div class="section" id="abstract"> 95<div class="section">
96<h1><a class="toc-backref" href="#id20" name="abstract">Abstract</a></h1> 96<h1><a class="toc-backref" href="#id20" id="abstract" name="abstract">Abstract</a></h1>
97<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
98regarding tree-related items.</p> 98regarding tree-related items.</p>
99</div> 99</div>
100<div class="section" id="motivation"> 100<div class="section">
101<h1><a class="toc-backref" href="#id21" name="motivation">Motivation</a></h1> 101<h1><a class="toc-backref" href="#id21" id="motivation" name="motivation">Motivation</a></h1>
102<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,
103occasionally an upgrade requires user intervention during the upgrade process. 103occasionally an upgrade requires user intervention during the upgrade process.
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> 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>
105and the <tt class="docutils literal"><span class="pre">mysql-4.1</span></tt> database format changes.</p> 105and the <tt class="docutils literal"><span class="pre">mysql-4.1</span></tt> database format changes.</p>
106<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
121<p class="last">This GLEP does not seek to replace or modify <tt class="docutils literal"><span class="pre">einfo</span></tt> messages 121<p class="last">This GLEP does not seek to replace or modify <tt class="docutils literal"><span class="pre">einfo</span></tt> messages
122which are displayed post-install. That is a separate issue which is handled 122which are displayed post-install. That is a separate issue which is handled
123by <tt class="docutils literal"><span class="pre">elog</span></tt> <a class="footnote-reference" href="#bug-11359" id="id1" name="id1">[1]</a>.</p> 123by <tt class="docutils literal"><span class="pre">elog</span></tt> <a class="footnote-reference" href="#bug-11359" id="id1" name="id1">[1]</a>.</p>
124</div> 124</div>
125</div> 125</div>
126<div class="section" id="requirements"> 126<div class="section">
127<h1><a class="toc-backref" href="#id22" name="requirements">Requirements</a></h1> 127<h1><a class="toc-backref" href="#id22" id="requirements" name="requirements">Requirements</a></h1>
128<p>An adequate solution must meet all of the following requirements:</p> 128<p>An adequate solution must meet all of the following requirements:</p>
129<dl class="docutils"> 129<dl class="docutils">
130<dt>Preemptive</dt> 130<dt>Preemptive</dt>
131<dd>Users should be told of changes <em>before</em> they break a system, not after the 131<dd>Users should be told of changes <em>before</em> they break a system, not after the
132damage has already been done. Ideally, the system administrator would be 132damage has already been done. Ideally, the system administrator would be
177sources (for example, Forums, GWN, the main Gentoo website) without 177sources (for example, Forums, GWN, the main Gentoo website) without
178excessive difficulty. Similarly, easy interoperation with any future news 178excessive difficulty. Similarly, easy interoperation with any future news
179sources should not be precluded.</dd> 179sources should not be precluded.</dd>
180</dl> 180</dl>
181</div> 181</div>
182<div class="section" id="specification"> 182<div class="section">
183<h1><a class="toc-backref" href="#id23" name="specification">Specification</a></h1> 183<h1><a class="toc-backref" href="#id23" id="specification" name="specification">Specification</a></h1>
184<div class="section" id="overview"> 184<div class="section">
185<h2><a class="toc-backref" href="#id24" name="overview">Overview</a></h2> 185<h2><a class="toc-backref" href="#id24" id="overview" name="overview">Overview</a></h2>
186<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>
187<ol class="arabic simple"> 187<ol class="arabic simple">
188<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>
189<li>The news item is reviewed, following the process described in 189<li>The news item is reviewed, following the process described in
190<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>
200informing the user that there are unread news items.</li> 200informing the user that there are unread news items.</li>
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 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
202Item Clients</a>.</li> 202Item Clients</a>.</li>
203</ol> 203</ol>
204</div> 204</div>
205<div class="section" id="required-portage-enhancements"> 205<div class="section">
206<h2><a class="toc-backref" href="#id25" name="required-portage-enhancements">Required Portage Enhancements</a></h2> 206<h2><a class="toc-backref" href="#id25" id="required-portage-enhancements" name="required-portage-enhancements">Required Portage Enhancements</a></h2>
207<p>The following extensions to Portage are required:</p> 207<p>The following extensions to Portage are required:</p>
208<p>TODO: ferringb wants spaces added to the first item on the list. I don't,
209because it makes repo id -&gt; filename mappings nasty.</p>
210<ul class="simple"> 208<ul class="simple">
211<li>Every repository (including overlays) will require a unique identifier. It is 209<li>Every repository (including overlays) will require a unique identifier. It is
212assumed that an identifier will be a string consisting of characters from 210assumed that an identifier will be a string consisting of characters from
213<tt class="docutils literal"><span class="pre">a</span></tt> to <tt class="docutils literal"><span class="pre">z</span></tt>, <tt class="docutils literal"><span class="pre">A</span></tt> to <tt class="docutils literal"><span class="pre">Z</span></tt>, <tt class="docutils literal"><span class="pre">0</span></tt> to <tt class="docutils literal"><span class="pre">9</span></tt>, <tt class="docutils literal"><span class="pre">+</span></tt> (plus), <tt class="docutils literal"><span class="pre">-</span></tt> (hyphen), 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)
214<tt class="docutils literal"><span class="pre">:</span></tt> (colon) and <tt class="docutils literal"><span class="pre">_</span></tt> (underscore).</li> 212<tt class="docutils literal"><span class="pre">_</span></tt> (underscore).</li>
215<li>Portage must provide a way for external programs to obtain a list of all 213<li>Portage must provide a way for external programs to obtain a list of all
216repository identifiers for a given system. It is assumed that this will be in 214repository identifiers for a given system. It is assumed that this will be in
217the form of a <tt class="docutils literal"><span class="pre">portageq</span></tt> command (e.g. <tt class="docutils literal"><span class="pre">portageq</span> <span class="pre">get_repo_ids</span></tt>).</li> 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>
218<li>Portage must provide a way for external programs to obtain the base path for 216<li>Portage must provide a way for external programs to obtain the base path for
219a repository with a given ID. It is assumed that this will be in the form of 217a repository with a given ID. It is assumed that this will be in the form of
224or not the profile used for a given repository ID matches a certain base path 222or not the profile used for a given repository ID matches a certain base path
225(e.g. <tt class="docutils literal"><span class="pre">portageq</span> <span class="pre">profile_used</span> <span class="pre">default-linux/sparc/sparc64/2004.3</span> <span class="pre">gentoo-x86</span></tt>).</li> 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>
226</ul> 224</ul>
227<p>These extensions are assumed during the following specification.</p> 225<p>These extensions are assumed during the following specification.</p>
228</div> 226</div>
229<div class="section" id="news-item-identities"> 227<div class="section">
230<h2><a class="toc-backref" href="#id26" name="news-item-identities">News Item Identities</a></h2> 228<h2><a class="toc-backref" href="#id26" id="news-item-identities" name="news-item-identities">News Item Identities</a></h2>
231<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
232form <tt class="docutils literal"><span class="pre">yyyy-mm-dd-short-name</span></tt>, where <tt class="docutils literal"><span class="pre">yyyy</span></tt> is the year (e.g. <tt class="docutils literal"><span class="pre">2005</span></tt>), 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>),
233<tt class="docutils literal"><span class="pre">mm</span></tt> is the month (<tt class="docutils literal"><span class="pre">01</span></tt> through <tt class="docutils literal"><span class="pre">12</span></tt>) and dd is the day of the month 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
234(<tt class="docutils literal"><span class="pre">01</span></tt> through <tt class="docutils literal"><span class="pre">31</span></tt>). The <tt class="docutils literal"><span class="pre">short-name</span></tt> is a very short name describing the 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
235news item (e.g. <tt class="docutils literal"><span class="pre">yoursql-updates</span></tt>), consisting only of the characters <tt class="docutils literal"><span class="pre">a-z</span></tt>, 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>,
236<tt class="docutils literal"><span class="pre">0-9</span></tt>, <tt class="docutils literal"><span class="pre">+</span></tt> (plus), <tt class="docutils literal"><span class="pre">:</span></tt> (colon), <tt class="docutils literal"><span class="pre">-</span></tt> (hyphen) and <tt class="docutils literal"><span class="pre">_</span></tt> (underscore).</p> 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>
237</div> 235</div>
238<div class="section" id="news-item-directories"> 236<div class="section">
239<h2><a class="toc-backref" href="#id27" name="news-item-directories">News Item Directories</a></h2> 237<h2><a class="toc-backref" href="#id27" id="news-item-directories" name="news-item-directories">News Item Directories</a></h2>
240<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
241news item's identifier.</p> 239news item's identifier.</p>
242<p>The directory will contain a file named <tt class="docutils literal"><span class="pre">yyyy-mm-dd-short-name.en.txt</span></tt>, which 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
243contains 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>
244<p>If a news item is translated, other files named <tt class="docutils literal"><span class="pre">yyyy-mm-dd-short-name.xx.txt</span></tt> 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>
245(where <tt class="docutils literal"><span class="pre">xx</span></tt> is the ISO 639 <a class="footnote-reference" href="#iso-639" id="id5" name="id5">[11]</a> two letter country code) will also be 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
246provided. However, only the English version of a news item is authoritative. 244provided. However, only the English version of a news item is authoritative.
247This anglocentricity is justified by precedent <a class="footnote-reference" href="#glep-34" id="id6" name="id6">[8]</a>.</p> 245This anglocentricity is justified by precedent <a class="footnote-reference" href="#glep-34" id="id6" name="id6">[8]</a>.</p>
248</div> 246</div>
249<div class="section" id="news-item-files"> 247<div class="section">
250<h2><a class="toc-backref" href="#id28" name="news-item-files">News Item Files</a></h2> 248<h2><a class="toc-backref" href="#id28" id="news-item-files" name="news-item-files">News Item Files</a></h2>
251<p>A news item file is a text file, encoded using UTF-8 <a class="footnote-reference" href="#rfc-3629" id="id7" name="id7">[14]</a> for 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
252compatibility with and for the same reasons as existing Gentoo documentation 250compatibility with and for the same reasons as existing Gentoo documentation
253<a class="footnote-reference" href="#docs-policy" id="id8" name="id8">[2]</a> and the tree <a class="footnote-reference" href="#glep-31" id="id9" name="id9">[7]</a>.</p> 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>
254<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>
255<pre class="literal-block"> 253<pre class="literal-block">
256gpg --armour --detach-sign ????-??-??-*.??.txt 254gpg --armour --detach-sign ????-??-??-*.??.txt
257</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>
258<p>A news item file's content will consist of an <a class="reference" href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> style header <a class="footnote-reference" href="#rfc-822" id="id10" name="id10">[13]</a> 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>
259followed 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
260various optional and mandatory headers. Future GLEPs may propose new headers — 261various optional and mandatory headers. Future GLEPs may propose new headers —
261tools handling these news items must ignore any unrecognised header.</p> 262tools handling these news items must ignore any unrecognised header.</p>
262<div class="section" id="news-item-headers"> 263<div class="section">
263<h3><a class="toc-backref" href="#id29" name="news-item-headers">News Item Headers</a></h3> 264<h3><a class="toc-backref" href="#id29" id="news-item-headers" name="news-item-headers">News Item Headers</a></h3>
264<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>
265<dl class="docutils"> 266<dl class="docutils">
266<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>
267<dd>A short (maximum 44 characters) descriptive title. Mandatory.</dd> 268<dd>A short (maximum 44 characters) descriptive title. Mandatory.</dd>
268<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>
275<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>
276<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>
277<dd>Date of posting, in <tt class="docutils literal"><span class="pre">yyyy-mm-dd</span></tt> format (e.g. 2005-12-18) for 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
278compatibility with GLEP 45 <a class="footnote-reference" href="#glep-45" id="id11" name="id11">[10]</a>. Mandatory.</dd> 279compatibility with GLEP 45 <a class="footnote-reference" href="#glep-45" id="id11" name="id11">[10]</a>. Mandatory.</dd>
279<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>
280<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
281which 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
282file. Mandatory.</dd> 284item. Mandatory.</dd>
283<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>
284<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
285number for backwards-compatible changes, or the major number for major 287number for backwards-compatible changes, or the major number for major
286changes.</dd> 288changes.</dd>
287</dl> 289</dl>
288<p>The following headers are used for filtering:</p> 290<p>The following headers are used for filtering:</p>
289<dl class="docutils"> 291<dl class="docutils">
290<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>
291<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
292<tt class="docutils literal"><span class="pre">&lt;dev-lang/php-5_alpha</span></tt> or <tt class="docutils literal"><span class="pre">net-www/apache</span></tt>). If the user has the 294<tt class="docutils literal"><span class="pre">net-www/apache</span></tt>). If the user has the package specified installed from
293package specified installed from the repository from which the news item was 295the repository from which the news item was obtained, the news item should
294obtained, the news item should be displayed.</dd> 296be displayed.</dd>
295<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>
296<dd>A keyword <a class="footnote-reference" href="#glep-22" id="id12" name="id12">[6]</a> name, for example <tt class="docutils literal"><span class="pre">mips</span></tt> or <tt class="docutils literal"><span class="pre">x86-fbsd</span></tt>. If the 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
297user 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>
298<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>
299<dd>A profile path, for example <tt class="docutils literal"><span class="pre">default-linux/sparc/sparc64/server</span></tt>. If the 301<dd>A profile path, for example <tt class="docutils literal"><span class="pre">default-linux/sparc/sparc64/server</span></tt>. If the
323simple to specify — it is believed that these kinds of condition are far more 325simple to specify — it is believed that these kinds of condition are far more
324likely 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
325for people on <tt class="docutils literal"><span class="pre">sparc</span></tt> or <tt class="docutils literal"><span class="pre">x86-obsd</span></tt>&quot; or &quot;display these news items for 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
326people who use <tt class="docutils literal"><span class="pre">YourSQL</span></tt> and who are on both <tt class="docutils literal"><span class="pre">sparc</span></tt> and <tt class="docutils literal"><span class="pre">x86-obsd</span></tt>&quot;.</p> 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>
327</div> 329</div>
328<div class="section" id="news-item-body"> 330<div class="section">
329<h3><a class="toc-backref" href="#id30" name="news-item-body">News Item Body</a></h3> 331<h3><a class="toc-backref" href="#id30" id="news-item-body" name="news-item-body">News Item Body</a></h3>
330<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
331text.</p> 333text.</p>
332<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
333characters 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
334terminal. Paragraphs should be separated by a blank line.</p> 336terminal. Paragraphs should be separated by a blank line.</p>
335<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
336guide). 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
337simply 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
338a 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
339administrated — 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>
340</div> 342</div>
341<div class="section" id="example-news-item"> 343<div class="section">
342<h3><a class="toc-backref" href="#id31" name="example-news-item">Example News Item</a></h3> 344<h3><a class="toc-backref" href="#id31" id="example-news-item" name="example-news-item">Example News Item</a></h3>
343<p><a class="reference" href="glep-0042-extras/example-news-item.txt">This hypothetical news item</a> <a class="footnote-reference" href="#id18" id="id19" name="id19">[16]</a> could be used for an upgrade to the 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
344<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>
345</div> 347</div>
346</div> 348</div>
347<div class="section" id="news-item-quality-control"> 349<div class="section">
348<h2><a class="toc-backref" href="#id32" name="news-item-quality-control">News Item Quality Control</a></h2> 350<h2><a class="toc-backref" href="#id32" id="news-item-quality-control" name="news-item-quality-control">News Item Quality Control</a></h2>
349<p>There have been complaints regarding the comprehensibility of some upgrade 351<p>There have been complaints regarding the comprehensibility of some upgrade
350notices 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
351developer 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,
352professionalism 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
353language 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>
354<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
355posted 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>
356(exceptions may be made in exceptional circumstances). Any complaints — for 358(exceptions may be made in exceptional circumstances). Any complaints — for
357example regarding wording, clarity or accuracy — <strong>must</strong> be addressed before 359example regarding wording, clarity or accuracy — <strong>must</strong> be addressed before
358the news item goes live.</p> 360the news item goes live.</p>
359<div class="note">
360<p class="first admonition-title">Note</p>
361<p class="last">A previous draft of this GLEP allowed news items to be sent to
362<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
363may arise where this will be necessary (for example, a security update which
364must break backwards compatibility and which cannot be revealed to the public
365before a given date).</p>
366</div>
367<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
368or compatibility problems. Ordinary upgrade messages and non-critical news items 362or compatibility problems. Ordinary upgrade messages and non-critical news items
369should 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
370intended audience should be justified with the proposal.</p> 364intended audience should be justified with the proposal.</p>
371<div class="important"> 365<div class="important">
374news items which are aimed at users of an uncommon package or architecture. 368news items which are aimed at users of an uncommon package or architecture.
375Thus, 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
376YourSQL users because ...&quot;, not &quot;YourSQL is important because ...&quot;.</p> 370YourSQL users because ...&quot;, not &quot;YourSQL is important because ...&quot;.</p>
377</div> 371</div>
378</div> 372</div>
379<div class="section" id="news-item-distribution"> 373<div class="section">
380<h2><a class="toc-backref" href="#id33" name="news-item-distribution">News Item Distribution</a></h2> 374<h2><a class="toc-backref" href="#id33" id="news-item-distribution" name="news-item-distribution">News Item Distribution</a></h2>
381<div class="section" id="server-side"> 375<div class="section">
382<h3><a class="toc-backref" href="#id34" name="server-side">Server Side</a></h3> 376<h3><a class="toc-backref" href="#id34" id="server-side" name="server-side">Server Side</a></h3>
383<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
384any need for polling of a remote source.</p> 378any need for polling of a remote source.</p>
385<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),
386location 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
387GLEP.</p> 381GLEP.</p>
394<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
395the 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
39612 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>
397<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
398tree, 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
399merging 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
400already 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>
401<p>The main rsync tree will <strong>not</strong> use the <tt class="docutils literal"><span class="pre">yyyy/mm/</span></tt> subdirectory layout.</p> 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>
402</div> 399</div>
403<div class="section" id="client-side"> 400<div class="section">
404<h3><a class="toc-backref" href="#id35" name="client-side">Client Side</a></h3> 401<h3><a class="toc-backref" href="#id35" id="client-side" name="client-side">Client Side</a></h3>
405<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
406file named <tt class="docutils literal"><span class="pre">/var/lib/gentoo/news/news-repoid.unread</span></tt> (if it does not 403file named <tt class="docutils literal"><span class="pre">/var/lib/gentoo/news/news-${repoid}.unread</span></tt> (if it does not
407already exist) and append the news item identifier (eg 404already exist) and append the news item identifier (eg
408<tt class="docutils literal"><span class="pre">2005-11-01-yoursql-updates</span></tt>) on a new line.</p> 405<tt class="docutils literal"><span class="pre">2005-11-01-yoursql-updates</span></tt>) on a new line.</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
407with the group write (and, for directories, execute) bits set. News files should
408be world readable.</p>
409<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
410<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
411updating&quot; messages:</p> 411updating&quot; messages:</p>
412<pre class="literal-block"> 412<pre class="literal-block">
413* Important: there are 5 unread news items. 413* Important: there are 5 unread news items.
416<p>Checks for new news messages should be displayed:</p> 416<p>Checks for new news messages should be displayed:</p>
417<ul class="simple"> 417<ul class="simple">
418<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>
419<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>
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> 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>
421<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>
422</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>
423<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
424news items unnecessarily.</p> 426news items unnecessarily.</p>
425<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
426to 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
427be handled via a <tt class="docutils literal"><span class="pre">news-repoid.skip</span></tt> file containing the IDs of news items that 429be handled via a <tt class="docutils literal"><span class="pre">news-${repoid}.skip</span></tt> file containing the IDs of news items
428have already been added to a <tt class="docutils literal"><span class="pre">news-repoid.unread</span></tt> file, but this method is not 430that have already been added to a <tt class="docutils literal"><span class="pre">news-${repoid}.unread</span></tt> file, but this
429required by this GLEP.</p> 431method is not required by this GLEP.</p>
430<p>Users who really don't care about news items can use <tt class="docutils literal"><span class="pre">rsync_excludes</span></tt> to 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
431filter 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>
432</div> 434</div>
433</div> 435</div>
434<div class="section" id="news-item-clients"> 436<div class="section">
435<h2><a class="toc-backref" href="#id36" name="news-item-clients">News Item Clients</a></h2> 437<h2><a class="toc-backref" href="#id36" id="news-item-clients" name="news-item-clients">News Item Clients</a></h2>
436<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
437Unix 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>
438<p>When a news item is read, its name should be removed from the 440<p>When a news item is read, its name should be removed from the
439<tt class="docutils literal"><span class="pre">news-repoid.unread</span></tt> file. If a news client acts as an interactive reader 441<tt class="docutils literal"><span class="pre">news-repoid.unread</span></tt> file. If a news client acts as an interactive reader
440rather than a gateway, it should then add the name to a <tt class="docutils literal"><span class="pre">news-repoid.read</span></tt> 442rather than a gateway, it should then add the name to a <tt class="docutils literal"><span class="pre">news-repoid.read</span></tt>
442<p>An <tt class="docutils literal"><span class="pre">eselect</span></tt> <a class="footnote-reference" href="#eselect" id="id15" name="id15">[3]</a> module shall be created as the 'suggested' display 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
443tool; 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
444be ideal for users who sync on a <tt class="docutils literal"><span class="pre">cron</span></tt>) are left as options for those who 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
445desire them.</p> 447desire them.</p>
446</div> 448</div>
447<div class="section" id="news-item-removal"> 449<div class="section">
448<h2><a class="toc-backref" href="#id37" name="news-item-removal">News Item Removal</a></h2> 450<h2><a class="toc-backref" href="#id37" id="news-item-removal" name="news-item-removal">News Item Removal</a></h2>
449<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
450they 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
451after a long period of time. This is the same as the method used for <tt class="docutils literal"><span class="pre">updates</span></tt> 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>
452entries.</p> 454entries.</p>
453</div> 455</div>
454</div> 456</div>
455<div class="section" id="integration-with-existing-systems"> 457<div class="section">
456<h1><a class="toc-backref" href="#id38" name="integration-with-existing-systems">Integration with Existing Systems</a></h1> 458<h1><a class="toc-backref" href="#id38" id="integration-with-existing-systems" name="integration-with-existing-systems">Integration with Existing Systems</a></h1>
457<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
458items 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>
459<p>There is an existing automated tool <a class="footnote-reference" href="#forums-glsa" id="id16" name="id16">[4]</a> for posting GLSAs to the 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
460forums. A similar tool can be used for these news items.</p> 462forums. A similar tool can be used for these news items.</p>
461</div> 463</div>
462<div class="section" id="backwards-compatibility"> 464<div class="section">
463<h1><a class="toc-backref" href="#id39" name="backwards-compatibility">Backwards Compatibility</a></h1> 465<h1><a class="toc-backref" href="#id39" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1>
464<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
465the <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>
466</div> 468</div>
467<div class="section" id="reference-implementation"> 469<div class="section">
468<h1><a class="toc-backref" href="#id40" name="reference-implementation">Reference Implementation</a></h1> 470<h1><a class="toc-backref" href="#id40" id="reference-implementation" name="reference-implementation">Reference Implementation</a></h1>
469<div class="section" id="portage-code"> 471<div class="section">
470<h2><a class="toc-backref" href="#id41" name="portage-code">Portage Code</a></h2> 472<h2><a class="toc-backref" href="#id41" id="portage-code" name="portage-code">Portage Code</a></h2>
471<p>TODO</p> 473<p>TODO</p>
472</div> 474</div>
473<div class="section" id="simple-eselect-news-client"> 475<div class="section">
474<h2><a class="toc-backref" href="#id42" name="simple-eselect-news-client">Simple <tt class="docutils literal docutils literal"><span class="pre">eselect</span></tt> News Client</a></h2> 476<h2><a class="toc-backref" href="#id42" id="simple-eselect-news-client" name="simple-eselect-news-client">Simple <tt class="docutils literal"><span class="pre">eselect</span></tt> News Client</a></h2>
475<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>
476</div> 478</div>
477<div class="section" id="simple-news-to-mail-forwarder"> 479<div class="section">
478<h2><a class="toc-backref" href="#id43" name="simple-news-to-mail-forwarder">Simple News to Mail Forwarder</a></h2> 480<h2><a class="toc-backref" href="#id43" id="simple-news-to-mail-forwarder" name="simple-news-to-mail-forwarder">Simple News to Mail Forwarder</a></h2>
479<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>
480</div> 482</div>
481</div> 483</div>
482<div class="section" id="credits"> 484<div class="section">
483<h1><a class="toc-backref" href="#id44" name="credits">Credits</a></h1> 485<h1><a class="toc-backref" href="#id44" id="credits" name="credits">Credits</a></h1>
484<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
485Herbert <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>
486<p>Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear, 488<p>Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear,
487Brian 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
488input. Some of the ideas presented here are theirs, others go completely 490Warner for input. Some of the ideas presented here are theirs, others go
489against their suggestions.</p> 491completely against their suggestions.</p>
490</div> 492</div>
491<div class="section" id="example-files"> 493<div class="section">
492<h1><a class="toc-backref" href="#id45" name="example-files">Example Files</a></h1> 494<h1><a class="toc-backref" href="#id45" id="example-files" name="example-files">Example Files</a></h1>
493<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>
494</div> 496</div>
495<div class="section" id="references"> 497<div class="section">
496<h1><a class="toc-backref" href="#id46" name="references">References</a></h1> 498<h1><a class="toc-backref" href="#id46" id="references" name="references">References</a></h1>
497<table class="docutils footnote" frame="void" id="bug-11359" rules="none"> 499<table class="docutils footnote" frame="void" id="bug-11359" rules="none">
498<colgroup><col class="label" /><col /></colgroup> 500<colgroup><col class="label" /><col /></colgroup>
499<tbody valign="top"> 501<tbody valign="top">
500<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
501&quot;[NEW FEATURE] pkg_postinst/pkg_preinst ewarn/einfo logging&quot;, 503&quot;[NEW FEATURE] pkg_postinst/pkg_preinst ewarn/einfo logging&quot;,
608<tbody valign="top"> 610<tbody valign="top">
609<tr><td class="label"><a class="fn-backref" href="#id19" name="id18">[16]</a></td><td><a class="reference" href="glep-0042-extras/example-news-item.txt">glep-0042-extras/example-news-item.txt</a></td></tr> 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>
610</tbody> 612</tbody>
611</table> 613</table>
612</div> 614</div>
613<div class="section" id="copyright"> 615<div class="section">
614<h1><a class="toc-backref" href="#id47" name="copyright">Copyright</a></h1> 616<h1><a class="toc-backref" href="#id47" id="copyright" name="copyright">Copyright</a></h1>
615<p>This document has been placed in the public domain.</p> 617<p>This document has been placed in the public domain.</p>
616<!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : --> 618<!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : -->
617</div> 619</div>
618 620
619</div> 621</div>
620<div class="footer"> 622<div class="footer">
621<hr class="footer" /> 623<hr class="footer" />
622<a class="reference" href="glep-0042.txt">View document source</a>. 624<a class="reference" href="glep-0042.txt">View document source</a>.
623Generated on: 2005-12-18 04:15 UTC. 625Generated on: 2006-02-13 16:26 UTC.
624Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. 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.
625 627
626</div> 628</div>
627</body> 629</body>
628</html> 630</html>

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

  ViewVC Help
Powered by ViewVC 1.1.20