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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.18 - (hide annotations) (download) (as text)
Sun Oct 14 17:00:15 2007 UTC (6 years, 9 months ago) by antarus
Branch: MAIN
Changes since 1.17: +6 -253 lines
File MIME type: text/html
the canary on 53 went well, changing the rest

1 g2boojum 1.1 <?xml version="1.0" encoding="utf-8" ?>
2     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3     <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4 antarus 1.18
5 g2boojum 1.1 <head>
6     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
7 g2boojum 1.8 <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
8 g2boojum 1.1 <title>GLEP 42 -- Critical News Reporting</title>
9 antarus 1.18 <link rel="stylesheet" href="tools/glep.css" type="text/css" />
10 g2boojum 1.1 </head>
11     <body bgcolor="white">
12     <table class="navigation" cellpadding="0" cellspacing="0"
13     width="100%" border="0">
14     <tr><td class="navicon" width="150" height="35">
15     <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
16     <img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
17     border="0" width="150" height="35" /></a></td>
18     <td class="textlinks" align="left">
19     [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
20 antarus 1.18 [<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>]
21 g2boojum 1.8 [<b><a href="http://www.gentoo.org/proj/en/glep/glep-0042.txt">GLEP Source</a></b>]
22 g2boojum 1.1 </td></tr></table>
23     <table class="rfc2822 docutils field-list" frame="void" rules="none">
24     <col class="field-name" />
25     <col class="field-body" />
26     <tbody valign="top">
27     <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">42</td>
28     </tr>
29     <tr class="field"><th class="field-name">Title:</th><td class="field-body">Critical News Reporting</td>
30     </tr>
31 antarus 1.18 <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.13</td>
32 g2boojum 1.1 </tr>
33 g2boojum 1.13 <tr class="field"><th class="field-name">Author:</th><td class="field-body">Ciaran McCreesh &lt;ciaranm&#32;&#97;t&#32;gentoo.org&gt;,
34     Stephen Bennett &lt;spb&#32;&#97;t&#32;gentoo.org&gt;,
35     Zach Medico &lt;zmedico&#32;&#97;t&#32;gentoo.org&gt;</td>
36 g2boojum 1.1 </tr>
37 antarus 1.18 <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">2007/05/05 22:24:25</a></td>
38 g2boojum 1.1 </tr>
39 antarus 1.17 <tr class="field"><th class="field-name">Status:</th><td class="field-body">Final</td>
40 g2boojum 1.1 </tr>
41     <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
42     </tr>
43 g2boojum 1.8 <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>
44 g2boojum 1.1 </tr>
45 ciaranm 1.3 <tr class="field"><th class="field-name">Created:</th><td class="field-body">31-Oct-2005</td>
46 g2boojum 1.1 </tr>
47 g2boojum 1.14 <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, 2-Mar-2006, 6-Mar-2006, 12-Jun-2006, 5-Sep-2006</td>
48 g2boojum 1.1 </tr>
49     </tbody>
50     </table>
51     <hr />
52 g2boojum 1.8 <div class="contents topic">
53     <p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
54 g2boojum 1.1 <ul class="simple">
55 spb 1.12 <li><a class="reference" href="#abstract" id="id22" name="id22">Abstract</a></li>
56     <li><a class="reference" href="#motivation" id="id23" name="id23">Motivation</a></li>
57     <li><a class="reference" href="#requirements" id="id24" name="id24">Requirements</a></li>
58     <li><a class="reference" href="#specification" id="id25" name="id25">Specification</a><ul>
59     <li><a class="reference" href="#overview" id="id26" name="id26">Overview</a></li>
60     <li><a class="reference" href="#required-portage-enhancements" id="id27" name="id27">Required Portage Enhancements</a></li>
61     <li><a class="reference" href="#news-item-identities" id="id28" name="id28">News Item Identities</a></li>
62     <li><a class="reference" href="#news-item-directories" id="id29" name="id29">News Item Directories</a></li>
63     <li><a class="reference" href="#news-item-files" id="id30" name="id30">News Item Files</a><ul>
64     <li><a class="reference" href="#news-item-headers" id="id31" name="id31">News Item Headers</a></li>
65     <li><a class="reference" href="#news-item-body" id="id32" name="id32">News Item Body</a></li>
66     <li><a class="reference" href="#example-news-item" id="id33" name="id33">Example News Item</a></li>
67 g2boojum 1.1 </ul>
68     </li>
69 spb 1.12 <li><a class="reference" href="#news-item-quality-control" id="id34" name="id34">News Item Quality Control</a></li>
70     <li><a class="reference" href="#news-item-distribution" id="id35" name="id35">News Item Distribution</a><ul>
71     <li><a class="reference" href="#server-side" id="id36" name="id36">Server Side</a></li>
72     <li><a class="reference" href="#client-side" id="id37" name="id37">Client Side</a></li>
73 g2boojum 1.1 </ul>
74     </li>
75 spb 1.12 <li><a class="reference" href="#news-item-clients" id="id38" name="id38">News Item Clients</a></li>
76     <li><a class="reference" href="#news-item-removal" id="id39" name="id39">News Item Removal</a></li>
77 g2boojum 1.1 </ul>
78     </li>
79 spb 1.12 <li><a class="reference" href="#integration-with-existing-systems" id="id40" name="id40">Integration with Existing Systems</a></li>
80     <li><a class="reference" href="#backwards-compatibility" id="id41" name="id41">Backwards Compatibility</a></li>
81     <li><a class="reference" href="#reference-implementation" id="id42" name="id42">Reference Implementation</a></li>
82     <li><a class="reference" href="#credits" id="id43" name="id43">Credits</a></li>
83     <li><a class="reference" href="#example-files" id="id44" name="id44">Example Files</a></li>
84     <li><a class="reference" href="#references" id="id45" name="id45">References</a></li>
85     <li><a class="reference" href="#copyright" id="id46" name="id46">Copyright</a></li>
86 g2boojum 1.1 </ul>
87     </div>
88 g2boojum 1.8 <div class="section">
89 spb 1.12 <h1><a class="toc-backref" href="#id22" id="abstract" name="abstract">Abstract</a></h1>
90 g2boojum 1.1 <p>This GLEP proposes a new way of informing users about important updates and news
91 ciaranm 1.9 related to the tree.</p>
92 g2boojum 1.1 </div>
93 g2boojum 1.8 <div class="section">
94 spb 1.12 <h1><a class="toc-backref" href="#id23" id="motivation" name="motivation">Motivation</a></h1>
95 ciaranm 1.4 <p>Although most package updates are clean and require little user action,
96 ciaranm 1.9 occasionally an upgrade requires user intervention. Recent examples of the
97     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> and the <tt class="docutils literal"><span class="pre">mysql-4.1</span></tt>
98     database format changes.</p>
99 ciaranm 1.4 <p>There are currently several ways of delivering important news items to our
100     users, none of them particularly effective:</p>
101 g2boojum 1.1 <ul class="simple">
102     <li>Gentoo Weekly News</li>
103 ciaranm 1.4 <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>
104 g2boojum 1.1 <li>The Gentoo Forums</li>
105     <li>The main Gentoo website</li>
106     <li>RSS feeds of Gentoo news</li>
107 ciaranm 1.5 <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>
108 g2boojum 1.1 </ul>
109     <p>A more reliable way of getting news of critical updates out to users is required
110 ciaranm 1.9 to avoid repeats of various prior upgrade debacles. This GLEP proposes a
111 g2boojum 1.1 solution based around pushing news items out to the user via the <tt class="docutils literal"><span class="pre">rsync</span></tt> tree.</p>
112 ciaranm 1.4 <div class="important">
113     <p class="first admonition-title">Important</p>
114     <p class="last">This GLEP does not seek to replace or modify <tt class="docutils literal"><span class="pre">einfo</span></tt> messages
115     which are displayed post-install. That is a separate issue which is handled
116     by <tt class="docutils literal"><span class="pre">elog</span></tt> <a class="footnote-reference" href="#bug-11359" id="id1" name="id1">[1]</a>.</p>
117     </div>
118 g2boojum 1.1 </div>
119 g2boojum 1.8 <div class="section">
120 spb 1.12 <h1><a class="toc-backref" href="#id24" id="requirements" name="requirements">Requirements</a></h1>
121 g2boojum 1.1 <p>An adequate solution must meet all of the following requirements:</p>
122     <dl class="docutils">
123     <dt>Preemptive</dt>
124 ciaranm 1.4 <dd>Users should be told of changes <em>before</em> they break a system, not after the
125     damage has already been done. Ideally, the system administrator would be
126     given ample warning to plan difficult upgrades and changes, rather than only
127     being told just before action is necessary.</dd>
128 g2boojum 1.1 <dt>No user subscription required</dt>
129 ciaranm 1.4 <dd>It has already been demonstrated <a class="footnote-reference" href="#forums-apache2" id="id2" name="id2">[5]</a> that many users do not
130 ciaranm 1.9 read the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list or <tt class="docutils literal"><span class="pre">RSS</span></tt> feeds. A solution that
131 g2boojum 1.1 requires subscription has no advantage over current methods.</dd>
132     <dt>No user monitoring required</dt>
133 ciaranm 1.4 <dd>It has already been demonstrated <a class="footnote-reference" href="#forums-apache2" id="id3" name="id3">[5]</a> that many users do not
134 g2boojum 1.1 read news items posted to the Gentoo website, or do not read news items
135     until it is too late. A solution that relies upon active monitoring of a
136     particular source has no advantage over current methods.</dd>
137     <dt>Relevant</dt>
138     <dd>System administrators who do not use a particular package should not have to
139     read news items which affect purely that package. Some news items may be of
140     relevance to most or all users, but those that are not should not be forced
141     upon users unnecessarily.</dd>
142     <dt>Lightweight</dt>
143     <dd>It is not reasonable to expect all users to have an MTA, web browser, email
144 ciaranm 1.4 client, cron daemon or text processing suite available on their system.
145     Users must not be forced to install unreasonable extra software to be able
146     to read news items.</dd>
147 g2boojum 1.1 <dt>No privacy violations</dt>
148     <dd>Users of the solution should not be required to provide information about
149     their systems (for example, IP addresses or installed packages).</dd>
150     <dt>Multiple delivery method support</dt>
151     <dd>Some users may wish to view news items via email, some via a terminal and
152     some via a web browser. A solution should either support all of these
153 ciaranm 1.4 methods or (better still) make it simple to write clients for displaying
154 g2boojum 1.1 news items in different ways.</dd>
155     </dl>
156     <p>The following characteristics would be desirable:</p>
157     <dl class="docutils">
158     <dt>Internationalisable</dt>
159     <dd>Being able to provide messages in multiple languages may be beneficial.</dd>
160     <dt>Quality control</dt>
161     <dd>There should be some way to ensure that badly written or irrelevant messages
162 ciaranm 1.4 are not sent out, for example by inexperienced developers or those whose
163     English language skills are below par.</dd>
164 g2boojum 1.1 <dt>Simple for developers</dt>
165     <dd>Posting news items should be as simple as is reasonably possible.</dd>
166     <dt>Simple for users</dt>
167     <dd>Reading relevant news items should be as simple as is reasonably possible.</dd>
168     <dt>Compatibility with existing and future news sources</dt>
169     <dd>A news system would ideally be able to be integrated with existing news
170     sources (for example, Forums, GWN, the main Gentoo website) without
171     excessive difficulty. Similarly, easy interoperation with any future news
172     sources should not be precluded.</dd>
173     </dl>
174     </div>
175 g2boojum 1.8 <div class="section">
176 spb 1.12 <h1><a class="toc-backref" href="#id25" id="specification" name="specification">Specification</a></h1>
177 g2boojum 1.8 <div class="section">
178 spb 1.12 <h2><a class="toc-backref" href="#id26" id="overview" name="overview">Overview</a></h2>
179 g2boojum 1.1 <p>News items are published and delivered to users as follows:</p>
180     <ol class="arabic simple">
181 ciaranm 1.4 <li>A news item is written. The format to be used is described below.</li>
182 g2boojum 1.1 <li>The news item is reviewed, following the process described in
183     <a class="reference" href="#news-item-quality-control">News Item Quality Control</a>.</li>
184 ciaranm 1.6 <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.
185 g2boojum 1.1 From here, it is merged with the rsync tree. This is described in <a class="reference" href="#news-item-distribution">News Item
186     Distribution</a>.</li>
187     <li>Users fetch the news item when they sync. This ensures that the news items in
188     question are pushed to the user before the user accidentally makes an
189     unwanted change. No changes to the existing rsync process are required by
190     this GLEP.</li>
191 ciaranm 1.4 <li>The package manager filters the news item and, if it is relevant, marks the
192     news item for reading. The package manager should also display a notice
193     informing the user that there are unread news items.</li>
194 g2boojum 1.1 <li>The news item is handled by the user's choice of news item reader. See <a class="reference" href="#news-item-clients">News
195     Item Clients</a>.</li>
196     </ol>
197     </div>
198 g2boojum 1.8 <div class="section">
199 spb 1.12 <h2><a class="toc-backref" href="#id27" id="required-portage-enhancements" name="required-portage-enhancements">Required Portage Enhancements</a></h2>
200 ciaranm 1.6 <p>The following extensions to Portage are required:</p>
201     <ul class="simple">
202     <li>Every repository (including overlays) will require a unique identifier. It is
203     assumed that an identifier will be a string consisting of characters from
204 ciaranm 1.7 <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)
205     <tt class="docutils literal"><span class="pre">_</span></tt> (underscore).</li>
206 ciaranm 1.6 <li>Portage must provide a way for external programs to obtain a list of all
207     repository identifiers for a given system. It is assumed that this will be in
208     the 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>
209     <li>Portage must provide a way for external programs to obtain the base path for
210     a repository with a given ID. It is assumed that this will be in the form of
211     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_root</span> <span class="pre">gentoo-x86</span></tt>).</li>
212     <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
213     given repository ID.</li>
214     <li>Portage must extend <tt class="docutils literal"><span class="pre">portageq</span></tt> to implement a command which returns whether
215 ciaranm 1.10 or not the profile used for a given repository ID is exactly the given profile
216     (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>
217     <span class="pre">gentoo-x86</span></tt>).</li>
218 ciaranm 1.6 </ul>
219     <p>These extensions are assumed during the following specification.</p>
220     </div>
221 g2boojum 1.8 <div class="section">
222 spb 1.12 <h2><a class="toc-backref" href="#id28" id="news-item-identities" name="news-item-identities">News Item Identities</a></h2>
223 ciaranm 1.4 <p>Each news item will have a unique identifier. This identifier will be in the
224     form <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>),
225     <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
226     (<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
227     news 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>,
228 ciaranm 1.7 <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>
229 ciaranm 1.4 </div>
230 g2boojum 1.8 <div class="section">
231 spb 1.12 <h2><a class="toc-backref" href="#id29" id="news-item-directories" name="news-item-directories">News Item Directories</a></h2>
232 ciaranm 1.4 <p>Each news item will be represented by a directory whose name is the same as the
233     news item's identifier.</p>
234     <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
235     contains the text of the news item, in English, in the format described below.</p>
236     <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>
237 ciaranm 1.9 (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, and the date
238     remains the same as the original news item) will also be provided. However, only
239     the English version of a news item is authoritative. This anglocentricity is
240     justified by precedent <a class="footnote-reference" href="#glep-34" id="id6" name="id6">[8]</a>.</p>
241 ciaranm 1.4 </div>
242 g2boojum 1.8 <div class="section">
243 spb 1.12 <h2><a class="toc-backref" href="#id30" id="news-item-files" name="news-item-files">News Item Files</a></h2>
244 ciaranm 1.4 <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
245     compatibility with and for the same reasons as existing Gentoo documentation
246 ciaranm 1.6 <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>
247 ciaranm 1.7 <p>News items must be signed with a detached GPG signature.:</p>
248 ciaranm 1.4 <pre class="literal-block">
249     gpg --armour --detach-sign ????-??-??-*.??.txt
250     </pre>
251 ciaranm 1.7 <p>This GLEP does not specify the type or strength of signature to be used, nor
252     does it discuss how, if at all, a centralised keychain will be provided. These
253     issues should be handled as part of the signing policy discussions.</p>
254 ciaranm 1.4 <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>
255 g2boojum 1.1 followed by the main body of the message as plain text. This GLEP defines
256 ciaranm 1.4 various optional and mandatory headers. Future GLEPs may propose new headers —
257 g2boojum 1.1 tools handling these news items must ignore any unrecognised header.</p>
258 g2boojum 1.8 <div class="section">
259 spb 1.12 <h3><a class="toc-backref" href="#id31" id="news-item-headers" name="news-item-headers">News Item Headers</a></h3>
260 g2boojum 1.1 <p>The following headers describe the purpose and format of the news item:</p>
261     <dl class="docutils">
262     <dt><tt class="docutils literal"><span class="pre">Title:</span></tt></dt>
263     <dd>A short (maximum 44 characters) descriptive title. Mandatory.</dd>
264     <dt><tt class="docutils literal"><span class="pre">Author:</span></tt></dt>
265     <dd>Author's name and email address, in the form <tt class="docutils literal"><span class="pre">Real</span> <span class="pre">Name</span> <span class="pre">&lt;email&#64;address&gt;</span></tt>.
266 ciaranm 1.4 Mandatory; multiple author headers may be specified if appropriate.</dd>
267 g2boojum 1.1 <dt><tt class="docutils literal"><span class="pre">Translator:</span></tt></dt>
268 ciaranm 1.4 <dd>For translated news items, the translator's name and email address. Multiple
269     translator headers may be specified if appropriate.</dd>
270 g2boojum 1.1 <dt><tt class="docutils literal"><span class="pre">Content-Type:</span></tt></dt>
271     <dd>Must be <tt class="docutils literal"><span class="pre">text/plain</span></tt>. Mandatory.</dd>
272     <dt><tt class="docutils literal"><span class="pre">Posted:</span></tt></dt>
273 ciaranm 1.6 <dd>Date of posting, in <tt class="docutils literal"><span class="pre">yyyy-mm-dd</span></tt> format (e.g. 2005-12-18) for
274 ciaranm 1.9 compatibility with GLEP 45 <a class="footnote-reference" href="#glep-45" id="id11" name="id11">[10]</a>. Translations should use the date
275     of the original news item. Mandatory.</dd>
276 ciaranm 1.4 <dt><tt class="docutils literal"><span class="pre">Revision:</span></tt></dt>
277 ciaranm 1.7 <dd>Initially 1. Should be incremented every time a change is made to the news
278     item. Changes that require a re-read of the news item (i.e., most changes
279     that are not spelling or formatting related) should instead use a new news
280     item. Mandatory.</dd>
281 g2boojum 1.1 <dt><tt class="docutils literal"><span class="pre">News-Item-Format:</span></tt></dt>
282     <dd>Must be <tt class="docutils literal"><span class="pre">1.0</span></tt>. Future revisions to the format may increment the minor
283     number for backwards-compatible changes, or the major number for major
284     changes.</dd>
285     </dl>
286 ciaranm 1.4 <p>The following headers are used for filtering:</p>
287 g2boojum 1.1 <dl class="docutils">
288     <dt><tt class="docutils literal"><span class="pre">Display-If-Installed:</span></tt></dt>
289 ciaranm 1.7 <dd>A dependency atom (for example, <tt class="docutils literal"><span class="pre">&lt;dev-lang/php-5_alpha</span></tt> or
290     <tt class="docutils literal"><span class="pre">net-www/apache</span></tt>). If the user has the package specified installed from
291     the repository from which the news item was obtained, the news item should
292     be displayed.</dd>
293 g2boojum 1.1 <dt><tt class="docutils literal"><span class="pre">Display-If-Keyword:</span></tt></dt>
294 ciaranm 1.6 <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
295 ciaranm 1.4 user is on the keyword in question, the news item should be displayed.</dd>
296 g2boojum 1.1 <dt><tt class="docutils literal"><span class="pre">Display-If-Profile:</span></tt></dt>
297 ciaranm 1.6 <dd>A profile path, for example <tt class="docutils literal"><span class="pre">default-linux/sparc/sparc64/server</span></tt>. If the
298 ciaranm 1.11 user is using the exact profile in question, the news item should be
299     displayed. This header may be used to replace <tt class="docutils literal"><span class="pre">deprecated</span></tt> files in the
300     future.</dd>
301 g2boojum 1.1 </dl>
302 ciaranm 1.4 <div class="note">
303     <p class="first admonition-title">Note</p>
304     <p class="last">When performing package moves, developers must also update any
305     relevant <tt class="docutils literal"><span class="pre">Display-If-Installed</span></tt> headers in news files.</p>
306     </div>
307     <p>The algorithm used to determine whether a news item is 'relevant' is as
308     follows:</p>
309     <ul class="simple">
310     <li>For each <tt class="docutils literal"><span class="pre">Display-If-</span></tt> header type which occurs at least once:<ul>
311     <li>The news item is not relevant if none of the headers of this type are
312     successfully matched.</li>
313     </ul>
314     </li>
315     <li>Otherwise the news item is relevant.</li>
316     </ul>
317     <p>In particular, if no <tt class="docutils literal"><span class="pre">Display-If-</span></tt> header is specified, a news item will be
318     relevant for all users.</p>
319     <p>This algorithm was chosen because it makes conditions like &quot;display this news
320     item for <tt class="docutils literal"><span class="pre">YourSQL</span></tt> users who are on <tt class="docutils literal"><span class="pre">sparc</span></tt> or <tt class="docutils literal"><span class="pre">x86-obsd</span></tt> relatively
321     simple to specify — it is believed that these kinds of condition are far more
322     likely to occur than &quot;display this news item for people using <tt class="docutils literal"><span class="pre">YourSQL</span></tt>, or
323     for 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
324     people 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>
325 g2boojum 1.1 </div>
326 g2boojum 1.8 <div class="section">
327 spb 1.12 <h3><a class="toc-backref" href="#id32" id="news-item-body" name="news-item-body">News Item Body</a></h3>
328 g2boojum 1.1 <p>The header section must be followed by a blank line, then the main body of the
329     text.</p>
330     <p>The text body should be wrapped at 72 characters. No fancy formatting or tab
331 ciaranm 1.4 characters should be used — the news item may be being displayed directly to a
332 ciaranm 1.2 terminal. Paragraphs should be separated by a blank line.</p>
333 g2boojum 1.1 <p>Hyperlinks may be used to refer to further information (for example, an upgrade
334     guide). However, the main body of the news item should be descriptive and not
335     simply a &quot;read this link&quot; text. It is assumed that the user will have access to
336     a web browser <em>somewhere</em>, but not necessarily on the box which is being
337 ciaranm 1.7 administrated — this will be the case on many servers and routers, for example.</p>
338 g2boojum 1.1 </div>
339 g2boojum 1.8 <div class="section">
340 spb 1.12 <h3><a class="toc-backref" href="#id33" id="example-news-item" name="example-news-item">Example News Item</a></h3>
341     <p><a class="reference" href="glep-0042-extras/example-news-item.txt">This hypothetical news item</a> <a class="footnote-reference" href="#id20" id="id21" name="id21">[18]</a> could be used for an upgrade to the
342 ciaranm 1.4 <tt class="docutils literal"><span class="pre">YourSQL</span></tt> database format which breaks forward compatibility.</p>
343 g2boojum 1.1 </div>
344     </div>
345 g2boojum 1.8 <div class="section">
346 spb 1.12 <h2><a class="toc-backref" href="#id34" id="news-item-quality-control" name="news-item-quality-control">News Item Quality Control</a></h2>
347 g2boojum 1.1 <p>There have been complaints regarding the comprehensibility of some upgrade
348 ciaranm 1.4 notices and news items in the past. This is understandable — not every Gentoo
349     developer speaks English as a first language. However, for the sake of clarity,
350     professionalism and avoiding making us look like prats, it is important that any
351     language problems be corrected before inflicting a news item upon end users.</p>
352     <p>Thus, at least 72 hours before a proposed news item is committed, it must be
353     posted 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>
354     (exceptions may be made in exceptional circumstances). Any complaints — for
355     example regarding wording, clarity or accuracy — <strong>must</strong> be addressed before
356     the news item goes live.</p>
357 g2boojum 1.1 <p>News items must only be for <strong>important</strong> changes that may cause serious upgrade
358     or compatibility problems. Ordinary upgrade messages and non-critical news items
359     should remain in <tt class="docutils literal"><span class="pre">einfo</span></tt> notices. The importance of the message to its
360     intended audience should be justified with the proposal.</p>
361     <div class="important">
362     <p class="first admonition-title">Important</p>
363     <p class="last">The filtering system means that it is appropriate to send out
364     news items which are aimed at users of an uncommon package or architecture.
365     Thus, the justification should be in the form &quot;this message is important to
366     YourSQL users because ...&quot;, not &quot;YourSQL is important because ...&quot;.</p>
367     </div>
368     </div>
369 g2boojum 1.8 <div class="section">
370 spb 1.12 <h2><a class="toc-backref" href="#id35" id="news-item-distribution" name="news-item-distribution">News Item Distribution</a></h2>
371 g2boojum 1.8 <div class="section">
372 spb 1.12 <h3><a class="toc-backref" href="#id36" id="server-side" name="server-side">Server Side</a></h3>
373 ciaranm 1.4 <p>News items are to be made available via the standard rsync tree. This removes
374     any need for polling of a remote source.</p>
375 g2boojum 1.1 <p>A new repository will be created for news items. The type (CVS or Subversion),
376     location and access controls on this repository are beyond the scope of this
377     GLEP.</p>
378     <div class="note">
379     <p class="first admonition-title">Note</p>
380     <p class="last">A previous draft of this GLEP instead used the main <tt class="docutils literal"><span class="pre">gentoo-x86</span></tt>
381     tree. This was changed following advice from Infrastructure
382 ciaranm 1.4 <a class="footnote-reference" href="#ramereth-repo" id="id14" name="id14">[12]</a>. Both solutions have the same end result.</p>
383 g2boojum 1.1 </div>
384 ciaranm 1.4 <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
385 g2boojum 1.1 the current year and <tt class="docutils literal"><span class="pre">mm</span></tt> is the current month number (01 for January through
386     12 for December). This separation will help keep news items more manageable.</p>
387     <p>The contents of this repository will automatically be merged with the main rsync
388 ciaranm 1.4 tree, placing the items in a <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory. The method used for
389 ciaranm 1.7 merging these items and the frequency at which it will occur is beyond the scope
390     of this GLEP; a similar setup is already used for merging GLSAs into the rsync
391     tree.</p>
392     <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
393     news item directories will all be immediately under the <tt class="docutils literal"><span class="pre">metadata/news/</span></tt>
394     directory.</p>
395 ciaranm 1.4 </div>
396 g2boojum 1.8 <div class="section">
397 spb 1.12 <h3><a class="toc-backref" href="#id37" id="client-side" name="client-side">Client Side</a></h3>
398 ciaranm 1.4 <p>Whenever relevant unread news items are found, the package manager will create a
399 ciaranm 1.7 file named <tt class="docutils literal"><span class="pre">/var/lib/gentoo/news/news-${repoid}.unread</span></tt> (if it does not
400 ciaranm 1.5 already exist) and append the news item identifier (eg
401     <tt class="docutils literal"><span class="pre">2005-11-01-yoursql-updates</span></tt>) on a new line.</p>
402 ciaranm 1.7 <p>All news item related files should be root owned and in the <tt class="docutils literal"><span class="pre">portage</span></tt> group
403     with the group write (and, for directories, execute) bits set. News files should
404     be world readable.</p>
405 g2boojum 1.1 <p>Notification that new relevant news items will be displayed via the
406     <tt class="docutils literal"><span class="pre">emerge</span></tt> tool in a similar way to the existing &quot;configuration files need
407     updating&quot; messages:</p>
408     <pre class="literal-block">
409     * Important: there are 5 unread news items.
410     * Type emerge --help news to learn how to read news files.
411     </pre>
412 ciaranm 1.4 <p>Checks for new news messages should be displayed:</p>
413     <ul class="simple">
414     <li>After an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">sync</span></tt></li>
415     <li>After an <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">--pretend</span></tt></li>
416     <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>
417     </ul>
418 ciaranm 1.7 <p>The package manager does not need to know how to launch the user's choice of
419     news client. This is consistent with the way configuration file updates are
420     handled.</p>
421 ciaranm 1.4 <p>The package manager may use a timestamp check file to avoid having to process
422     news items unnecessarily.</p>
423     <p>The package manager must keep track of news items that have already been added
424     to the unread list to avoid repeatedly marking a deleted news item. This could
425 ciaranm 1.7 be handled via a <tt class="docutils literal"><span class="pre">news-${repoid}.skip</span></tt> file containing the IDs of news items
426     that have already been added to a <tt class="docutils literal"><span class="pre">news-${repoid}.unread</span></tt> file, but this
427     method is not required by this GLEP.</p>
428 g2boojum 1.1 <p>Users who really don't care about news items can use <tt class="docutils literal"><span class="pre">rsync_excludes</span></tt> to
429 ciaranm 1.4 filter out the <tt class="docutils literal"><span class="pre">metadata/news/</span></tt> directory.</p>
430 g2boojum 1.1 </div>
431     </div>
432 g2boojum 1.8 <div class="section">
433 spb 1.12 <h2><a class="toc-backref" href="#id38" id="news-item-clients" name="news-item-clients">News Item Clients</a></h2>
434 ciaranm 1.4 <p>Once a news item is marked for reading, third party tools (or traditional core
435     Unix tools) can be used to display and view the news files.</p>
436 ciaranm 1.5 <p>When a news item is read, its name should be removed from the
437 ciaranm 1.9 <tt class="docutils literal"><span class="pre">news-${repoid}.unread</span></tt> file. If a news client acts as an interactive reader
438     rather than a gateway, it should then add the name to a <tt class="docutils literal"><span class="pre">news-${repoid}.read</span></tt>
439 ciaranm 1.6 file in the same directory with the same file format.</p>
440 ciaranm 1.4 <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
441     tool; other display tools (for example, a news to email forwarder, which would
442     be ideal for users who sync on a <tt class="docutils literal"><span class="pre">cron</span></tt>) are left as options for those who
443     desire them.</p>
444 g2boojum 1.1 </div>
445 g2boojum 1.8 <div class="section">
446 spb 1.12 <h2><a class="toc-backref" href="#id39" id="news-item-removal" name="news-item-removal">News Item Removal</a></h2>
447 g2boojum 1.1 <p>News items can be removed (by removing the news file from the main tree) when
448     they are no longer relevant, if they are made obsolete by a future news item or
449     after a long period of time. This is the same as the method used for <tt class="docutils literal"><span class="pre">updates</span></tt>
450     entries.</p>
451     </div>
452     </div>
453 g2boojum 1.8 <div class="section">
454 spb 1.12 <h1><a class="toc-backref" href="#id40" id="integration-with-existing-systems" name="integration-with-existing-systems">Integration with Existing Systems</a></h1>
455 ciaranm 1.4 <p>It would be simple to convert these news items into the format used for news
456 g2boojum 1.1 items on the Gentoo website or posts for the <tt class="docutils literal"><span class="pre">gentoo-announce</span></tt> mailing list.</p>
457 ciaranm 1.4 <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
458 g2boojum 1.1 forums. A similar tool can be used for these news items.</p>
459     </div>
460 g2boojum 1.8 <div class="section">
461 spb 1.12 <h1><a class="toc-backref" href="#id41" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1>
462 g2boojum 1.1 <p>Backwards compatibility is not a concern here. Existing tools will simply ignore
463     the <tt class="docutils literal"><span class="pre">news/</span></tt> directory.</p>
464     </div>
465 g2boojum 1.8 <div class="section">
466 spb 1.12 <h1><a class="toc-backref" href="#id42" id="reference-implementation" name="reference-implementation">Reference Implementation</a></h1>
467     <p>A reference implementation of the required package manager support can be found
468     in Paludis <a class="footnote-reference" href="#paludis" id="id17" name="id17">[15]</a>, along with a reference newsreader implemented as an
469     eselect module <a class="footnote-reference" href="#eselect-news" id="id18" name="id18">[16]</a>.</p>
470 g2boojum 1.1 </div>
471 g2boojum 1.8 <div class="section">
472 spb 1.12 <h1><a class="toc-backref" href="#id43" id="credits" name="credits">Credits</a></h1>
473 g2boojum 1.1 <p>The idea behind notifying users of news updates via Portage comes from Stuart
474 spb 1.12 Herbert <a class="footnote-reference" href="#stuart-blog" id="id19" name="id19">[17]</a>.</p>
475 ciaranm 1.4 <p>Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear,
476 ciaranm 1.7 Brian Harring, Marius Mauch, Dan Meltzer, Jason Stubbs, Paul de Vrieze and Alec
477     Warner for input. Some of the ideas presented here are theirs, others go
478     completely against their suggestions.</p>
479 ciaranm 1.4 </div>
480 g2boojum 1.8 <div class="section">
481 spb 1.12 <h1><a class="toc-backref" href="#id44" id="example-files" name="example-files">Example Files</a></h1>
482 ciaranm 1.9 <dl class="docutils">
483     <dt><a class="reference" href="glep-0042-extras/example-news-item.txt">example-news-item.txt</a></dt>
484     <dd>An example news item.</dd>
485     </dl>
486 g2boojum 1.1 </div>
487 g2boojum 1.8 <div class="section">
488 spb 1.12 <h1><a class="toc-backref" href="#id45" id="references" name="references">References</a></h1>
489 ciaranm 1.4 <table class="docutils footnote" frame="void" id="bug-11359" rules="none">
490     <colgroup><col class="label" /><col /></colgroup>
491     <tbody valign="top">
492     <tr><td class="label"><a class="fn-backref" href="#id1" name="bug-11359">[1]</a></td><td>Bugzilla Bug 11359
493     &quot;[NEW FEATURE] pkg_postinst/pkg_preinst ewarn/einfo logging&quot;,
494     <a class="reference" href="https://bugs.gentoo.org/show_bug.cgi?id=11359">https://bugs.gentoo.org/show_bug.cgi?id=11359</a></td></tr>
495     </tbody>
496     </table>
497 g2boojum 1.1 <table class="docutils footnote" frame="void" id="docs-policy" rules="none">
498     <colgroup><col class="label" /><col /></colgroup>
499     <tbody valign="top">
500 ciaranm 1.4 <tr><td class="label"><a class="fn-backref" href="#id8" name="docs-policy">[2]</a></td><td>Gentoo XML Guide, Daniel Robbins et al.,
501 g2boojum 1.1 <a class="reference" href="http://www.gentoo.org/doc/en/xml-guide.xml">http://www.gentoo.org/doc/en/xml-guide.xml</a></td></tr>
502     </tbody>
503     </table>
504     <table class="docutils footnote" frame="void" id="eselect" rules="none">
505     <colgroup><col class="label" /><col /></colgroup>
506     <tbody valign="top">
507 ciaranm 1.4 <tr><td class="label"><a class="fn-backref" href="#id15" name="eselect">[3]</a></td><td>eselect modular framework for configuration and
508 g2boojum 1.1 administration utilities,
509     <a class="reference" href="http://www.gentoo.org/proj/en/eselect/index.xml">http://www.gentoo.org/proj/en/eselect/index.xml</a></td></tr>
510     </tbody>
511     </table>
512     <table class="docutils footnote" frame="void" id="forums-glsa" rules="none">
513     <colgroup><col class="label" /><col /></colgroup>
514     <tbody valign="top">
515 ciaranm 1.4 <tr><td class="label"><a class="fn-backref" href="#id16" name="forums-glsa">[4]</a></td><td>Forums user GLSA,
516 g2boojum 1.1 <a class="reference" href="http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=55648">http://forums.gentoo.org/profile.php?mode=viewprofile&amp;u=55648</a></td></tr>
517     </tbody>
518     </table>
519 ciaranm 1.4 <table class="docutils footnote" frame="void" id="forums-apache2" rules="none">
520 g2boojum 1.1 <colgroup><col class="label" /><col /></colgroup>
521     <tbody valign="top">
522 ciaranm 1.4 <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;,
523 g2boojum 1.1 <a class="reference" href="http://forums.gentoo.org/viewtopic-t-384368.html">http://forums.gentoo.org/viewtopic-t-384368.html</a></td></tr>
524     </tbody>
525     </table>
526     <table class="docutils footnote" frame="void" id="glep-22" rules="none">
527     <colgroup><col class="label" /><col /></colgroup>
528     <tbody valign="top">
529 ciaranm 1.6 <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
530 g2boojum 1.1 userlands/kernels/archs&quot;, Grant Goodyear,
531     <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>
532     </tbody>
533     </table>
534     <table class="docutils footnote" frame="void" id="glep-31" rules="none">
535     <colgroup><col class="label" /><col /></colgroup>
536     <tbody valign="top">
537 ciaranm 1.6 <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
538 g2boojum 1.1 McCreesh,
539     <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>
540     </tbody>
541     </table>
542     <table class="docutils footnote" frame="void" id="glep-34" rules="none">
543     <colgroup><col class="label" /><col /></colgroup>
544     <tbody valign="top">
545 ciaranm 1.6 <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,
546 g2boojum 1.1 <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>
547     </tbody>
548     </table>
549     <table class="docutils footnote" frame="void" id="glep-36" rules="none">
550     <colgroup><col class="label" /><col /></colgroup>
551     <tbody valign="top">
552 ciaranm 1.6 <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
553 g2boojum 1.1 Walker,
554     <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>
555     </tbody>
556     </table>
557 ciaranm 1.6 <table class="docutils footnote" frame="void" id="glep-45" rules="none">
558     <colgroup><col class="label" /><col /></colgroup>
559     <tbody valign="top">
560     <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,
561     <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>
562     </tbody>
563     </table>
564 g2boojum 1.1 <table class="docutils footnote" frame="void" id="iso-639" rules="none">
565     <colgroup><col class="label" /><col /></colgroup>
566     <tbody valign="top">
567 ciaranm 1.4 <tr><td class="label"><a class="fn-backref" href="#id5" name="iso-639">[11]</a></td><td>ISO 639 &quot;Code for the representation of names of languages&quot;</td></tr>
568 g2boojum 1.1 </tbody>
569     </table>
570     <table class="docutils footnote" frame="void" id="ramereth-repo" rules="none">
571     <colgroup><col class="label" /><col /></colgroup>
572     <tbody valign="top">
573 ciaranm 1.4 <tr><td class="label"><a class="fn-backref" href="#id14" name="ramereth-repo">[12]</a></td><td>&quot;Re: [gentoo-dev] GLEP ??: Critical News Reporting&quot;, Lance
574 g2boojum 1.1 Albertson,
575     <a class="reference" href="http://marc.theaimsgroup.com/?l=gentoo-dev&amp;m=113111585907703&amp;w=2">http://marc.theaimsgroup.com/?l=gentoo-dev&amp;m=113111585907703&amp;w=2</a></td></tr>
576     </tbody>
577     </table>
578     <table class="docutils footnote" frame="void" id="rfc-822" rules="none">
579     <colgroup><col class="label" /><col /></colgroup>
580     <tbody valign="top">
581 ciaranm 1.4 <tr><td class="label"><a class="fn-backref" href="#id10" name="rfc-822">[13]</a></td><td><a class="reference" href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> &quot;Standard for the format of ARPA Internet text messages&quot;</td></tr>
582     </tbody>
583     </table>
584     <table class="docutils footnote" frame="void" id="rfc-3629" rules="none">
585     <colgroup><col class="label" /><col /></colgroup>
586     <tbody valign="top">
587     <tr><td class="label"><a class="fn-backref" href="#id7" name="rfc-3629">[14]</a></td><td><a class="reference" href="http://www.faqs.org/rfcs/rfc3629.html">RFC 3629</a>: &quot;UTF-8, a transformation format of ISO 10646&quot;
588     <a class="reference" href="http://www.ietf.org/rfc/rfc3629.txt">http://www.ietf.org/rfc/rfc3629.txt</a></td></tr>
589 g2boojum 1.1 </tbody>
590     </table>
591 spb 1.12 <table class="docutils footnote" frame="void" id="paludis" rules="none">
592     <colgroup><col class="label" /><col /></colgroup>
593     <tbody valign="top">
594     <tr><td class="label"><a class="fn-backref" href="#id17" name="paludis">[15]</a></td><td>Paludis homepage, <a class="reference" href="http://paludis.berlios.de">http://paludis.berlios.de</a></td></tr>
595     </tbody>
596     </table>
597     <table class="docutils footnote" frame="void" id="eselect-news" rules="none">
598     <colgroup><col class="label" /><col /></colgroup>
599     <tbody valign="top">
600     <tr><td class="label"><a class="fn-backref" href="#id18" name="eselect-news">[16]</a></td><td>news.eselect, <a class="reference" href="http://svn.berlios.de/svnroot/repos/paludis/trunk/eselect/news.eselect">http://svn.berlios.de/svnroot/repos/paludis/trunk/eselect/news.eselect</a></td></tr>
601     </tbody>
602     </table>
603 g2boojum 1.1 <table class="docutils footnote" frame="void" id="stuart-blog" rules="none">
604     <colgroup><col class="label" /><col /></colgroup>
605     <tbody valign="top">
606 spb 1.12 <tr><td class="label"><a class="fn-backref" href="#id19" name="stuart-blog">[17]</a></td><td>&quot;Favouring an automatic news mechanism&quot;, Stuart Herbert,
607 g2boojum 1.1 <a class="reference" href="http://stu.gnqs.org/diary/gentoo.php/2005/10/28/favouring_an_automatic_news_mechanism">http://stu.gnqs.org/diary/gentoo.php/2005/10/28/favouring_an_automatic_news_mechanism</a></td></tr>
608     </tbody>
609     </table>
610 spb 1.12 <table class="docutils footnote" frame="void" id="id20" rules="none">
611 ciaranm 1.4 <colgroup><col class="label" /><col /></colgroup>
612     <tbody valign="top">
613 spb 1.12 <tr><td class="label"><a class="fn-backref" href="#id21" name="id20">[18]</a></td><td><a class="reference" href="glep-0042-extras/example-news-item.txt">glep-0042-extras/example-news-item.txt</a></td></tr>
614 ciaranm 1.4 </tbody>
615     </table>
616 g2boojum 1.1 </div>
617 g2boojum 1.8 <div class="section">
618 spb 1.12 <h1><a class="toc-backref" href="#id46" id="copyright" name="copyright">Copyright</a></h1>
619 g2boojum 1.1 <p>This document has been placed in the public domain.</p>
620     <!-- vim: set tw=80 fileencoding=utf-8 spell spelllang=en et : -->
621     </div>
622    
623     </div>
624     <div class="footer">
625     <hr class="footer" />
626     <a class="reference" href="glep-0042.txt">View document source</a>.
627 antarus 1.18 Generated on: 2007-10-13 13:39 UTC.
628 g2boojum 1.1 Generated 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.
629    
630     </div>
631     </body>
632     </html>

  ViewVC Help
Powered by ViewVC 1.1.20