| … | |
… | |
| 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
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"> |
3 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> |
| 4 | |
4 | |
| 5 | <head> |
5 | <head> |
| 6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
| 7 | <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" /> |
7 | <meta name="generator" content="Docutils 0.5: http://docutils.sourceforge.net/" /> |
| 8 | <title>GLEP 44 -- Manifest2 format</title> |
8 | <title>GLEP 44 -- Manifest2 format</title> |
| 9 | <link rel="stylesheet" href="tools/glep.css" type="text/css" /> |
9 | <link rel="stylesheet" href="tools/glep.css" type="text/css" /></head> |
| 10 | </head> |
|
|
| 11 | <body bgcolor="white"> |
10 | <body bgcolor="white"> |
| 12 | <table class="navigation" cellpadding="0" cellspacing="0" |
11 | <table class="navigation" cellpadding="0" cellspacing="0" |
| 13 | width="100%" border="0"> |
12 | width="100%" border="0"> |
| 14 | <tr><td class="navicon" width="150" height="35"> |
13 | <tr><td class="navicon" width="150" height="35"> |
| 15 | <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page"> |
14 | <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page"> |
| … | |
… | |
| 28 | </tr> |
27 | </tr> |
| 29 | <tr class="field"><th class="field-name">Title:</th><td class="field-body">Manifest2 format</td> |
28 | <tr class="field"><th class="field-name">Title:</th><td class="field-body">Manifest2 format</td> |
| 30 | </tr> |
29 | </tr> |
| 31 | <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.7</td> |
30 | <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.7</td> |
| 32 | </tr> |
31 | </tr> |
| 33 | <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-0044.txt?cvsroot=gentoo">2006/10/14 02:55:39</a></td> |
32 | <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference external" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0044.txt?cvsroot=gentoo">2006/10/14 02:55:39</a></td> |
| 34 | </tr> |
33 | </tr> |
| 35 | <tr class="field"><th class="field-name">Author:</th><td class="field-body">Marius Mauch <genone at gentoo.org>,</td> |
34 | <tr class="field"><th class="field-name">Author:</th><td class="field-body">Marius Mauch <genone at gentoo.org>,</td> |
| 36 | </tr> |
35 | </tr> |
| 37 | <tr class="field"><th class="field-name">Status:</th><td class="field-body">Accepted</td> |
36 | <tr class="field"><th class="field-name">Status:</th><td class="field-body">Final</td> |
| 38 | </tr> |
37 | </tr> |
| 39 | <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> |
38 | <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> |
| 40 | </tr> |
39 | </tr> |
| 41 | <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> |
40 | <tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference external" href="glep-0002.html">text/x-rst</a></td> |
| 42 | </tr> |
41 | </tr> |
| 43 | <tr class="field"><th class="field-name">Created:</th><td class="field-body">04-Dec-2005</td> |
42 | <tr class="field"><th class="field-name">Created:</th><td class="field-body">04-Dec-2005</td> |
| 44 | </tr> |
43 | </tr> |
| 45 | <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">06-Dec-2005, 23-Jan-2006, 3-Sep-2006</td> |
44 | <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">06-Dec-2005, 23-Jan-2006, 3-Sep-2006</td> |
| 46 | </tr> |
45 | </tr> |
| 47 | </tbody> |
46 | </tbody> |
| 48 | </table> |
47 | </table> |
| 49 | <hr /> |
48 | <hr /> |
| 50 | <div class="contents topic"> |
49 | <div class="contents topic" id="contents"> |
| 51 | <p class="topic-title first"><a id="contents" name="contents">Contents</a></p> |
50 | <p class="topic-title first">Contents</p> |
| 52 | <ul class="simple"> |
51 | <ul class="simple"> |
| 53 | <li><a class="reference" href="#abstract" id="id9" name="id9">Abstract</a></li> |
52 | <li><a class="reference internal" href="#abstract" id="id9">Abstract</a></li> |
| 54 | <li><a class="reference" href="#motivation" id="id10" name="id10">Motivation</a></li> |
53 | <li><a class="reference internal" href="#motivation" id="id10">Motivation</a></li> |
| 55 | <li><a class="reference" href="#specification" id="id11" name="id11">Specification</a><ul> |
54 | <li><a class="reference internal" href="#specification" id="id11">Specification</a><ul> |
| 56 | <li><a class="reference" href="#compability-entries" id="id12" name="id12">Compability Entries</a></li> |
55 | <li><a class="reference internal" href="#compability-entries" id="id12">Compability Entries</a></li> |
| 57 | <li><a class="reference" href="#scope" id="id13" name="id13">Scope</a></li> |
56 | <li><a class="reference internal" href="#scope" id="id13">Scope</a></li> |
| 58 | <li><a class="reference" href="#number-of-hashes" id="id14" name="id14">Number of hashes</a></li> |
57 | <li><a class="reference internal" href="#number-of-hashes" id="id14">Number of hashes</a></li> |
| 59 | </ul> |
|
|
| 60 | </li> |
58 | </ul> |
|
|
59 | </li> |
| 61 | <li><a class="reference" href="#rationale" id="id15" name="id15">Rationale</a><ul> |
60 | <li><a class="reference internal" href="#rationale" id="id15">Rationale</a><ul> |
| 62 | <li><a class="reference" href="#removal-of-digest-files" id="id16" name="id16">Removal of digest files</a></li> |
61 | <li><a class="reference internal" href="#removal-of-digest-files" id="id16">Removal of digest files</a></li> |
| 63 | <li><a class="reference" href="#reducing-redundancy" id="id17" name="id17">Reducing redundancy</a></li> |
62 | <li><a class="reference internal" href="#reducing-redundancy" id="id17">Reducing redundancy</a></li> |
| 64 | <li><a class="reference" href="#removal-of-checksum-collisions" id="id18" name="id18">Removal of checksum collisions</a></li> |
63 | <li><a class="reference internal" href="#removal-of-checksum-collisions" id="id18">Removal of checksum collisions</a></li> |
| 65 | <li><a class="reference" href="#flexible-verification-system" id="id19" name="id19">Flexible verification system</a></li> |
64 | <li><a class="reference internal" href="#flexible-verification-system" id="id19">Flexible verification system</a></li> |
| 66 | </ul> |
|
|
| 67 | </li> |
65 | </ul> |
|
|
66 | </li> |
| 68 | <li><a class="reference" href="#backwards-compatibility" id="id20" name="id20">Backwards Compatibility</a></li> |
67 | <li><a class="reference internal" href="#backwards-compatibility" id="id20">Backwards Compatibility</a></li> |
| 69 | <li><a class="reference" href="#other-problems" id="id21" name="id21">Other problems</a><ul> |
68 | <li><a class="reference internal" href="#other-problems" id="id21">Other problems</a><ul> |
| 70 | <li><a class="reference" href="#impacts-on-infrastructure" id="id22" name="id22">Impacts on infrastructure</a></li> |
69 | <li><a class="reference internal" href="#impacts-on-infrastructure" id="id22">Impacts on infrastructure</a></li> |
| 71 | </ul> |
|
|
| 72 | </li> |
70 | </ul> |
|
|
71 | </li> |
| 73 | <li><a class="reference" href="#reference-implementation" id="id23" name="id23">Reference Implementation</a></li> |
72 | <li><a class="reference internal" href="#reference-implementation" id="id23">Reference Implementation</a></li> |
| 74 | <li><a class="reference" href="#options" id="id24" name="id24">Options</a></li> |
73 | <li><a class="reference internal" href="#options" id="id24">Options</a></li> |
| 75 | <li><a class="reference" href="#credits" id="id25" name="id25">Credits</a></li> |
74 | <li><a class="reference internal" href="#credits" id="id25">Credits</a></li> |
| 76 | <li><a class="reference" href="#references" id="id26" name="id26">References</a></li> |
75 | <li><a class="reference internal" href="#references" id="id26">References</a></li> |
| 77 | <li><a class="reference" href="#copyright" id="id27" name="id27">Copyright</a></li> |
76 | <li><a class="reference internal" href="#copyright" id="id27">Copyright</a></li> |
| 78 | </ul> |
77 | </ul> |
| 79 | </div> |
78 | </div> |
| 80 | <div class="section"> |
79 | <div class="section" id="abstract"> |
| 81 | <h1><a class="toc-backref" href="#id9" id="abstract" name="abstract">Abstract</a></h1> |
80 | <h1><a class="toc-backref" href="#id9">Abstract</a></h1> |
| 82 | <p>This GLEP proposes a new format for the Portage Manifest and digest file system |
81 | <p>This GLEP proposes a new format for the Portage Manifest and digest file system |
| 83 | by unifying both filetypes into one to improve functional and non-functional |
82 | by unifying both filetypes into one to improve functional and non-functional |
| 84 | aspects of the Portage Tree.</p> |
83 | aspects of the Portage Tree.</p> |
| 85 | </div> |
84 | </div> |
| 86 | <div class="section"> |
85 | <div class="section" id="motivation"> |
| 87 | <h1><a class="toc-backref" href="#id10" id="motivation" name="motivation">Motivation</a></h1> |
86 | <h1><a class="toc-backref" href="#id10">Motivation</a></h1> |
| 88 | <p>Please see <a class="footnote-reference" href="#reorg-thread" id="id1" name="id1">[1]</a> for a general overview. |
87 | <p>Please see <a class="footnote-reference" href="#reorg-thread" id="id1">[1]</a> for a general overview. |
| 89 | The main long term goals of this proposal are to:</p> |
88 | The main long term goals of this proposal are to:</p> |
| 90 | <ul class="simple"> |
89 | <ul class="simple"> |
| 91 | <li>Remove the tiny digest files from the tree. They are a major annoyance as on a |
90 | <li>Remove the tiny digest files from the tree. They are a major annoyance as on a |
| 92 | typical configuration they waste a lot of disk space and the simple transmission |
91 | typical configuration they waste a lot of disk space and the simple transmission |
| 93 | of the names for all digest files during a <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">--sync</span></tt> needs a substantial |
92 | of the names for all digest files during a <tt class="docutils literal"><span class="pre">emerge</span> <span class="pre">--sync</span></tt> needs a substantial |
| … | |
… | |
| 96 | <li>Remove potential for checksum collisions if a file is recorded in more than one |
95 | <li>Remove potential for checksum collisions if a file is recorded in more than one |
| 97 | digest file</li> |
96 | digest file</li> |
| 98 | <li>Difference between filetypes for a more flexible verification system</li> |
97 | <li>Difference between filetypes for a more flexible verification system</li> |
| 99 | </ul> |
98 | </ul> |
| 100 | </div> |
99 | </div> |
| 101 | <div class="section"> |
100 | <div class="section" id="specification"> |
| 102 | <h1><a class="toc-backref" href="#id11" id="specification" name="specification">Specification</a></h1> |
101 | <h1><a class="toc-backref" href="#id11">Specification</a></h1> |
| 103 | <p>The new Manifest format would change the existing format in the following ways:</p> |
102 | <p>The new Manifest format would change the existing format in the following ways:</p> |
| 104 | <ul> |
103 | <ul> |
| 105 | <li><p class="first">Addition of a filetype specifier, currently planned are</p> |
104 | <li><p class="first">Addition of a filetype specifier, currently planned are</p> |
| 106 | <ul class="simple"> |
105 | <ul class="simple"> |
| 107 | <li><tt class="docutils literal"><span class="pre">AUX</span></tt> for files directly used by ebuilds (e.g. patches or initscripts), |
106 | <li><tt class="docutils literal"><span class="pre">AUX</span></tt> for files directly used by ebuilds (e.g. patches or initscripts), |
| … | |
… | |
| 124 | <p>Each line in the new format has the following format:</p> |
123 | <p>Each line in the new format has the following format:</p> |
| 125 | <pre class="literal-block"> |
124 | <pre class="literal-block"> |
| 126 | <filetype> <filename> <filesize> <chksumtype1> <chksum1> ... <chksumtypen> <chksumn> |
125 | <filetype> <filename> <filesize> <chksumtype1> <chksum1> ... <chksumtypen> <chksumn> |
| 127 | </pre> |
126 | </pre> |
| 128 | <p>However theses entries will be stored in the existing Manifest files.</p> |
127 | <p>However theses entries will be stored in the existing Manifest files.</p> |
| 129 | <p>An <a class="reference" href="glep-0044-extras/manifest2-example.txt">actual example</a> <a class="footnote-reference" href="#id7" id="id8" name="id8">[6]</a> for a (pure) Manifest2 file..</p> |
128 | <p>An <a class="reference external" href="glep-0044-extras/manifest2-example.txt">actual example</a> <a class="footnote-reference" href="#id7" id="id8">[6]</a> for a (pure) Manifest2 file..</p> |
| 130 | <div class="section"> |
129 | <div class="section" id="compability-entries"> |
| 131 | <h2><a class="toc-backref" href="#id12" id="compability-entries" name="compability-entries">Compability Entries</a></h2> |
130 | <h2><a class="toc-backref" href="#id12">Compability Entries</a></h2> |
| 132 | <p>To maintain compability with existing portage versions a transition period after |
131 | <p>To maintain compability with existing portage versions a transition period after |
| 133 | is the introduction of the Manifest2 format is required during which portage |
132 | is the introduction of the Manifest2 format is required during which portage |
| 134 | will not only have to be capable of using existing Manifest and digest files but |
133 | will not only have to be capable of using existing Manifest and digest files but |
| 135 | also generate them in addition to the new entries. |
134 | also generate them in addition to the new entries. |
| 136 | Fortunately this can be accomplished by simply mixing old and new style entries |
135 | Fortunately this can be accomplished by simply mixing old and new style entries |
| 137 | in one file for the Manifest files, existing portage versions will simply ignore |
136 | in one file for the Manifest files, existing portage versions will simply ignore |
| 138 | the new style entries. For the digest files there are no new entries to care |
137 | the new style entries. For the digest files there are no new entries to care |
| 139 | about.</p> |
138 | about.</p> |
| 140 | </div> |
139 | </div> |
| 141 | <div class="section"> |
140 | <div class="section" id="scope"> |
| 142 | <h2><a class="toc-backref" href="#id13" id="scope" name="scope">Scope</a></h2> |
141 | <h2><a class="toc-backref" href="#id13">Scope</a></h2> |
| 143 | <p>It is important to note that this proposal only deals with a change of the |
142 | <p>It is important to note that this proposal only deals with a change of the |
| 144 | format of the digest and Manifest system.</p> |
143 | format of the digest and Manifest system.</p> |
| 145 | <p>It does not expand the scope of it to cover eclasses, profiles or anything |
144 | <p>It does not expand the scope of it to cover eclasses, profiles or anything |
| 146 | else not already covered by the Manifest system, it also doesn't affect |
145 | else not already covered by the Manifest system, it also doesn't affect |
| 147 | the Manifest signing efforts in any way (though the implementations of both |
146 | the Manifest signing efforts in any way (though the implementations of both |
| 148 | might be coupled).</p> |
147 | might be coupled).</p> |
| 149 | <p>Also while multiple hash functions will become standard with the proposed |
148 | <p>Also while multiple hash functions will become standard with the proposed |
| 150 | implementation they are not a specific feature of this format <a class="footnote-reference" href="#multi-hash-thread" id="id3" name="id3">[2]</a>.</p> |
149 | implementation they are not a specific feature of this format <a class="footnote-reference" href="#multi-hash-thread" id="id3">[2]</a>.</p> |
| 151 | </div> |
150 | </div> |
| 152 | <div class="section"> |
151 | <div class="section" id="number-of-hashes"> |
| 153 | <h2><a class="toc-backref" href="#id14" id="number-of-hashes" name="number-of-hashes">Number of hashes</a></h2> |
152 | <h2><a class="toc-backref" href="#id14">Number of hashes</a></h2> |
| 154 | <p>While using multiple hashes for each file is a major feature of this proposal |
153 | <p>While using multiple hashes for each file is a major feature of this proposal |
| 155 | we have to make sure that the number of hashes listed is limited to avoid |
154 | we have to make sure that the number of hashes listed is limited to avoid |
| 156 | an explosion of the Manifest size that would revert the main benefit of this proposal |
155 | an explosion of the Manifest size that would revert the main benefit of this proposal |
| 157 | (reduzing tree size). Therefore the number of hashes that will be generated |
156 | (reduzing tree size). Therefore the number of hashes that will be generated |
| 158 | will be limited to three different hash functions. For compability though we |
157 | will be limited to three different hash functions. For compability though we |
| … | |
… | |
| 160 | suggest to use SHA1 for this purpose (as it is supposed to be more secure than MD5 |
159 | suggest to use SHA1 for this purpose (as it is supposed to be more secure than MD5 |
| 161 | and currently only SHA1 and MD5 are directly available in python, also MD5 doesn't |
160 | and currently only SHA1 and MD5 are directly available in python, also MD5 doesn't |
| 162 | have any benefit in terms of compability).</p> |
161 | have any benefit in terms of compability).</p> |
| 163 | </div> |
162 | </div> |
| 164 | </div> |
163 | </div> |
| 165 | <div class="section"> |
164 | <div class="section" id="rationale"> |
| 166 | <h1><a class="toc-backref" href="#id15" id="rationale" name="rationale">Rationale</a></h1> |
165 | <h1><a class="toc-backref" href="#id15">Rationale</a></h1> |
| 167 | <p>The main goals of the proposal have been listed in the <a class="reference" href="#motivation">Motivation</a>, here now |
166 | <p>The main goals of the proposal have been listed in the <a class="reference internal" href="#motivation">Motivation</a>, here now |
| 168 | the explanation why they are improvements and how the proposed format will |
167 | the explanation why they are improvements and how the proposed format will |
| 169 | accomplish them.</p> |
168 | accomplish them.</p> |
| 170 | <div class="section"> |
169 | <div class="section" id="removal-of-digest-files"> |
| 171 | <h2><a class="toc-backref" href="#id16" id="removal-of-digest-files" name="removal-of-digest-files">Removal of digest files</a></h2> |
170 | <h2><a class="toc-backref" href="#id16">Removal of digest files</a></h2> |
| 172 | <p>Normal users that don't use a "tuned" filesystem for the portage tree are |
171 | <p>Normal users that don't use a "tuned" filesystem for the portage tree are |
| 173 | wasting several dozen to a few hundred megabytes of disk space with the current |
172 | wasting several dozen to a few hundred megabytes of disk space with the current |
| 174 | system, largely caused by the digest files. |
173 | system, largely caused by the digest files. |
| 175 | This is due to the filesystem overhead present in most filesystem that |
174 | This is due to the filesystem overhead present in most filesystem that |
| 176 | have a standard blocksize of four kilobytes while most digest files are under |
175 | have a standard blocksize of four kilobytes while most digest files are under |
| … | |
… | |
| 183 | verified yet.</p> |
182 | verified yet.</p> |
| 184 | <p>By unifying the digest files with the Manifest these tiny files are eliminated |
183 | <p>By unifying the digest files with the Manifest these tiny files are eliminated |
| 185 | (in the long run), reducing the apparent tree size by about 20%, benefitting |
184 | (in the long run), reducing the apparent tree size by about 20%, benefitting |
| 186 | both users and the Gentoo infrastructure.</p> |
185 | both users and the Gentoo infrastructure.</p> |
| 187 | </div> |
186 | </div> |
| 188 | <div class="section"> |
187 | <div class="section" id="reducing-redundancy"> |
| 189 | <h2><a class="toc-backref" href="#id17" id="reducing-redundancy" name="reducing-redundancy">Reducing redundancy</a></h2> |
188 | <h2><a class="toc-backref" href="#id17">Reducing redundancy</a></h2> |
| 190 | <p>When multiple hashes are used with the current system |
189 | <p>When multiple hashes are used with the current system |
| 191 | both the filename and filesize are repeated for every checksum type used as each |
190 | both the filename and filesize are repeated for every checksum type used as each |
| 192 | checksum is standalone. However this doesn't add any functionality and is |
191 | checksum is standalone. However this doesn't add any functionality and is |
| 193 | therefore useless, so the new format removes this redundancy. |
192 | therefore useless, so the new format removes this redundancy. |
| 194 | This is a theoretical improvement at this moment as only one hash function is in |
193 | This is a theoretical improvement at this moment as only one hash function is in |
| 195 | use, but expected to change soon (see <a class="footnote-reference" href="#multi-hash-thread" id="id4" name="id4">[2]</a>).</p> |
194 | use, but expected to change soon (see <a class="footnote-reference" href="#multi-hash-thread" id="id4">[2]</a>).</p> |
| 196 | </div> |
195 | </div> |
| 197 | <div class="section"> |
196 | <div class="section" id="removal-of-checksum-collisions"> |
| 198 | <h2><a class="toc-backref" href="#id18" id="removal-of-checksum-collisions" name="removal-of-checksum-collisions">Removal of checksum collisions</a></h2> |
197 | <h2><a class="toc-backref" href="#id18">Removal of checksum collisions</a></h2> |
| 199 | <p>The current system theoretically allows for a <tt class="docutils literal"><span class="pre">DIST</span></tt> type file to be recorded |
198 | <p>The current system theoretically allows for a <tt class="docutils literal"><span class="pre">DIST</span></tt> type file to be recorded |
| 200 | in multiple digest files with different sizes and/or checksums. In such a case |
199 | in multiple digest files with different sizes and/or checksums. In such a case |
| 201 | one version of a package would report a checksum violation while another one |
200 | one version of a package would report a checksum violation while another one |
| 202 | would not. This could create confusion and uncertainity among users. |
201 | would not. This could create confusion and uncertainity among users. |
| 203 | So far this case hasn't been observed, but it can't be ruled out with the |
202 | So far this case hasn't been observed, but it can't be ruled out with the |
| 204 | existing system. |
203 | existing system. |
| 205 | As the new format lists each file exactly once this would be no longer possible.</p> |
204 | As the new format lists each file exactly once this would be no longer possible.</p> |
| 206 | </div> |
205 | </div> |
| 207 | <div class="section"> |
206 | <div class="section" id="flexible-verification-system"> |
| 208 | <h2><a class="toc-backref" href="#id19" id="flexible-verification-system" name="flexible-verification-system">Flexible verification system</a></h2> |
207 | <h2><a class="toc-backref" href="#id19">Flexible verification system</a></h2> |
| 209 | <p>Right now portage verifies the checksum of every file listed in the Manifest |
208 | <p>Right now portage verifies the checksum of every file listed in the Manifest |
| 210 | before using any file of the package and all <tt class="docutils literal"><span class="pre">DIST</span></tt> files of an ebuild |
209 | before using any file of the package and all <tt class="docutils literal"><span class="pre">DIST</span></tt> files of an ebuild |
| 211 | before using that ebuild. This is unnecessary in many cases:</p> |
210 | before using that ebuild. This is unnecessary in many cases:</p> |
| 212 | <ul class="simple"> |
211 | <ul class="simple"> |
| 213 | <li>During the "depend" phase (when the ebuild metadata is generated) only |
212 | <li>During the "depend" phase (when the ebuild metadata is generated) only |
| … | |
… | |
| 224 | before unpacking them (which often will be one step), not every time their |
223 | before unpacking them (which often will be one step), not every time their |
| 225 | associated ebuild is used.</li> |
224 | associated ebuild is used.</li> |
| 226 | </ul> |
225 | </ul> |
| 227 | </div> |
226 | </div> |
| 228 | </div> |
227 | </div> |
| 229 | <div class="section"> |
228 | <div class="section" id="backwards-compatibility"> |
| 230 | <h1><a class="toc-backref" href="#id20" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1> |
229 | <h1><a class="toc-backref" href="#id20">Backwards Compatibility</a></h1> |
| 231 | <p>Switching the Manifest system is a task that will need a long transition period |
230 | <p>Switching the Manifest system is a task that will need a long transition period |
| 232 | like most changes affecting both portage and the tree. In this case the |
231 | like most changes affecting both portage and the tree. In this case the |
| 233 | implementation will be rolled out in several phases:</p> |
232 | implementation will be rolled out in several phases:</p> |
| 234 | <ol class="arabic simple"> |
233 | <ol class="arabic simple"> |
| 235 | <li>Add support for verification of Manifest2 entries in portage</li> |
234 | <li>Add support for verification of Manifest2 entries in portage</li> |
| … | |
… | |
| 267 | on the completion of each step.</p> |
266 | on the completion of each step.</p> |
| 268 | <p>In summary it can be said that while a full conversion will take over a year |
267 | <p>In summary it can be said that while a full conversion will take over a year |
| 269 | to be completed due to compability issues mentioned above some benefits of the |
268 | to be completed due to compability issues mentioned above some benefits of the |
| 270 | system can selectively be used as soon as step 2) is completed.</p> |
269 | system can selectively be used as soon as step 2) is completed.</p> |
| 271 | </div> |
270 | </div> |
| 272 | <div class="section"> |
271 | <div class="section" id="other-problems"> |
| 273 | <h1><a class="toc-backref" href="#id21" id="other-problems" name="other-problems">Other problems</a></h1> |
272 | <h1><a class="toc-backref" href="#id21">Other problems</a></h1> |
| 274 | <div class="section"> |
273 | <div class="section" id="impacts-on-infrastructure"> |
| 275 | <h2><a class="toc-backref" href="#id22" id="impacts-on-infrastructure" name="impacts-on-infrastructure">Impacts on infrastructure</a></h2> |
274 | <h2><a class="toc-backref" href="#id22">Impacts on infrastructure</a></h2> |
| 276 | <p>While one long term goal of this proposal is to reduce the size of the tree |
275 | <p>While one long term goal of this proposal is to reduce the size of the tree |
| 277 | and therefore make life for the Gentoo Infrastructure easier this will only |
276 | and therefore make life for the Gentoo Infrastructure easier this will only |
| 278 | take effect once the implementation is rolled out completely. In the meantime |
277 | take effect once the implementation is rolled out completely. In the meantime |
| 279 | however it will increase the tree size due to keeping checksums in both formats. |
278 | however it will increase the tree size due to keeping checksums in both formats. |
| 280 | It's not possible to give a usable estimate on the degree of the increase as |
279 | It's not possible to give a usable estimate on the degree of the increase as |
| 281 | it depends on many variables such as the exact implementation timeframe, |
280 | it depends on many variables such as the exact implementation timeframe, |
| 282 | propagation of Manifest2 capable portage versions among devs or the update |
281 | propagation of Manifest2 capable portage versions among devs or the update |
| 283 | rate of the tree. It has been suggested that Manifest files that are not gpg |
282 | rate of the tree. It has been suggested that Manifest files that are not gpg |
| 284 | signed could be mass converted in one step, this could certainly help but only |
283 | signed could be mass converted in one step, this could certainly help but only |
| 285 | to some degree (according to a recent research <a class="footnote-reference" href="#gpg-numbers" id="id5" name="id5">[3]</a> about 40% of |
284 | to some degree (according to a recent research <a class="footnote-reference" href="#gpg-numbers" id="id5">[3]</a> about 40% of |
| 286 | all Manifests in the tree are signed, but this number hasn't been verified).</p> |
285 | all Manifests in the tree are signed, but this number hasn't been verified).</p> |
| 287 | </div> |
286 | </div> |
| 288 | </div> |
287 | </div> |
| 289 | <div class="section"> |
288 | <div class="section" id="reference-implementation"> |
| 290 | <h1><a class="toc-backref" href="#id23" id="reference-implementation" name="reference-implementation">Reference Implementation</a></h1> |
289 | <h1><a class="toc-backref" href="#id23">Reference Implementation</a></h1> |
| 291 | <p>A patch for a prototype implementation of Manifest2 verification and partial |
290 | <p>A patch for a prototype implementation of Manifest2 verification and partial |
| 292 | generation has been posted at <a class="footnote-reference" href="#manifest2-patch" id="id6" name="id6">[4]</a>, it will be reworked before |
291 | generation has been posted at <a class="footnote-reference" href="#manifest2-patch" id="id6">[4]</a>, it will be reworked before |
| 293 | being considered for inclusion in portage. However it shows that adding support |
292 | being considered for inclusion in portage. However it shows that adding support |
| 294 | for verification is quite simple, but generation is a bit tricky and will |
293 | for verification is quite simple, but generation is a bit tricky and will |
| 295 | therefore be implemented later.</p> |
294 | therefore be implemented later.</p> |
| 296 | </div> |
295 | </div> |
| 297 | <div class="section"> |
296 | <div class="section" id="options"> |
| 298 | <h1><a class="toc-backref" href="#id24" id="options" name="options">Options</a></h1> |
297 | <h1><a class="toc-backref" href="#id24">Options</a></h1> |
| 299 | <p>Some things have been considered for this GLEP but aren't part of the proposal |
298 | <p>Some things have been considered for this GLEP but aren't part of the proposal |
| 300 | yet for various reasons:</p> |
299 | yet for various reasons:</p> |
| 301 | <ul class="simple"> |
300 | <ul class="simple"> |
| 302 | <li>timestamp field: the author has considered adding a timestamp field for |
301 | <li>timestamp field: the author has considered adding a timestamp field for |
| 303 | each entry to list the time the entry was created. However so far no practical |
302 | each entry to list the time the entry was created. However so far no practical |
| … | |
… | |
| 315 | or packages directly they can contain viable information for users, so |
314 | or packages directly they can contain viable information for users, so |
| 316 | the author has the opinion that at least the option for integrity checks |
315 | the author has the opinion that at least the option for integrity checks |
| 317 | should be kept.</li> |
316 | should be kept.</li> |
| 318 | </ul> |
317 | </ul> |
| 319 | </div> |
318 | </div> |
| 320 | <div class="section"> |
319 | <div class="section" id="credits"> |
| 321 | <h1><a class="toc-backref" href="#id25" id="credits" name="credits">Credits</a></h1> |
320 | <h1><a class="toc-backref" href="#id25">Credits</a></h1> |
| 322 | <p>Thanks to the following persons for their input on or related to this GLEP |
321 | <p>Thanks to the following persons for their input on or related to this GLEP |
| 323 | (even though they might not have known it): |
322 | (even though they might not have known it): |
| 324 | Ned Ludd (solar), Brian Harring (ferringb), Jason Stubbs (jstubbs), |
323 | Ned Ludd (solar), Brian Harring (ferringb), Jason Stubbs (jstubbs), |
| 325 | Robin H. Johnson (robbat2), Aron Griffis (agriffis)</p> |
324 | Robin H. Johnson (robbat2), Aron Griffis (agriffis)</p> |
| 326 | <p>Also thanks to Nicholas Jones (carpaski) to make the current Manifest system |
325 | <p>Also thanks to Nicholas Jones (carpaski) to make the current Manifest system |
| 327 | resistent enough to be able to handle this change without too many transition |
326 | resistent enough to be able to handle this change without too many transition |
| 328 | problems.</p> |
327 | problems.</p> |
| 329 | </div> |
328 | </div> |
| 330 | <div class="section"> |
329 | <div class="section" id="references"> |
| 331 | <h1><a class="toc-backref" href="#id26" id="references" name="references">References</a></h1> |
330 | <h1><a class="toc-backref" href="#id26">References</a></h1> |
| 332 | <table class="docutils footnote" frame="void" id="reorg-thread" rules="none"> |
331 | <table class="docutils footnote" frame="void" id="reorg-thread" rules="none"> |
| 333 | <colgroup><col class="label" /><col /></colgroup> |
332 | <colgroup><col class="label" /><col /></colgroup> |
| 334 | <tbody valign="top"> |
333 | <tbody valign="top"> |
| 335 | <tr><td class="label"><a class="fn-backref" href="#id1" name="reorg-thread">[1]</a></td><td><a class="reference" href="http://thread.gmane.org/gmane.linux.gentoo.devel/21920">http://thread.gmane.org/gmane.linux.gentoo.devel/21920</a></td></tr> |
334 | <tr><td class="label"><a class="fn-backref" href="#id1">[1]</a></td><td><a class="reference external" href="http://thread.gmane.org/gmane.linux.gentoo.devel/21920">http://thread.gmane.org/gmane.linux.gentoo.devel/21920</a></td></tr> |
| 336 | </tbody> |
335 | </tbody> |
| 337 | </table> |
336 | </table> |
| 338 | <table class="docutils footnote" frame="void" id="multi-hash-thread" rules="none"> |
337 | <table class="docutils footnote" frame="void" id="multi-hash-thread" rules="none"> |
| 339 | <colgroup><col class="label" /><col /></colgroup> |
338 | <colgroup><col class="label" /><col /></colgroup> |
| 340 | <tbody valign="top"> |
339 | <tbody valign="top"> |
| 341 | <tr><td class="label"><a name="multi-hash-thread">[2]</a></td><td><em>(<a class="fn-backref" href="#id3">1</a>, <a class="fn-backref" href="#id4">2</a>)</em> <a class="reference" href="http://thread.gmane.org/gmane.linux.gentoo.devel/33434">http://thread.gmane.org/gmane.linux.gentoo.devel/33434</a></td></tr> |
340 | <tr><td class="label">[2]</td><td><em>(<a class="fn-backref" href="#id3">1</a>, <a class="fn-backref" href="#id4">2</a>)</em> <a class="reference external" href="http://thread.gmane.org/gmane.linux.gentoo.devel/33434">http://thread.gmane.org/gmane.linux.gentoo.devel/33434</a></td></tr> |
| 342 | </tbody> |
341 | </tbody> |
| 343 | </table> |
342 | </table> |
| 344 | <table class="docutils footnote" frame="void" id="gpg-numbers" rules="none"> |
343 | <table class="docutils footnote" frame="void" id="gpg-numbers" rules="none"> |
| 345 | <colgroup><col class="label" /><col /></colgroup> |
344 | <colgroup><col class="label" /><col /></colgroup> |
| 346 | <tbody valign="top"> |
345 | <tbody valign="top"> |
| 347 | <tr><td class="label"><a class="fn-backref" href="#id5" name="gpg-numbers">[3]</a></td><td>gentoo-core mailing list, topic "Gentoo key signing practices |
346 | <tr><td class="label"><a class="fn-backref" href="#id5">[3]</a></td><td>gentoo-core mailing list, topic "Gentoo key signing practices |
| 348 | and official Gentoo keyring", Message-ID <<a class="reference" href="mailto:20051117075838.GB15734@curie-int.vc.shawcable.net">20051117075838.GB15734@curie-int.vc.shawcable.net</a>></td></tr> |
347 | and official Gentoo keyring", Message-ID <<a class="reference external" href="mailto:20051117075838.GB15734@curie-int.vc.shawcable.net">20051117075838.GB15734@curie-int.vc.shawcable.net</a>></td></tr> |
| 349 | </tbody> |
348 | </tbody> |
| 350 | </table> |
349 | </table> |
| 351 | <table class="docutils footnote" frame="void" id="manifest2-patch" rules="none"> |
350 | <table class="docutils footnote" frame="void" id="manifest2-patch" rules="none"> |
| 352 | <colgroup><col class="label" /><col /></colgroup> |
351 | <colgroup><col class="label" /><col /></colgroup> |
| 353 | <tbody valign="top"> |
352 | <tbody valign="top"> |
| 354 | <tr><td class="label"><a class="fn-backref" href="#id6" name="manifest2-patch">[4]</a></td><td><a class="reference" href="http://thread.gmane.org/gmane.linux.gentoo.portage.devel/1374">http://thread.gmane.org/gmane.linux.gentoo.portage.devel/1374</a></td></tr> |
353 | <tr><td class="label"><a class="fn-backref" href="#id6">[4]</a></td><td><a class="reference external" href="http://thread.gmane.org/gmane.linux.gentoo.portage.devel/1374">http://thread.gmane.org/gmane.linux.gentoo.portage.devel/1374</a></td></tr> |
| 355 | </tbody> |
354 | </tbody> |
| 356 | </table> |
355 | </table> |
| 357 | <table class="docutils footnote" frame="void" id="manifest2-example" rules="none"> |
356 | <table class="docutils footnote" frame="void" id="manifest2-example" rules="none"> |
| 358 | <colgroup><col class="label" /><col /></colgroup> |
357 | <colgroup><col class="label" /><col /></colgroup> |
| 359 | <tbody valign="top"> |
358 | <tbody valign="top"> |
| 360 | <tr><td class="label"><a name="manifest2-example">[5]</a></td><td><a class="reference" href="http://www.gentoo.org/proj/en/glep/glep-0044-extras/manifest2-example">http://www.gentoo.org/proj/en/glep/glep-0044-extras/manifest2-example</a></td></tr> |
359 | <tr><td class="label">[5]</td><td><a class="reference external" href="http://www.gentoo.org/proj/en/glep/glep-0044-extras/manifest2-example">http://www.gentoo.org/proj/en/glep/glep-0044-extras/manifest2-example</a></td></tr> |
| 361 | </tbody> |
360 | </tbody> |
| 362 | </table> |
361 | </table> |
| 363 | <table class="docutils footnote" frame="void" id="id7" rules="none"> |
362 | <table class="docutils footnote" frame="void" id="id7" rules="none"> |
| 364 | <colgroup><col class="label" /><col /></colgroup> |
363 | <colgroup><col class="label" /><col /></colgroup> |
| 365 | <tbody valign="top"> |
364 | <tbody valign="top"> |
| 366 | <tr><td class="label"><a class="fn-backref" href="#id8" name="id7">[6]</a></td><td><a class="reference" href="glep-0044-extras/manifest2-example.txt">glep-0044-extras/manifest2-example.txt</a></td></tr> |
365 | <tr><td class="label"><a class="fn-backref" href="#id8">[6]</a></td><td><a class="reference external" href="glep-0044-extras/manifest2-example.txt">glep-0044-extras/manifest2-example.txt</a></td></tr> |
| 367 | </tbody> |
366 | </tbody> |
| 368 | </table> |
367 | </table> |
| 369 | </div> |
368 | </div> |
| 370 | <div class="section"> |
369 | <div class="section" id="copyright"> |
| 371 | <h1><a class="toc-backref" href="#id27" id="copyright" name="copyright">Copyright</a></h1> |
370 | <h1><a class="toc-backref" href="#id27">Copyright</a></h1> |
| 372 | <p>This document has been placed in the public domain.</p> |
371 | <p>This document has been placed in the public domain.</p> |
| 373 | </div> |
372 | </div> |
| 374 | |
373 | |
| 375 | </div> |
374 | </div> |
| 376 | <div class="footer"> |
375 | <div class="footer"> |
| 377 | <hr class="footer" /> |
376 | <hr class="footer" /> |
| 378 | <a class="reference" href="glep-0044.txt">View document source</a>. |
377 | <a class="reference external" href="glep-0044.txt">View document source</a>. |
| 379 | Generated on: 2007-10-13 13:39 UTC. |
378 | Generated on: 2009-01-11 19:35 UTC. |
| 380 | 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. |
379 | Generated by <a class="reference external" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference external" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source. |
| 381 | |
380 | |
| 382 | </div> |
381 | </div> |
| 383 | </body> |
382 | </body> |
| 384 | </html> |
383 | </html> |
| 385 | |
|
|
Parent Directory
| 
Revision Log
| 
Patch