| 1 |
nightmorph 07/04/14 03:09:30 |
| 2 |
|
| 3 |
Modified: hb-working-use.xml |
| 4 |
Log: |
| 5 |
massive english fixes. it's 'USE flag', not 'USE-flag'. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.46 xml/htdocs/doc/en/handbook/hb-working-use.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml?rev=1.46&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml?rev=1.46&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml?r1=1.45&r2=1.46 |
| 13 |
|
| 14 |
Index: hb-working-use.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v |
| 17 |
retrieving revision 1.45 |
| 18 |
retrieving revision 1.46 |
| 19 |
diff -u -r1.45 -r1.46 |
| 20 |
--- hb-working-use.xml 20 Feb 2007 22:07:04 -0000 1.45 |
| 21 |
+++ hb-working-use.xml 14 Apr 2007 03:09:30 -0000 1.46 |
| 22 |
@@ -4,22 +4,22 @@ |
| 23 |
<!-- The content of this document is licensed under the CC-BY-SA license --> |
| 24 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 25 |
|
| 26 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v 1.45 2007/02/20 22:07:04 nightmorph Exp $ --> |
| 27 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v 1.46 2007/04/14 03:09:30 nightmorph Exp $ --> |
| 28 |
|
| 29 |
<sections> |
| 30 |
|
| 31 |
<abstract> |
| 32 |
-USE-flags are a very important aspect of Gentoo. In this chapter, you learn to |
| 33 |
-work with USE-flags and understand how USE-flags interact with your system. |
| 34 |
+USE flags are a very important aspect of Gentoo. In this chapter, you learn to |
| 35 |
+work with USE flags and understand how USE flags interact with your system. |
| 36 |
</abstract> |
| 37 |
|
| 38 |
<version>1.36</version> |
| 39 |
<date>2007-02-20</date> |
| 40 |
|
| 41 |
<section> |
| 42 |
-<title>What are USE-flags?</title> |
| 43 |
+<title>What are USE flags?</title> |
| 44 |
<subsection> |
| 45 |
-<title>The ideas behind USE-flags</title> |
| 46 |
+<title>The ideas behind USE flags</title> |
| 47 |
<body> |
| 48 |
|
| 49 |
<p> |
| 50 |
@@ -34,7 +34,7 @@ |
| 51 |
what features a certain package should support. If you don't need OpenGL, why |
| 52 |
would you bother installing OpenGL and build OpenGL support in most of your |
| 53 |
packages? If you don't want to use KDE, why would you bother compiling packages |
| 54 |
-with KDE-support if those packages work flawlessly without? |
| 55 |
+with KDE support if those packages work flawlessly without? |
| 56 |
</p> |
| 57 |
|
| 58 |
<p> |
| 59 |
@@ -47,12 +47,12 @@ |
| 60 |
</body> |
| 61 |
</subsection> |
| 62 |
<subsection> |
| 63 |
-<title>Definition of a USE-flag</title> |
| 64 |
+<title>Definition of a USE flag</title> |
| 65 |
<body> |
| 66 |
|
| 67 |
<p> |
| 68 |
-Enter the USE-flags. Such a flag is a keyword that embodies support and |
| 69 |
-dependency-information for a certain concept. If you define a certain USE-flag, |
| 70 |
+Enter the USE flags. Such a flag is a keyword that embodies support and |
| 71 |
+dependency-information for a certain concept. If you define a certain USE flag, |
| 72 |
Portage will know that you want support for the chosen keyword. Of course |
| 73 |
this also alters the dependency information for a package. |
| 74 |
</p> |
| 75 |
@@ -75,32 +75,32 @@ |
| 76 |
</body> |
| 77 |
</subsection> |
| 78 |
<subsection> |
| 79 |
-<title>What USE-flags exist?</title> |
| 80 |
+<title>What USE flags exist?</title> |
| 81 |
<body> |
| 82 |
|
| 83 |
<p> |
| 84 |
-There are two types of USE-flags: <e>global</e> and <e>local</e> USE-flags. |
| 85 |
+There are two types of USE flags: <e>global</e> and <e>local</e> USE flags. |
| 86 |
</p> |
| 87 |
|
| 88 |
<ul> |
| 89 |
<li> |
| 90 |
- A <e>global</e> USE-flag is used by several packages, system-wide. This is |
| 91 |
- what most people see as USE-flags. |
| 92 |
+ A <e>global</e> USE flag is used by several packages, system-wide. This is |
| 93 |
+ what most people see as USE flags. |
| 94 |
</li> |
| 95 |
<li> |
| 96 |
- A <e>local</e> USE-flag is used by a single package to make package-specific |
| 97 |
+ A <e>local</e> USE flag is used by a single package to make package-specific |
| 98 |
decisions. |
| 99 |
</li> |
| 100 |
</ul> |
| 101 |
|
| 102 |
<p> |
| 103 |
-A list of available global USE-flags can be found <uri |
| 104 |
+A list of available global USE flags can be found <uri |
| 105 |
link="/dyn/use-index.xml">online</uri> or locally in |
| 106 |
<path>/usr/portage/profiles/use.desc</path>. |
| 107 |
</p> |
| 108 |
|
| 109 |
<p> |
| 110 |
-A list of available local USE-flags can be found locally in |
| 111 |
+A list of available local USE flags can be found locally in |
| 112 |
<path>/usr/portage/profiles/use.local.desc</path>. |
| 113 |
</p> |
| 114 |
|
| 115 |
@@ -108,20 +108,20 @@ |
| 116 |
</subsection> |
| 117 |
</section> |
| 118 |
<section> |
| 119 |
-<title>Using USE-flags</title> |
| 120 |
+<title>Using USE flags</title> |
| 121 |
<subsection> |
| 122 |
-<title>Declare permanent USE-flags</title> |
| 123 |
+<title>Declare permanent USE flags</title> |
| 124 |
<body> |
| 125 |
|
| 126 |
<p> |
| 127 |
-In the hope you are convinced of the importance of USE-flags we will now inform |
| 128 |
-you how to declare USE-flags. |
| 129 |
+In the hope you are convinced of the importance of USE flags we will now inform |
| 130 |
+you how to declare USE flags. |
| 131 |
</p> |
| 132 |
|
| 133 |
<p> |
| 134 |
-As previously mentioned, all USE-flags are declared inside the <c>USE</c> |
| 135 |
-variable. To make it easy for users to search and pick USE-flags, we already |
| 136 |
-provide a <e>default</e> USE setting. This setting is a collection of USE-flags |
| 137 |
+As previously mentioned, all USE flags are declared inside the <c>USE</c> |
| 138 |
+variable. To make it easy for users to search and pick USE flags, we already |
| 139 |
+provide a <e>default</e> USE setting. This setting is a collection of USE flags |
| 140 |
we think are commonly used by the Gentoo users. This default setting is declared |
| 141 |
in the <path>make.defaults</path> files part of your profile. |
| 142 |
</p> |
| 143 |
@@ -157,8 +157,8 @@ |
| 144 |
<p> |
| 145 |
To change this default setting, you need to add or remove keywords to the |
| 146 |
<c>USE</c> variable. This is done globally by defining the <c>USE</c> variable |
| 147 |
-in <path>/etc/make.conf</path>. In this variable you add the extra USE-flags you |
| 148 |
-require, or remove the USE-flags you don't want. This latter is done by |
| 149 |
+in <path>/etc/make.conf</path>. In this variable you add the extra USE flags you |
| 150 |
+require, or remove the USE flags you don't want. This latter is done by |
| 151 |
prefixing the keyword with the minus-sign ("-"). |
| 152 |
</p> |
| 153 |
|
| 154 |
@@ -205,19 +205,19 @@ |
| 155 |
</body> |
| 156 |
</subsection> |
| 157 |
<subsection> |
| 158 |
-<title>Declare temporary USE-flags</title> |
| 159 |
+<title>Declare temporary USE flags</title> |
| 160 |
<body> |
| 161 |
|
| 162 |
<p> |
| 163 |
-Sometimes you want to set a certain USE-setting only once. Instead of editing |
| 164 |
-<path>/etc/make.conf</path> twice (to do and undo the USE-changes) you can just |
| 165 |
-declare the USE-variable as environment variable. Remember that, when you |
| 166 |
+Sometimes you want to set a certain USE setting only once. Instead of editing |
| 167 |
+<path>/etc/make.conf</path> twice (to do and undo the USE changes) you can just |
| 168 |
+declare the USE variable as environment variable. Remember that, when you |
| 169 |
re-emerge or update this application (either explicitly or as part of a system |
| 170 |
update) your changes will be lost! |
| 171 |
</p> |
| 172 |
|
| 173 |
<p> |
| 174 |
-As an example we will temporarily remove java from the USE-setting |
| 175 |
+As an example we will temporarily remove java from the USE setting |
| 176 |
during the installation of seamonkey. |
| 177 |
</p> |
| 178 |
|
| 179 |
@@ -316,18 +316,18 @@ |
| 180 |
</subsection> |
| 181 |
</section> |
| 182 |
<section> |
| 183 |
-<title>Package specific USE-flags</title> |
| 184 |
+<title>Package specific USE flags</title> |
| 185 |
<subsection> |
| 186 |
-<title>Viewing available USE-flags</title> |
| 187 |
+<title>Viewing available USE flags</title> |
| 188 |
<body> |
| 189 |
|
| 190 |
<p> |
| 191 |
-Let us take the example of <c>seamonkey</c>: what USE-flags does it listen to? To |
| 192 |
+Let us take the example of <c>seamonkey</c>: what USE flags does it listen to? To |
| 193 |
find out, we use <c>emerge</c> with the <c>--pretend</c> and <c>--verbose</c> |
| 194 |
options: |
| 195 |
</p> |
| 196 |
|
| 197 |
-<pre caption="Viewing the used USE-flags"> |
| 198 |
+<pre caption="Viewing the used USE flags"> |
| 199 |
# <i>emerge --pretend --verbose seamonkey</i> |
| 200 |
These are the packages that I would merge, in order: |
| 201 |
|
| 202 |
@@ -348,11 +348,11 @@ |
| 203 |
</pre> |
| 204 |
|
| 205 |
<p> |
| 206 |
-Now run <c>equery</c> with the <c>uses</c> argument to view the USE-flags of a |
| 207 |
+Now run <c>equery</c> with the <c>uses</c> argument to view the USE flags of a |
| 208 |
certain package. For instance, for the <c>gnumeric</c> package: |
| 209 |
</p> |
| 210 |
|
| 211 |
-<pre caption="Using equery to view used USE-flags"> |
| 212 |
+<pre caption="Using equery to view used USE flags"> |
| 213 |
# <i>equery uses =gnumeric-1.6.3 -a</i> |
| 214 |
[ Searching for packages matching =gnumeric-1.6.3... ] |
| 215 |
[ Colour Code : <comment>set</comment> <i>unset</i> ] |
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
-- |
| 220 |
gentoo-doc-cvs@g.o mailing list |
Archives