nightmorph    07/04/14 03:09:30

  Modified:             hb-working-use.xml
  Log:
  massive english fixes. it's 'USE flag', not 'USE-flag'.

Revision  Changes    Path
1.46                 xml/htdocs/doc/en/handbook/hb-working-use.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml?rev=1.46&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml?rev=1.46&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml?r1=1.45&r2=1.46

Index: hb-working-use.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- hb-working-use.xml  20 Feb 2007 22:07:04 -0000      1.45
+++ hb-working-use.xml  14 Apr 2007 03:09:30 -0000      1.46
@@ -4,22 +4,22 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v 1.45 
2007/02/20 22:07:04 nightmorph Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v 1.46 
2007/04/14 03:09:30 nightmorph Exp $ -->
 
 <sections>
 
 <abstract>
-USE-flags are a very important aspect of Gentoo. In this chapter, you learn to
-work with USE-flags and understand how USE-flags interact with your system.
+USE flags are a very important aspect of Gentoo. In this chapter, you learn to
+work with USE flags and understand how USE flags interact with your system.
 </abstract>
 
 <version>1.36</version>
 <date>2007-02-20</date>
 
 <section>
-<title>What are USE-flags?</title>
+<title>What are USE flags?</title>
 <subsection>
-<title>The ideas behind USE-flags</title>
+<title>The ideas behind USE flags</title>
 <body>
 
 <p>
@@ -34,7 +34,7 @@
 what features a certain package should support. If you don't need OpenGL, why
 would you bother installing OpenGL and build OpenGL support in most of your
 packages? If you don't want to use KDE, why would you bother compiling packages
-with KDE-support if those packages work flawlessly without?
+with KDE support if those packages work flawlessly without?
 </p>
 
 <p>
@@ -47,12 +47,12 @@
 </body>
 </subsection>
 <subsection>
-<title>Definition of a USE-flag</title>
+<title>Definition of a USE flag</title>
 <body>
 
 <p>
-Enter the USE-flags. Such a flag is a keyword that embodies support and
-dependency-information for a certain concept. If you define a certain 
USE-flag, 
+Enter the USE flags. Such a flag is a keyword that embodies support and
+dependency-information for a certain concept. If you define a certain USE 
flag, 
 Portage will know that you want support for the chosen keyword. Of course
 this also alters the dependency information for a package.
 </p>
@@ -75,32 +75,32 @@
 </body>
 </subsection>
 <subsection>
-<title>What USE-flags exist?</title>
+<title>What USE flags exist?</title>
 <body>
 
 <p>
-There are two types of USE-flags: <e>global</e> and <e>local</e> USE-flags.
+There are two types of USE flags: <e>global</e> and <e>local</e> USE flags.
 </p>
 
 <ul>
   <li>
-    A <e>global</e> USE-flag is used by several packages, system-wide. This is 
-    what most people see as USE-flags.
+    A <e>global</e> USE flag is used by several packages, system-wide. This is 
+    what most people see as USE flags.
   </li>
   <li>
-    A <e>local</e> USE-flag is used by a single package to make 
package-specific
+    A <e>local</e> USE flag is used by a single package to make 
package-specific
     decisions.
   </li>
 </ul>
 
 <p>
-A list of available global USE-flags can be found <uri
+A list of available global USE flags can be found <uri
 link="/dyn/use-index.xml">online</uri> or locally in
 <path>/usr/portage/profiles/use.desc</path>.
 </p>
 
 <p>
-A list of available local USE-flags can be found locally in
+A list of available local USE flags can be found locally in
 <path>/usr/portage/profiles/use.local.desc</path>.
 </p>
 
@@ -108,20 +108,20 @@
 </subsection>
 </section>
 <section>
-<title>Using USE-flags</title>
+<title>Using USE flags</title>
 <subsection>
-<title>Declare permanent USE-flags</title>
+<title>Declare permanent USE flags</title>
 <body>
 
 <p>
-In the hope you are convinced of the importance of USE-flags we will now inform
-you how to declare USE-flags.
+In the hope you are convinced of the importance of USE flags we will now inform
+you how to declare USE flags.
 </p>
 
 <p>
-As previously mentioned, all USE-flags are declared inside the <c>USE</c>
-variable. To make it easy for users to search and pick USE-flags, we already
-provide a <e>default</e> USE setting. This setting is a collection of USE-flags
+As previously mentioned, all USE flags are declared inside the <c>USE</c>
+variable. To make it easy for users to search and pick USE flags, we already
+provide a <e>default</e> USE setting. This setting is a collection of USE flags
 we think are commonly used by the Gentoo users. This default setting is 
declared
 in the <path>make.defaults</path> files part of your profile.
 </p>
@@ -157,8 +157,8 @@
 <p>
 To change this default setting, you need to add or remove keywords to the
 <c>USE</c> variable. This is done globally by defining the <c>USE</c> variable 
-in <path>/etc/make.conf</path>. In this variable you add the extra USE-flags 
you
-require, or remove the USE-flags you don't want. This latter is done by
+in <path>/etc/make.conf</path>. In this variable you add the extra USE flags 
you
+require, or remove the USE flags you don't want. This latter is done by
 prefixing the keyword with the minus-sign ("-").
 </p>
 
@@ -205,19 +205,19 @@
 </body>
 </subsection>
 <subsection>
-<title>Declare temporary USE-flags</title>
+<title>Declare temporary USE flags</title>
 <body>
 
 <p>
-Sometimes you want to set a certain USE-setting only once. Instead of editing
-<path>/etc/make.conf</path> twice (to do and undo the USE-changes) you can 
just 
-declare the USE-variable as environment variable. Remember that, when you
+Sometimes you want to set a certain USE setting only once. Instead of editing
+<path>/etc/make.conf</path> twice (to do and undo the USE changes) you can 
just 
+declare the USE variable as environment variable. Remember that, when you
 re-emerge or update this application (either explicitly or as part of a system 
 update) your changes will be lost!
 </p>
 
 <p>
-As an example we will temporarily remove java from the USE-setting
+As an example we will temporarily remove java from the USE setting
 during the installation of seamonkey.
 </p>
 
@@ -316,18 +316,18 @@
 </subsection>
 </section>
 <section>
-<title>Package specific USE-flags</title>
+<title>Package specific USE flags</title>
 <subsection>
-<title>Viewing available USE-flags</title>
+<title>Viewing available USE flags</title>
 <body>
 
 <p>
-Let us take the example of <c>seamonkey</c>: what USE-flags does it listen to? 
To
+Let us take the example of <c>seamonkey</c>: what USE flags does it listen to? 
To
 find out, we use <c>emerge</c> with the <c>--pretend</c> and <c>--verbose</c>
 options:
 </p>
 
-<pre caption="Viewing the used USE-flags">
+<pre caption="Viewing the used USE flags">
 # <i>emerge --pretend --verbose seamonkey</i>
 These are the packages that I would merge, in order:
 
@@ -348,11 +348,11 @@
 </pre>
 
 <p>
-Now run <c>equery</c> with the <c>uses</c> argument to view the USE-flags of a
+Now run <c>equery</c> with the <c>uses</c> argument to view the USE flags of a
 certain package. For instance, for the <c>gnumeric</c> package:
 </p>
 
-<pre caption="Using equery to view used USE-flags">
+<pre caption="Using equery to view used USE flags">
 # <i>equery uses =gnumeric-1.6.3 -a</i>
 [ Searching for packages matching =gnumeric-1.6.3... ]
 [ Colour Code : <comment>set</comment> <i>unset</i> ]



-- 
[EMAIL PROTECTED] mailing list

Reply via email to