[gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: gentoolkit.xml

[Sven Vermeulen (swift)]

swift       11/08/15 19:30:36

  Modified:             gentoolkit.xml
  Log:
  Coding style updates, thanks to Chema Alonso (nimiux)

Revision  Changes    Path
1.36                 xml/htdocs/doc/en/gentoolkit.xml

file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoolkit.xml?rev=1.36&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoolkit.xml?rev=1.36&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoolkit.xml?r1=1.35&r2=1.36

Index: gentoolkit.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- gentoolkit.xml	15 Aug 2011 19:29:48 -0000	1.35
+++ gentoolkit.xml	15 Aug 2011 19:30:36 -0000	1.36
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.35 2011/08/15 19:29:48 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.36 2011/08/15 19:30:36 swift Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide>
@@ -41,7 +41,7 @@
 <!-- Licensed under GFDL -->
 
 <version>4</version>
-<date>2011-08-15</date>
+<date>2011-08-16</date>
 
 <chapter>
 <title>Introduction</title>
@@ -117,10 +117,10 @@
 
 <p>
 <c>equery</c> is a tool that displays useful information about the packages on
-your system. <c>equery</c> is based on a system of modules. 
+your system. <c>equery</c> is based on a system of modules.
 Every module has a shorthand name. For example, <c>equery l gcc</c> is the same
 as <c>equery list gcc</c>.  <c>equery --help</c> explains global options
-and lists all available modules and their shorthand names. 
+and lists all available modules and their shorthand names.
 <c>equery --help module</c> will display the help screen for a specific
 module. Lastly, <c>man equery</c> provides a detailed explanation of all
 available modules and options, and provides useful examples.
@@ -155,11 +155,11 @@
 
 <comment>(Most equery modules take multiple input):</comment>
 $ <i>equery hasuse sse sse2</i>
- * Searching for USE flag sse ... 
+ * Searching for USE flag sse ...
 [IP-] [  ] media-libs/flac-1.2.1-r3 (0)
 [IP-] [  ] media-libs/speex-1.2_beta3_p2 (0)
 
- * Searching for USE flag sse2 ... 
+ * Searching for USE flag sse2 ...
 [IP-] [  ] dev-libs/openssl-0.9.8k (0)
 [IP-] [  ] x11-libs/pixman-0.16.0 (0)
 
@@ -175,12 +175,12 @@
 
 <note>
 Globbing support replaced a number of older options in <c>equery</c>.
-For example, to act on all packages in a certain set, use <c>'*'</c>. 
+For example, to act on all packages in a certain set, use <c>'*'</c>.
 To act on all packages in a category, use <c>'category-name/*'</c>.
 </note>
 
 <warn>
-Don't forget to quote input when using special shell characters 
+Don't forget to quote input when using special shell characters
 like asterisks or greater than/less than signs.
 </warn>
 
@@ -197,7 +197,7 @@
 
 <pre caption="Finding the Package that Installed a Given File">
 $ <i>equery belongs -e /usr/bin/glxgears</i>
- * Searching for /usr/bin/glxgears ... 
+ * Searching for /usr/bin/glxgears ...
  x11-apps/mesa-progs-7.5.1 (/usr/bin/glxgears)
 </pre>
 
@@ -216,7 +216,7 @@
 
 <p>
 <c>changes</c> lets you view ChangeLog entries for a package version or range
-of versions. Imagine after an <c>emerge --sync</c>, you 
+of versions. Imagine after an <c>emerge --sync</c>, you
 notice Portage is going to be upgraded and want to check what has changed:
 </p>
 
@@ -284,7 +284,7 @@
 it will find the packages <e>it</e> depends on (not that depend on it).
 When it finds a dependency, it will recursively search for all of
 <e>that</e> package's dependencies. Control how deep the tree gets with
-the <c>--depth</c> option. 
+the <c>--depth</c> option.
 </p>
 
 <pre caption="Viewing Dependency Graph for mozilla-firefox">
@@ -373,18 +373,18 @@
 <p>
 You can use <c>hasuse</c> to find out which packages have a given USE flag.
 <c>hasuse</c> won't tell you if the flag is enabled, only if the ebuild lists
-it as an option. See the EXAMPLES section of <c>hasuse</c> in the 
+it as an option. See the EXAMPLES section of <c>hasuse</c> in the
 <c>equery</c> man page for more tip on getting that information.
 </p>
 
 <pre caption="Searching For Installed Packages that Use the qt3 or qt4 USE Flags">
 $ <i>equery hasuse qt3 qt4</i>
- * Searching for USE flag qt3 ... 
+ * Searching for USE flag qt3 ...
 [IP-] [  ] app-crypt/pinentry-0.7.5 (0)
 [IP-] [  ] net-dns/avahi-0.6.24-r2 (0)
 [IP-] [  ] net-wireless/wpa_supplicant-0.6.9 (0)
 
- * Searching for USE flag qt4 ... 
+ * Searching for USE flag qt4 ...
 [IP-] [  ] net-dns/avahi-0.6.24-r2 (0)
 [IP-] [  ] net-wireless/wpa_supplicant-0.6.9 (0)
 </pre>
@@ -396,8 +396,8 @@
 <body>
 
 <p>
-<c>list</c> is a simple, yet powerful module to list packages that are installed,
-in the Portage tree or in an overlay.
+<c>list</c> is a simple, yet powerful module to list packages that are
+installed, in the Portage tree or in an overlay.
 </p>
 
 <pre caption="Listing Installed Packages with list">
@@ -420,7 +420,7 @@
 
 <p>
 The standard query will search installed packages for the given package name.
-Passing in '*' displays all packages in the set. In the leftmost field, we 
+Passing in '*' displays all packages in the set. In the leftmost field, we
 see that all the above packages are <c>I</c>nstalled and from the <c>P</c>ortage
 tree. They're not masked (the second field is blank), and they're all installed
 in the default slot (0).
@@ -447,7 +447,7 @@
 
 <p>
 In this example you can see version 7.2.182 is installed and there are no
-versions available from an overlay. You can see which versions are keyword 
+versions available from an overlay. You can see which versions are keyword
 masked by the <c>~</c> in the second field.
 </p>
 
@@ -459,11 +459,11 @@
 
 <p>
 Each package in the Portage tree provides at least some metadata about
-its maintainer, herd, etc. Read about <uri 
-link="http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&amp;chap=4">Gentoo
-Metadata</uri>. The amount of useful information depends on how much package
-maintainers decide to provide. With no options, <c>meta</c> returns some basic
-useful information.
+its maintainer, herd, etc. Read about <uri
+link="http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&amp;chap=4">
+Gentoo Metadata</uri>. The amount of useful information depends on how much
+package maintainers decide to provide. With no options, <c>meta</c> returns
+some basic useful information.
 </p>
 
 <pre caption="Getting Package Metadata with meta">
@@ -474,8 +474,8 @@
  Upstream:    None specified
  Location:    /usr/portage/app-office/gnucash
  Keywords:    2.2.9-r1:0: alpha amd64 ppc sparc x86
- Keywords:    2.2.9-r2:0: 
- Keywords:    2.3.8:0: 
+ Keywords:    2.2.9-r2:0:
+ Keywords:    2.3.8:0:
  Keywords:    2.3.10:0: ~alpha ~amd64 ~ppc ~sparc ~x86
 </pre>
 
@@ -599,7 +599,7 @@
 </pre>
 
 <p>
-Lastly, if none of the above features of <c>equery</c> have answered your 
+Lastly, if none of the above features of <c>equery</c> have answered your
 question, try using <c>which</c> to manually search an ebuild with programs
 like <c>cat</c>, <c>less</c> or <c>grep</c>:
 </p>
@@ -610,10 +610,10 @@
 </pre>
 
 <warn>
-Be aware that equery currently changes the format of the output if it is sent
-through a pipe. The piped format is intended to be easier to parse by tools, but
-you can also turn it off by adding the <c>--no-pipe</c> option. If you write
-scripts that employ equery, you should be aware of this.
+Be aware that <c>equery</c> currently changes the format of the output if it
+is sent through a pipe. The piped format is intended to be easier to parse by
+tools, but you can also turn it off by adding the <c>--no-pipe</c> option. If
+you write scripts that employ <c>equery</c>, you should be aware of this.
 </warn>
 
 </body>