/[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.3 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.3 2003/11/27 11:08:27 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>
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 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>
240
231</body> 241</body>
232</subsection> 242</subsection>
233</section> 243</section>
234<section> 244<section>
235<title>Package specific USE-flags</title> 245<title>Package specific USE-flags</title>

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

  ViewVC Help
Powered by ViewVC 1.1.20