1 |
swift 11/08/15 19:30:36 |
2 |
|
3 |
Modified: gentoolkit.xml |
4 |
Log: |
5 |
Coding style updates, thanks to Chema Alonso (nimiux) |
6 |
|
7 |
Revision Changes Path |
8 |
1.36 xml/htdocs/doc/en/gentoolkit.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoolkit.xml?rev=1.36&view=markup |
11 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoolkit.xml?rev=1.36&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/gentoolkit.xml?r1=1.35&r2=1.36 |
13 |
|
14 |
Index: gentoolkit.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v |
17 |
retrieving revision 1.35 |
18 |
retrieving revision 1.36 |
19 |
diff -u -r1.35 -r1.36 |
20 |
--- gentoolkit.xml 15 Aug 2011 19:29:48 -0000 1.35 |
21 |
+++ gentoolkit.xml 15 Aug 2011 19:30:36 -0000 1.36 |
22 |
@@ -1,5 +1,5 @@ |
23 |
<?xml version="1.0" encoding="UTF-8"?> |
24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.35 2011/08/15 19:29:48 swift Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.36 2011/08/15 19:30:36 swift Exp $ --> |
26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
27 |
|
28 |
<guide> |
29 |
@@ -41,7 +41,7 @@ |
30 |
<!-- Licensed under GFDL --> |
31 |
|
32 |
<version>4</version> |
33 |
-<date>2011-08-15</date> |
34 |
+<date>2011-08-16</date> |
35 |
|
36 |
<chapter> |
37 |
<title>Introduction</title> |
38 |
@@ -117,10 +117,10 @@ |
39 |
|
40 |
<p> |
41 |
<c>equery</c> is a tool that displays useful information about the packages on |
42 |
-your system. <c>equery</c> is based on a system of modules. |
43 |
+your system. <c>equery</c> is based on a system of modules. |
44 |
Every module has a shorthand name. For example, <c>equery l gcc</c> is the same |
45 |
as <c>equery list gcc</c>. <c>equery --help</c> explains global options |
46 |
-and lists all available modules and their shorthand names. |
47 |
+and lists all available modules and their shorthand names. |
48 |
<c>equery --help module</c> will display the help screen for a specific |
49 |
module. Lastly, <c>man equery</c> provides a detailed explanation of all |
50 |
available modules and options, and provides useful examples. |
51 |
@@ -155,11 +155,11 @@ |
52 |
|
53 |
<comment>(Most equery modules take multiple input):</comment> |
54 |
$ <i>equery hasuse sse sse2</i> |
55 |
- * Searching for USE flag sse ... |
56 |
+ * Searching for USE flag sse ... |
57 |
[IP-] [ ] media-libs/flac-1.2.1-r3 (0) |
58 |
[IP-] [ ] media-libs/speex-1.2_beta3_p2 (0) |
59 |
|
60 |
- * Searching for USE flag sse2 ... |
61 |
+ * Searching for USE flag sse2 ... |
62 |
[IP-] [ ] dev-libs/openssl-0.9.8k (0) |
63 |
[IP-] [ ] x11-libs/pixman-0.16.0 (0) |
64 |
|
65 |
@@ -175,12 +175,12 @@ |
66 |
|
67 |
<note> |
68 |
Globbing support replaced a number of older options in <c>equery</c>. |
69 |
-For example, to act on all packages in a certain set, use <c>'*'</c>. |
70 |
+For example, to act on all packages in a certain set, use <c>'*'</c>. |
71 |
To act on all packages in a category, use <c>'category-name/*'</c>. |
72 |
</note> |
73 |
|
74 |
<warn> |
75 |
-Don't forget to quote input when using special shell characters |
76 |
+Don't forget to quote input when using special shell characters |
77 |
like asterisks or greater than/less than signs. |
78 |
</warn> |
79 |
|
80 |
@@ -197,7 +197,7 @@ |
81 |
|
82 |
<pre caption="Finding the Package that Installed a Given File"> |
83 |
$ <i>equery belongs -e /usr/bin/glxgears</i> |
84 |
- * Searching for /usr/bin/glxgears ... |
85 |
+ * Searching for /usr/bin/glxgears ... |
86 |
x11-apps/mesa-progs-7.5.1 (/usr/bin/glxgears) |
87 |
</pre> |
88 |
|
89 |
@@ -216,7 +216,7 @@ |
90 |
|
91 |
<p> |
92 |
<c>changes</c> lets you view ChangeLog entries for a package version or range |
93 |
-of versions. Imagine after an <c>emerge --sync</c>, you |
94 |
+of versions. Imagine after an <c>emerge --sync</c>, you |
95 |
notice Portage is going to be upgraded and want to check what has changed: |
96 |
</p> |
97 |
|
98 |
@@ -284,7 +284,7 @@ |
99 |
it will find the packages <e>it</e> depends on (not that depend on it). |
100 |
When it finds a dependency, it will recursively search for all of |
101 |
<e>that</e> package's dependencies. Control how deep the tree gets with |
102 |
-the <c>--depth</c> option. |
103 |
+the <c>--depth</c> option. |
104 |
</p> |
105 |
|
106 |
<pre caption="Viewing Dependency Graph for mozilla-firefox"> |
107 |
@@ -373,18 +373,18 @@ |
108 |
<p> |
109 |
You can use <c>hasuse</c> to find out which packages have a given USE flag. |
110 |
<c>hasuse</c> won't tell you if the flag is enabled, only if the ebuild lists |
111 |
-it as an option. See the EXAMPLES section of <c>hasuse</c> in the |
112 |
+it as an option. See the EXAMPLES section of <c>hasuse</c> in the |
113 |
<c>equery</c> man page for more tip on getting that information. |
114 |
</p> |
115 |
|
116 |
<pre caption="Searching For Installed Packages that Use the qt3 or qt4 USE Flags"> |
117 |
$ <i>equery hasuse qt3 qt4</i> |
118 |
- * Searching for USE flag qt3 ... |
119 |
+ * Searching for USE flag qt3 ... |
120 |
[IP-] [ ] app-crypt/pinentry-0.7.5 (0) |
121 |
[IP-] [ ] net-dns/avahi-0.6.24-r2 (0) |
122 |
[IP-] [ ] net-wireless/wpa_supplicant-0.6.9 (0) |
123 |
|
124 |
- * Searching for USE flag qt4 ... |
125 |
+ * Searching for USE flag qt4 ... |
126 |
[IP-] [ ] net-dns/avahi-0.6.24-r2 (0) |
127 |
[IP-] [ ] net-wireless/wpa_supplicant-0.6.9 (0) |
128 |
</pre> |
129 |
@@ -396,8 +396,8 @@ |
130 |
<body> |
131 |
|
132 |
<p> |
133 |
-<c>list</c> is a simple, yet powerful module to list packages that are installed, |
134 |
-in the Portage tree or in an overlay. |
135 |
+<c>list</c> is a simple, yet powerful module to list packages that are |
136 |
+installed, in the Portage tree or in an overlay. |
137 |
</p> |
138 |
|
139 |
<pre caption="Listing Installed Packages with list"> |
140 |
@@ -420,7 +420,7 @@ |
141 |
|
142 |
<p> |
143 |
The standard query will search installed packages for the given package name. |
144 |
-Passing in '*' displays all packages in the set. In the leftmost field, we |
145 |
+Passing in '*' displays all packages in the set. In the leftmost field, we |
146 |
see that all the above packages are <c>I</c>nstalled and from the <c>P</c>ortage |
147 |
tree. They're not masked (the second field is blank), and they're all installed |
148 |
in the default slot (0). |
149 |
@@ -447,7 +447,7 @@ |
150 |
|
151 |
<p> |
152 |
In this example you can see version 7.2.182 is installed and there are no |
153 |
-versions available from an overlay. You can see which versions are keyword |
154 |
+versions available from an overlay. You can see which versions are keyword |
155 |
masked by the <c>~</c> in the second field. |
156 |
</p> |
157 |
|
158 |
@@ -459,11 +459,11 @@ |
159 |
|
160 |
<p> |
161 |
Each package in the Portage tree provides at least some metadata about |
162 |
-its maintainer, herd, etc. Read about <uri |
163 |
-link="http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=4">Gentoo |
164 |
-Metadata</uri>. The amount of useful information depends on how much package |
165 |
-maintainers decide to provide. With no options, <c>meta</c> returns some basic |
166 |
-useful information. |
167 |
+its maintainer, herd, etc. Read about <uri |
168 |
+link="http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=4"> |
169 |
+Gentoo Metadata</uri>. The amount of useful information depends on how much |
170 |
+package maintainers decide to provide. With no options, <c>meta</c> returns |
171 |
+some basic useful information. |
172 |
</p> |
173 |
|
174 |
<pre caption="Getting Package Metadata with meta"> |
175 |
@@ -474,8 +474,8 @@ |
176 |
Upstream: None specified |
177 |
Location: /usr/portage/app-office/gnucash |
178 |
Keywords: 2.2.9-r1:0: alpha amd64 ppc sparc x86 |
179 |
- Keywords: 2.2.9-r2:0: |
180 |
- Keywords: 2.3.8:0: |
181 |
+ Keywords: 2.2.9-r2:0: |
182 |
+ Keywords: 2.3.8:0: |
183 |
Keywords: 2.3.10:0: ~alpha ~amd64 ~ppc ~sparc ~x86 |
184 |
</pre> |
185 |
|
186 |
@@ -599,7 +599,7 @@ |
187 |
</pre> |
188 |
|
189 |
<p> |
190 |
-Lastly, if none of the above features of <c>equery</c> have answered your |
191 |
+Lastly, if none of the above features of <c>equery</c> have answered your |
192 |
question, try using <c>which</c> to manually search an ebuild with programs |
193 |
like <c>cat</c>, <c>less</c> or <c>grep</c>: |
194 |
</p> |
195 |
@@ -610,10 +610,10 @@ |
196 |
</pre> |
197 |
|
198 |
<warn> |
199 |
-Be aware that equery currently changes the format of the output if it is sent |
200 |
-through a pipe. The piped format is intended to be easier to parse by tools, but |
201 |
-you can also turn it off by adding the <c>--no-pipe</c> option. If you write |
202 |
-scripts that employ equery, you should be aware of this. |
203 |
+Be aware that <c>equery</c> currently changes the format of the output if it |
204 |
+is sent through a pipe. The piped format is intended to be easier to parse by |
205 |
+tools, but you can also turn it off by adding the <c>--no-pipe</c> option. If |
206 |
+you write scripts that employ <c>equery</c>, you should be aware of this. |
207 |
</warn> |
208 |
|
209 |
</body> |