/[gentoo]/xml/htdocs/doc/en/handbook/hb-working-use.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-working-use.xml

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

Revision 1.2 Revision 1.5
1<!-- The content of this document is licensed under the CC-BY-SA license --> 1<!-- The content of this document is licensed under the CC-BY-SA license -->
2<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 2<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
3 3
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v 1.2 2003/11/25 17:34:47 swift Exp $ --> 4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v 1.5 2003/12/16 18:08:56 swift Exp $ -->
5 5
6<sections> 6<sections>
7<section> 7<section>
8<title>What are USE-flags?</title> 8<title>What are USE-flags?</title>
9<subsection> 9<subsection>
20<p> 20<p>
21This is not only true for choosing what packages you want to install, but also 21This is not only true for choosing what packages you want to install, but also
22what features a certain package should support. If you don't need OpenGL, why 22what features a certain package should support. If you don't need OpenGL, why
23would you bother installing OpenGL and build OpenGL support in most of your 23would you bother installing OpenGL and build OpenGL support in most of your
24packages? If you don't want to use KDE, why would you bother compiling packages 24packages? If you don't want to use KDE, why would you bother compiling packages
25with KDE-support if those packages work flawless without? 25with KDE-support if those packages work flawlessly without?
26</p> 26</p>
27 27
28<p> 28<p>
29To help users in deciding what to install/activate and what not, we wanted the 29To help users in deciding what to install/activate and what not, we wanted the
30user to specify his environment in an easy way. This forces the user into 30user to specify his environment in an easy way. This forces the user into
31deciding what he really wants and eases the process for Portage, our package 31deciding what he really wants and eases the process for Portage, our package
32managment system, to make usefull decisions. 32managment system, to make useful decisions.
33</p> 33</p>
34 34
35</body> 35</body>
36</subsection> 36</subsection>
37<subsection> 37<subsection>
39<body> 39<body>
40 40
41<p> 41<p>
42Enter the USE-flags. Such a flag is a keyword that embodies support and 42Enter the USE-flags. Such a flag is a keyword that embodies support and
43dependency-information for a certain concept. If you define a certain USE-flag, 43dependency-information for a certain concept. If you define a certain USE-flag,
44Portage will know that you want support for the chosen keyword. Ofcourse 44Portage will know that you want support for the chosen keyword. Of course
45this also alters the dependency information for a package. 45this also alters the dependency information for a package.
46</p> 46</p>
47 47
48<p> 48<p>
49Lets take a look at a specific example: the <c>kde</c> keyword. If you do not 49Lets take a look at a specific example: the <c>kde</c> keyword. If you do not
204<subsection> 204<subsection>
205<title>Precendence</title> 205<title>Precendence</title>
206<body> 206<body>
207 207
208<p> 208<p>
209Ofcourse there is a certain precendence on what setting has priority over the 209Of course there is a certain precendence on what setting has priority over the
210USE setting. You don't want to declare <c>USE="-java"</c> only to see that 210USE setting. You don't want to declare <c>USE="-java"</c> only to see that
211<c>java</c> is declared anyway. The precedence for the USE setting is, ordered 211<c>java</c> is declared anyway. The precedence for the USE setting is, ordered
212by priority (first has lowest priority): 212by priority (first has lowest priority):
213</p> 213</p>
214 214
225 </li> 225 </li>
226 <li> 226 <li>
227 User-defined USE setting as environment variable 227 User-defined USE setting as environment variable
228 </li> 228 </li>
229</ol> 229</ol>
230
231<p>
232To view the final <c>USE</c> setting as seen by Portage, run <c>emerge info</c>.
233This will list all relevant variables (including the <c>USE</c> variable) with
234the content used by Portage.
235</p>
236
237<pre caption="Running emerge info">
238# <i>emerge info</i>
239</pre>
230 240
231</body> 241</body>
232</subsection> 242</subsection>
233</section> 243</section>
234<section> 244<section>

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.5

  ViewVC Help
Powered by ViewVC 1.1.20