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

Diff of /xml/htdocs/proj/en/glep/glep-0021.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.1 Revision 1.8
… …
6PEP, see http://www.python.org/peps/pep-0001.html for instructions and links 6PEP, see http://www.python.org/peps/pep-0001.html for instructions and links
7to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE! 7to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE!
8--> 8-->
9<head> 9<head>
10 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 10 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
11 <meta name="generator" content="Docutils 0.3.0: http://docutils.sourceforge.net/" /> 11 <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
12 <title>GLEP 21 -- User-defined Package Sets</title> 12 <title>GLEP 21 -- User-defined Package Sets</title>
13 <link rel="stylesheet" href="tools/glep.css" type="text/css" /> 13 <style type="text/css">
14
15/*
16:Author: David Goodger
17:Contact: goodger@users.sourceforge.net
18:date: $Date: 2007/10/21 11:42:57 $
19:version: $Revision: 1.8 $
20:copyright: This stylesheet has been placed in the public domain.
21
22Default cascading style sheet for the PEP HTML output of Docutils.
23*/
24
25.first {
26 margin-top: 0 }
27
28.last {
29 margin-bottom: 0 }
30
31.navigation {
32 width: 100% ;
33 background: #cc99ff ;
34 margin-top: 0px ;
35 margin-bottom: 0px }
36
37.navigation .navicon {
38 width: 150px ;
39 height: 35px }
40
41.navigation .textlinks {
42 padding-left: 1em ;
43 text-align: left }
44
45.navigation td, .navigation th {
46 padding-left: 0em ;
47 padding-right: 0em ;
48 vertical-align: middle }
49
50.rfc2822 {
51 margin-top: 0.5em ;
52 margin-left: 0.5em ;
53 margin-right: 0.5em ;
54 margin-bottom: 0em }
55
56.rfc2822 td {
57 text-align: left }
58
59.rfc2822 th.field-name {
60 text-align: right ;
61 font-family: sans-serif ;
62 padding-right: 0.5em ;
63 font-weight: bold ;
64 margin-bottom: 0em }
65
66a.toc-backref {
67 text-decoration: none ;
68 color: black }
69
70body {
71 margin: 0px ;
72 margin-bottom: 1em ;
73 padding: 0px }
74
75dd {
76 margin-bottom: 0.5em }
77
78div.section {
79 margin-left: 1em ;
80 margin-right: 1em ;
81 margin-bottom: 1.5em }
82
83div.section div.section {
84 margin-left: 0em ;
85 margin-right: 0em ;
86 margin-top: 1.5em }
87
88div.abstract {
89 margin: 2em 5em }
90
91div.abstract p.topic-title {
92 font-weight: bold ;
93 text-align: center }
94
95div.attention, div.caution, div.danger, div.error, div.hint,
96div.important, div.note, div.tip, div.warning {
97 margin: 2em ;
98 border: medium outset ;
99 padding: 1em }
100
101div.attention p.admonition-title, div.caution p.admonition-title,
102div.danger p.admonition-title, div.error p.admonition-title,
103div.warning p.admonition-title {
104 color: red ;
105 font-weight: bold ;
106 font-family: sans-serif }
107
108div.hint p.admonition-title, div.important p.admonition-title,
109div.note p.admonition-title, div.tip p.admonition-title {
110 font-weight: bold ;
111 font-family: sans-serif }
112
113div.figure {
114 margin-left: 2em }
115
116div.footer, div.header {
117 font-size: smaller }
118
119div.footer {
120 margin-left: 1em ;
121 margin-right: 1em }
122
123div.system-messages {
124 margin: 5em }
125
126div.system-messages h1 {
127 color: red }
128
129div.system-message {
130 border: medium outset ;
131 padding: 1em }
132
133div.system-message p.system-message-title {
134 color: red ;
135 font-weight: bold }
136
137div.topic {
138 margin: 2em }
139
140h1 {
141 font-family: sans-serif ;
142 font-size: large }
143
144h2 {
145 font-family: sans-serif ;
146 font-size: medium }
147
148h3 {
149 font-family: sans-serif ;
150 font-size: small }
151
152h4 {
153 font-family: sans-serif ;
154 font-style: italic ;
155 font-size: small }
156
157h5 {
158 font-family: sans-serif;
159 font-size: x-small }
160
161h6 {
162 font-family: sans-serif;
163 font-style: italic ;
164 font-size: x-small }
165
166.section hr {
167 width: 75% }
168
169ol.simple, ul.simple {
170 margin-bottom: 1em }
171
172ol.arabic {
173 list-style: decimal }
174
175ol.loweralpha {
176 list-style: lower-alpha }
177
178ol.upperalpha {
179 list-style: upper-alpha }
180
181ol.lowerroman {
182 list-style: lower-roman }
183
184ol.upperroman {
185 list-style: upper-roman }
186
187p.caption {
188 font-style: italic }
189
190p.credits {
191 font-style: italic ;
192 font-size: smaller }
193
194p.label {
195 white-space: nowrap }
196
197p.topic-title {
198 font-family: sans-serif ;
199 font-weight: bold }
200
201pre.line-block {
202 font-family: serif ;
203 font-size: 100% }
204
205pre.literal-block, pre.doctest-block {
206 margin-left: 2em ;
207 margin-right: 2em ;
208 background-color: #eeeeee }
209
210span.classifier {
211 font-family: sans-serif ;
212 font-style: oblique }
213
214span.classifier-delimiter {
215 font-family: sans-serif ;
216 font-weight: bold }
217
218span.interpreted {
219 font-family: sans-serif }
220
221span.option-argument {
222 font-style: italic }
223
224span.pre {
225 white-space: pre }
226
227span.problematic {
228 color: red }
229
230table {
231 margin-top: 0.5em ;
232 margin-bottom: 0.5em }
233
234td, th {
235 padding-left: 0.5em ;
236 padding-right: 0.5em ;
237 vertical-align: top }
238
239td.num {
240 text-align: right }
241
242th.field-name {
243 font-weight: bold ;
244 text-align: left ;
245 white-space: nowrap }
246
247h1 tt, h2 tt, h3 tt, h4 tt, h5 tt, h6 tt {
248 font-size: 100% }
249
250tt {
251 background-color: #eeeeee }
252
253ul.auto-toc {
254 list-style-type: none }
255
256</style>
14</head> 257</head>
15<body bgcolor="white"> 258<body bgcolor="white">
16<table class="navigation" cellpadding="0" cellspacing="0" 259<table class="navigation" cellpadding="0" cellspacing="0"
17 width="100%" border="0"> 260 width="100%" border="0">
18<tr><td class="navicon" width="150" height="35"> 261<tr><td class="navicon" width="150" height="35">
19<a href="http://www.gentoo.org/" title="Gentoo Linux Home Page"> 262<a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
20<img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]" 263<img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
21 border="0" width="150" height="35" /></a></td> 264 border="0" width="150" height="35" /></a></td>
22<td class="textlinks" align="left"> 265<td class="textlinks" align="left">
23[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>] 266[<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
24[<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>] 267[<b><a href="http://www.gentoo.org/peps">GLEP Index</a></b>]
25[<b><a href="http://www.gentoo.org/proj/en/glep/glep-0021.txt">GLEP Source</a></b>] 268[<b><a href="http://www.gentoo.org/proj/en/glep/glep-0021.txt">GLEP Source</a></b>]
26</td></tr></table> 269</td></tr></table>
27<div class="document">
28<table class="rfc2822 field-list" frame="void" rules="none"> 270<table class="rfc2822 docutils field-list" frame="void" rules="none">
29<col class="field-name" /> 271<col class="field-name" />
30<col class="field-body" /> 272<col class="field-body" />
31<tbody valign="top"> 273<tbody valign="top">
32<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">21</td> 274<tr class="field"><th class="field-name">GLEP:</th><td class="field-body">21</td>
33</tr> 275</tr>
34<tr class="field"><th class="field-name">Title:</th><td class="field-body">User-defined Package Sets</td> 276<tr class="field"><th class="field-name">Title:</th><td class="field-body">User-defined Package Sets</td>
35</tr> 277</tr>
36<tr class="field"><th class="field-name">Version:</th><td class="field-body">1.1</td> 278<tr class="field"><th class="field-name">Version:</th><td class="field-body">1.4</td>
37</tr> 279</tr>
38<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-0021.txt?cvsroot=gentoo">2004/03/06 23:19:05</a></td> 280<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-0021.txt?cvsroot=gentoo">2007/04/21 03:13:16</a></td>
39</tr> 281</tr>
40<tr class="field"><th class="field-name">Author:</th><td class="field-body">Tal Peer &lt;coredumb&#32;&#97;t&#32;gentoo.org&gt;</td> 282<tr class="field"><th class="field-name">Author:</th><td class="field-body">Tal Peer &lt;coredumb&#32;&#97;t&#32;gentoo.org&gt;,
283Alec Warner &lt;antarus&#32;&#97;t&#32;gentoo.org&gt;</td>
41</tr> 284</tr>
42<tr class="field"><th class="field-name">Status:</th><td class="field-body">Draft</td> 285<tr class="field"><th class="field-name">Status:</th><td class="field-body">Deferred</td>
43</tr> 286</tr>
44<tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> 287<tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
45</tr> 288</tr>
46<tr class="field"><th class="field-name">Discussed-To:</th><td class="field-body"><a class="reference" href="mailto:gentoo-portage-dev&#64;lists.gentoo.org">gentoo-portage-dev&#64;lists.gentoo.org</a></td> 289<tr class="field"><th class="field-name">Discussed-To:</th><td class="field-body"><a class="reference" href="mailto:gentoo-portage-dev&#64;lists.gentoo.org">gentoo-portage-dev&#64;lists.gentoo.org</a></td>
47</tr> 290</tr>
48<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> 291<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>
49</tr> 292</tr>
50<tr class="field"><th class="field-name">Created:</th><td class="field-body">22-Feb-2004</td> 293<tr class="field"><th class="field-name">Created:</th><td class="field-body">22-Feb-2004</td>
51</tr> 294</tr>
52<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">6-Mar-2004</td> 295<tr class="field"><th class="field-name">Post-History:</th><td class="field-body">6-Mar-2004, 3-Sep-2006</td>
53</tr> 296</tr>
54</tbody> 297</tbody>
55</table> 298</table>
56<hr /> 299<hr />
57<div class="contents topic" id="contents"> 300<div class="contents topic">
58<p class="topic-title"><a name="contents">Contents</a></p> 301<p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
59<ul class="simple"> 302<ul class="simple">
303<li><a class="reference" href="#status" id="id3" name="id3">Status</a></li>
60<li><a class="reference" href="#abstract" id="id3" name="id3">Abstract</a></li> 304<li><a class="reference" href="#abstract" id="id4" name="id4">Abstract</a></li>
61<li><a class="reference" href="#motivation" id="id4" name="id4">Motivation</a></li> 305<li><a class="reference" href="#motivation" id="id5" name="id5">Motivation</a></li>
62<li><a class="reference" href="#specification" id="id5" name="id5">Specification</a><ul> 306<li><a class="reference" href="#specification" id="id6" name="id6">Specification</a><ul>
63<li><a class="reference" href="#using-user-defined-sets-with-emerge" id="id6" name="id6">Using User-defined Sets With Emerge</a></li> 307<li><a class="reference" href="#using-user-defined-sets-with-emerge" id="id7" name="id7">Using User-defined Sets With Emerge</a></li>
64<li><a class="reference" href="#compatibility-with-other-portage-features" id="id7" name="id7">Compatibility With Other Portage Features</a></li> 308<li><a class="reference" href="#compatibility-with-other-portage-features" id="id8" name="id8">Compatibility With Other Portage Features</a></li>
65</ul> 309</ul>
66</li> 310</li>
67<li><a class="reference" href="#implementation" id="id8" name="id8">Implementation</a></li> 311<li><a class="reference" href="#implementation" id="id9" name="id9">Implementation</a></li>
68<li><a class="reference" href="#rationale" id="id9" name="id9">Rationale</a></li> 312<li><a class="reference" href="#rationale" id="id10" name="id10">Rationale</a></li>
69<li><a class="reference" href="#backwards-compatibility" id="id10" name="id10">Backwards Compatibility</a></li> 313<li><a class="reference" href="#backwards-compatibility" id="id11" name="id11">Backwards Compatibility</a></li>
70<li><a class="reference" href="#references" id="id11" name="id11">References</a></li> 314<li><a class="reference" href="#references" id="id12" name="id12">References</a></li>
71<li><a class="reference" href="#copyright" id="id12" name="id12">Copyright</a></li> 315<li><a class="reference" href="#copyright" id="id13" name="id13">Copyright</a></li>
72</ul> 316</ul>
73</div> 317</div>
74<div class="section" id="abstract"> 318<div class="section">
319<h1><a class="toc-backref" href="#id3" id="status" name="status">Status</a></h1>
320<p>Abandoned. Package set support has been added in portage-2.2, but it
321doesn't match the description in this document in many cases, and the
322document has several major gaps regarding the behavior and restrictions
323of package sets.</p>
324</div>
325<div class="section">
75<h1><a class="toc-backref" href="#id3" name="abstract">Abstract</a></h1> 326<h1><a class="toc-backref" href="#id4" id="abstract" name="abstract">Abstract</a></h1>
76<p>In Portage, package sets (formerly known as 'classes' or 'targets') 327<p>In Portage, package sets (formerly known as 'classes' or 'targets')
77are mere groups of packages, grouped together to allow easier updating 328are mere groups of packages, grouped together to allow easier updating
78and handling of them. Currently it is impossible to define sets further 329and handling of them. Currently it is impossible to define sets further
79than the two default ones: &quot;system&quot; and &quot;world&quot;.</p> 330than the two default ones: &quot;system&quot; and &quot;world&quot;.</p>
80</div> 331</div>
81<div class="section" id="motivation"> 332<div class="section">
82<h1><a class="toc-backref" href="#id4" name="motivation">Motivation</a></h1> 333<h1><a class="toc-backref" href="#id5" id="motivation" name="motivation">Motivation</a></h1>
83<p>Over the months, quite a few requests for user-defined sets were 334<p>Over the months, quite a few requests for user-defined sets were
84made by users and developers, either by posting bugs, messages to 335made by users and developers, either by posting bugs, messages to
85mailing lists or on IRC. Usually the response is that this is an 336mailing lists or on IRC. Usually the response is that this is an
86awesome idea, but no one ever took the time to actually define it 337awesome idea, but no one ever took the time to actually define it
87properly and implement it.</p> 338properly and implement it.</p>
88<p>This document offers a specification for the implementation of 339<p>This document offers a specification for the implementation of
89user-defined sets using configuration files similar to the current 340user-defined sets using configuration files similar to the current
90world/system sets use.</p> 341world/system sets use.</p>
91</div> 342</div>
92<div class="section" id="specification"> 343<div class="section">
93<h1><a class="toc-backref" href="#id5" name="specification">Specification</a></h1> 344<h1><a class="toc-backref" href="#id6" id="specification" name="specification">Specification</a></h1>
94<p>The proposed implementation uses a one file per set approach, meaning 345<p>The proposed implementation uses a one file per set approach, meaning
95each package set is defined in a single file. All set definition files 346each package set is defined in a single file. All set definition files
96will reside in a directory <tt class="literal"><span class="pre">/etc/portage/sets/</span></tt> and each set's name 347will reside in a directory <tt class="docutils literal"><span class="pre">/etc/portage/sets/</span></tt> and each set's name
97will be its file name. Therefore, if one defines a set in 348will be its file name. Therefore, if one defines a set in
98/etc/portage/sets/foo-set, the set name will be 'foo-set'. Usual 349/etc/portage/sets/foo-set, the set name will be 'foo-set'. Usual
99package naming rules <a class="footnote-reference" href="#name-rules" id="id1" name="id1">[1]</a> also apply to sets.</p> 350package naming rules <a class="footnote-reference" href="#name-rules" id="id1" name="id1">[1]</a> also apply to sets.</p>
100<p>As it is impossible to create two or more files with identical names 351<p>As it is impossible to create two or more files with identical names
101in the same directory, a theoretic conflict between two different sets 352in the same directory, a theoretic conflict between two different sets
… …
105<p>Syntax for the package list file is the same as the world file syntax, 356<p>Syntax for the package list file is the same as the world file syntax,
106as described in the Portage manpage <a class="footnote-reference" href="#portage-manpage" id="id2" name="id2">[2]</a>, with one 357as described in the Portage manpage <a class="footnote-reference" href="#portage-manpage" id="id2" name="id2">[2]</a>, with one
107addition: sets may not be 'inherited' by other sets, only packages may 358addition: sets may not be 'inherited' by other sets, only packages may
108be listed. There is no limitation to the number of packages in a set 359be listed. There is no limitation to the number of packages in a set
109or to the number of sets a package may belong to.</p> 360or to the number of sets a package may belong to.</p>
110<div class="section" id="using-user-defined-sets-with-emerge"> 361<div class="section">
111<h2><a class="toc-backref" href="#id6" name="using-user-defined-sets-with-emerge">Using User-defined Sets With Emerge</a></h2> 362<h2><a class="toc-backref" href="#id7" id="using-user-defined-sets-with-emerge" name="using-user-defined-sets-with-emerge">Using User-defined Sets With Emerge</a></h2>
112<p>The user-defined sets will be available either directly or using 363<p>The user-defined sets will be available either directly or using
113the --package-set option, As in:</p> 364the --package-set option, As in:</p>
114<pre class="literal-block"> 365<pre class="literal-block">
115# Basically the same: 366# Basically the same:
116emerge foo-set 367emerge foo-set
… …
132<p>When running emerge with the --pretend option, sets will be 383<p>When running emerge with the --pretend option, sets will be
133expanded to the packages they are comprised off in the output, as with 384expanded to the packages they are comprised off in the output, as with
134the current system-defined sets.</p> 385the current system-defined sets.</p>
135<p>Only one set may be passed to portage at time, and sets can not 386<p>Only one set may be passed to portage at time, and sets can not
136be mixed with ordinary packages. Thus, the following snippets are 387be mixed with ordinary packages. Thus, the following snippets are
137all invalid and will result in an error (assuming <tt class="literal"><span class="pre">foo-set</span></tt> and 388all invalid and will result in an error (assuming <tt class="docutils literal"><span class="pre">foo-set</span></tt> and
138<tt class="literal"><span class="pre">bar-set</span></tt> are defined as sets):</p> 389<tt class="docutils literal"><span class="pre">bar-set</span></tt> are defined as sets):</p>
139<pre class="literal-block"> 390<pre class="literal-block">
140emerge foo-set glibc 391emerge foo-set glibc
141emerge bar-set system 392emerge bar-set system
142emerge world foo-set gcc 393emerge world foo-set gcc
143</pre> 394</pre>
144</div> 395</div>
145<div class="section" id="compatibility-with-other-portage-features"> 396<div class="section">
146<h2><a class="toc-backref" href="#id7" name="compatibility-with-other-portage-features">Compatibility With Other Portage Features</a></h2> 397<h2><a class="toc-backref" href="#id8" id="compatibility-with-other-portage-features" name="compatibility-with-other-portage-features">Compatibility With Other Portage Features</a></h2>
147<ul class="simple"> 398<ul class="simple">
148<li>Dependencies: 399<li>Dependencies:
149Package sets (both system-defined and user-defined) may not be 400Package sets (both system-defined and user-defined) may not be
150depended on by ordinary packages and eclasses.</li> 401depended on by ordinary packages and eclasses.</li>
151<li>package.mask: 402<li>package.mask:
152Masking a package set through the <tt class="literal"><span class="pre">package.mask</span></tt> file is forbidden. 403Masking a package set through the <tt class="docutils literal"><span class="pre">package.mask</span></tt> file is forbidden.
153In order to 'mask' a package set, one should comment it in the 404In order to 'mask' a package set, one should move it away from the
154<tt class="literal"><span class="pre">package.sets</span></tt> file (see above).</li> 405sets directory.</li>
155<li>package.use: 406<li>package.use:
156USE flags may not be defined for sets in the <tt class="literal"><span class="pre">package.use</span></tt> file.</li> 407USE flags may not be defined for sets in the <tt class="docutils literal"><span class="pre">package.use</span></tt> file.</li>
157</ul> 408</ul>
158</div> 409</div>
159</div> 410</div>
160<div class="section" id="implementation"> 411<div class="section">
161<h1><a class="toc-backref" href="#id8" name="implementation">Implementation</a></h1> 412<h1><a class="toc-backref" href="#id9" id="implementation" name="implementation">Implementation</a></h1>
162<p>The implementation of the package sets concept in Portage should be 413<p>The implementation of the package sets concept in Portage should be
163mostly done in portage.py, and only the interface parts should be 414mostly done in portage.py, and only the interface parts should be
164added to emerge itself, to keep the separation between interface and 415added to emerge itself, to keep the separation between interface and
165logic.</p> 416logic.</p>
166<p>The amount of work needed for implementation is not trivial, but not 417<p>The amount of work needed for implementation is not trivial, but not
167huge either.</p> 418huge either.</p>
168</div> 419</div>
169<div class="section" id="rationale"> 420<div class="section">
170<h1><a class="toc-backref" href="#id9" name="rationale">Rationale</a></h1> 421<h1><a class="toc-backref" href="#id10" id="rationale" name="rationale">Rationale</a></h1>
171<p>The one file per set approach makes it easy to list the sets which are 422<p>The one file per set approach makes it easy to list the sets which are
172defined on a system by just listing the <tt class="literal"><span class="pre">/etc/portage/sets</span></tt> 423defined on a system by just listing the <tt class="docutils literal"><span class="pre">/etc/portage/sets</span></tt>
173directory contents. Additionally, it makes the set lookup process more 424directory contents. Additionally, it makes the set lookup process more
174efficient as it only requires to check if a file exists.</p> 425efficient as it only requires to check if a file exists.</p>
175<p>I chose the --package-set option over the --set option for explicitly 426<p>I chose the --package-set option over the --set option for explicitly
176telling portage to emerge a set mostly because --set implies setting 427telling portage to emerge a set mostly because --set implies setting
177an environment variable, or such.</p> 428an environment variable, or such.</p>
178<p>Allowing sets' USE flags to be manipulated through the <tt class="literal"><span class="pre">package.use</span></tt> 429<p>Allowing sets' USE flags to be manipulated through the <tt class="docutils literal"><span class="pre">package.use</span></tt>
179file would have done more harm than good, for several reasons:</p> 430file would have done more harm than good, for several reasons:</p>
180<ul class="simple"> 431<ul class="simple">
181<li>If a USE flag is turned on (i.e. 'foo') for a set and the same USE 432<li>If a USE flag is turned on (i.e. 'foo') for a set and the same USE
182flag is turned off (i.e. '-foo'), for a package which is part of 433flag is turned off (i.e. '-foo'), for a package which is part of
183the set, it is unclear which setting should take precedence.</li> 434the set, it is unclear which setting should take precedence.</li>
… …
189USE flag should be defined when emerging the package in question.</li> 440USE flag should be defined when emerging the package in question.</li>
190</ul> 441</ul>
191<p>Therefore, I have decided it would be better to disallow setting USE 442<p>Therefore, I have decided it would be better to disallow setting USE
192flags for sets.</p> 443flags for sets.</p>
193</div> 444</div>
194<div class="section" id="backwards-compatibility"> 445<div class="section">
195<h1><a class="toc-backref" href="#id10" name="backwards-compatibility">Backwards Compatibility</a></h1> 446<h1><a class="toc-backref" href="#id11" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1>
196<p>Backwards compatibility with the current situation, in which only two 447<p>Backwards compatibility with the current situation, in which only two
197system-defined sets exist can be kept in one of two ways:</p> 448system-defined sets exist can be kept in one of two ways:</p>
198<ol class="arabic simple"> 449<ol class="arabic simple">
199<li>Leaving the situation as is - the 'world' and 'system' sets are 450<li>Leaving the situation as is - the 'world' and 'system' sets are
200hard-coded in Portage.</li> 451hard-coded in Portage.</li>
201<li>Distributing default 'system' and 'world' files under the 452<li>Distributing default 'system' and 'world' files under the
202<tt class="literal"><span class="pre">/etc/portage/sets/</span></tt> directory.</li> 453<tt class="docutils literal"><span class="pre">/etc/portage/sets/</span></tt> directory.</li>
203</ol> 454</ol>
204<p>Other than that, there are no other backwards compatibility concerns 455<p>Other than that, there are no other backwards compatibility concerns
205involved.</p> 456involved.</p>
206</div> 457</div>
207<div class="section" id="references"> 458<div class="section">
208<h1><a class="toc-backref" href="#id11" name="references">References</a></h1> 459<h1><a class="toc-backref" href="#id12" id="references" name="references">References</a></h1>
209<table class="footnote" frame="void" id="name-rules" rules="none"> 460<table class="docutils footnote" frame="void" id="name-rules" rules="none">
210<colgroup><col class="label" /><col /></colgroup> 461<colgroup><col class="label" /><col /></colgroup>
211<tbody valign="top"> 462<tbody valign="top">
212<tr><td class="label"><a class="fn-backref" href="#id1" name="name-rules">[1]</a></td><td>Gentoo Linux Development Policy - Ebuild Policy 463<tr><td class="label"><a class="fn-backref" href="#id1" name="name-rules">[1]</a></td><td>Gentoo Linux Development Policy - Ebuild Policy
213(<a class="reference" href="http://www.gentoo.org/doc/en/policy.xml#doc_chap3">http://www.gentoo.org/doc/en/policy.xml#doc_chap3</a>)</td></tr> 464(<a class="reference" href="http://www.gentoo.org/doc/en/policy.xml#doc_chap3">http://www.gentoo.org/doc/en/policy.xml#doc_chap3</a>)</td></tr>
214</tbody> 465</tbody>
215</table> 466</table>
216<table class="footnote" frame="void" id="portage-manpage" rules="none"> 467<table class="docutils footnote" frame="void" id="portage-manpage" rules="none">
217<colgroup><col class="label" /><col /></colgroup> 468<colgroup><col class="label" /><col /></colgroup>
218<tbody valign="top"> 469<tbody valign="top">
219<tr><td class="label"><a class="fn-backref" href="#id2" name="portage-manpage">[2]</a></td><td><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage/man/portage.5?root=gentoo-src">http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage/man/portage.5?root=gentoo-src</a></td></tr> 470<tr><td class="label"><a class="fn-backref" href="#id2" name="portage-manpage">[2]</a></td><td><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage/man/portage.5?root=gentoo-src">http://www.gentoo.org/cgi-bin/viewcvs.cgi/portage/man/portage.5?root=gentoo-src</a></td></tr>
220</tbody> 471</tbody>
221</table> 472</table>
222</div> 473</div>
223<div class="section" id="copyright"> 474<div class="section">
224<h1><a class="toc-backref" href="#id12" name="copyright">Copyright</a></h1> 475<h1><a class="toc-backref" href="#id13" id="copyright" name="copyright">Copyright</a></h1>
225<p>This document has been placed in the public domain.</p> 476<p>This document has been placed in the public domain.</p>
226</div> 477</div>
227</div>
228 478
229<hr class="footer"/> 479</div>
230<div class="footer"> 480<div class="footer">
481<hr class="footer" />
231<a class="reference" href="glep-0021.txt">View document source</a>. 482<a class="reference" href="glep-0021.txt">View document source</a>.
232Generated on: 2004-03-06 23:19 UTC. 483Generated on: 2007-10-21 11:40 UTC.
233Generated 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. 484Generated 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.
485
234</div> 486</div>
235</body> 487</body>
236</html> 488</html>
237 489
Legend:
Removed from v.1.1  
changed lines
  Added in v.1.8
  ViewVC Help
Powered by ViewVC 1.1.13