|
Lines 117-126
Link Here
|
| 117 |
|
117 |
|
| 118 |
<p> |
118 |
<p> |
| 119 |
<c>equery</c> is a tool that displays useful information about the packages on |
119 |
<c>equery</c> is a tool that displays useful information about the packages on |
| 120 |
your system. <c>equery</c> is based on a system of modules. |
120 |
your system. <c>equery</c> is based on a system of modules. |
| 121 |
Every module has a shorthand name. For example, <c>equery l gcc</c> is the same |
121 |
Every module has a shorthand name. For example, <c>equery l gcc</c> is the same |
| 122 |
as <c>equery list gcc</c>. <c>equery --help</c> explains global options |
122 |
as <c>equery list gcc</c>. <c>equery --help</c> explains global options |
| 123 |
and lists all available modules and their shorthand names. |
123 |
and lists all available modules and their shorthand names. |
| 124 |
<c>equery --help module</c> will display the help screen for a specific |
124 |
<c>equery --help module</c> will display the help screen for a specific |
| 125 |
module. Lastly, <c>man equery</c> provides a detailed explanation of all |
125 |
module. Lastly, <c>man equery</c> provides a detailed explanation of all |
| 126 |
available modules and options, and provides useful examples. |
126 |
available modules and options, and provides useful examples. |
|
Lines 155-165
Link Here
|
| 155 |
|
155 |
|
| 156 |
<comment>(Most equery modules take multiple input):</comment> |
156 |
<comment>(Most equery modules take multiple input):</comment> |
| 157 |
$ <i>equery hasuse sse sse2</i> |
157 |
$ <i>equery hasuse sse sse2</i> |
| 158 |
* Searching for USE flag sse ... |
158 |
* Searching for USE flag sse ... |
| 159 |
[IP-] [ ] media-libs/flac-1.2.1-r3 (0) |
159 |
[IP-] [ ] media-libs/flac-1.2.1-r3 (0) |
| 160 |
[IP-] [ ] media-libs/speex-1.2_beta3_p2 (0) |
160 |
[IP-] [ ] media-libs/speex-1.2_beta3_p2 (0) |
| 161 |
|
161 |
|
| 162 |
* Searching for USE flag sse2 ... |
162 |
* Searching for USE flag sse2 ... |
| 163 |
[IP-] [ ] dev-libs/openssl-0.9.8k (0) |
163 |
[IP-] [ ] dev-libs/openssl-0.9.8k (0) |
| 164 |
[IP-] [ ] x11-libs/pixman-0.16.0 (0) |
164 |
[IP-] [ ] x11-libs/pixman-0.16.0 (0) |
| 165 |
|
165 |
|
|
Lines 175-186
Link Here
|
| 175 |
|
175 |
|
| 176 |
<note> |
176 |
<note> |
| 177 |
Globbing support replaced a number of older options in <c>equery</c>. |
177 |
Globbing support replaced a number of older options in <c>equery</c>. |
| 178 |
For example, to act on all packages in a certain set, use <c>'*'</c>. |
178 |
For example, to act on all packages in a certain set, use <c>'*'</c>. |
| 179 |
To act on all packages in a category, use <c>'category-name/*'</c>. |
179 |
To act on all packages in a category, use <c>'category-name/*'</c>. |
| 180 |
</note> |
180 |
</note> |
| 181 |
|
181 |
|
| 182 |
<warn> |
182 |
<warn> |
| 183 |
Don't forget to quote input when using special shell characters |
183 |
Don't forget to quote input when using special shell characters |
| 184 |
like asterisks or greater than/less than signs. |
184 |
like asterisks or greater than/less than signs. |
| 185 |
</warn> |
185 |
</warn> |
| 186 |
|
186 |
|
|
Lines 197-203
Link Here
|
| 197 |
|
197 |
|
| 198 |
<pre caption="Finding the Package that Installed a Given File"> |
198 |
<pre caption="Finding the Package that Installed a Given File"> |
| 199 |
$ <i>equery belongs -e /usr/bin/glxgears</i> |
199 |
$ <i>equery belongs -e /usr/bin/glxgears</i> |
| 200 |
* Searching for /usr/bin/glxgears ... |
200 |
* Searching for /usr/bin/glxgears ... |
| 201 |
x11-apps/mesa-progs-7.5.1 (/usr/bin/glxgears) |
201 |
x11-apps/mesa-progs-7.5.1 (/usr/bin/glxgears) |
| 202 |
</pre> |
202 |
</pre> |
| 203 |
|
203 |
|
|
Lines 216-222
Link Here
|
| 216 |
|
216 |
|
| 217 |
<p> |
217 |
<p> |
| 218 |
<c>changes</c> lets you view ChangeLog entries for a package version or range |
218 |
<c>changes</c> lets you view ChangeLog entries for a package version or range |
| 219 |
of versions. Imagine after an <c>emerge --sync</c>, you |
219 |
of versions. Imagine after an <c>emerge --sync</c>, you |
| 220 |
notice Portage is going to be upgraded and want to check what has changed: |
220 |
notice Portage is going to be upgraded and want to check what has changed: |
| 221 |
</p> |
221 |
</p> |
| 222 |
|
222 |
|
|
Lines 284-293
Link Here
|
| 284 |
it will find the packages <e>it</e> depends on (not that depend on it). |
284 |
it will find the packages <e>it</e> depends on (not that depend on it). |
| 285 |
When it finds a dependency, it will recursively search for all of |
285 |
When it finds a dependency, it will recursively search for all of |
| 286 |
<e>that</e> package's dependencies. Control how deep the tree gets with |
286 |
<e>that</e> package's dependencies. Control how deep the tree gets with |
| 287 |
the <c>--depth</c> option. |
287 |
the <c>--depth</c> option. |
| 288 |
</p> |
288 |
</p> |
| 289 |
|
289 |
|
| 290 |
<pre caption="Viewing Dependency Graph for cdrtools"> |
290 |
<pre caption="Viewing Dependency Graph for mozilla-firefox"> |
| 291 |
$ <i>equery depgraph mozilla-firefox</i> |
291 |
$ <i>equery depgraph mozilla-firefox</i> |
| 292 |
* Searching for mozilla-firefox ... |
292 |
* Searching for mozilla-firefox ... |
| 293 |
* dependency graph for www-client/mozilla-firefox-2.0.0.19: |
293 |
* dependency graph for www-client/mozilla-firefox-2.0.0.19: |
|
Lines 318-324
Link Here
|
| 318 |
|
318 |
|
| 319 |
<p> |
319 |
<p> |
| 320 |
<c>equery</c> can list all the files installed by an ebuild with the |
320 |
<c>equery</c> can list all the files installed by an ebuild with the |
| 321 |
<c>files</c> command. Try <c>--tree</c> to get an easy to read directory |
321 |
<c>files</c> module. Try <c>--tree</c> to get an easy to read directory |
| 322 |
layout. Use <c>--filter</c> to only find a certain type of file. For example, |
322 |
layout. Use <c>--filter</c> to only find a certain type of file. For example, |
| 323 |
to find where executables were installed, use <c>--filter=cmd</c>, and to |
323 |
to find where executables were installed, use <c>--filter=cmd</c>, and to |
| 324 |
quickly find the configuration file location, try <c>--filter=conf</c>. |
324 |
quickly find the configuration file location, try <c>--filter=conf</c>. |
|
Lines 373-390
Link Here
|
| 373 |
<p> |
373 |
<p> |
| 374 |
You can use <c>hasuse</c> to find out which packages have a given USE flag. |
374 |
You can use <c>hasuse</c> to find out which packages have a given USE flag. |
| 375 |
<c>hasuse</c> won't tell you if the flag is enabled, only if the ebuild lists |
375 |
<c>hasuse</c> won't tell you if the flag is enabled, only if the ebuild lists |
| 376 |
it as an option. See the EXAMPLES section of <c>hasuse</c> in the |
376 |
it as an option. See the EXAMPLES section of <c>hasuse</c> in the |
| 377 |
<c>equery</c> man page for more tip on getting that information. |
377 |
<c>equery</c> man page for more tip on getting that information. |
| 378 |
</p> |
378 |
</p> |
| 379 |
|
379 |
|
| 380 |
<pre caption="Searching For Installed Packages that Use the qt3 or qt4 USE Flags"> |
380 |
<pre caption="Searching For Installed Packages that Use the qt3 or qt4 USE Flags"> |
| 381 |
$ <i>equery hasuse qt3 qt4</i> |
381 |
$ <i>equery hasuse qt3 qt4</i> |
| 382 |
* Searching for USE flag qt3 ... |
382 |
* Searching for USE flag qt3 ... |
| 383 |
[IP-] [ ] app-crypt/pinentry-0.7.5 (0) |
383 |
[IP-] [ ] app-crypt/pinentry-0.7.5 (0) |
| 384 |
[IP-] [ ] net-dns/avahi-0.6.24-r2 (0) |
384 |
[IP-] [ ] net-dns/avahi-0.6.24-r2 (0) |
| 385 |
[IP-] [ ] net-wireless/wpa_supplicant-0.6.9 (0) |
385 |
[IP-] [ ] net-wireless/wpa_supplicant-0.6.9 (0) |
| 386 |
|
386 |
|
| 387 |
* Searching for USE flag qt4 ... |
387 |
* Searching for USE flag qt4 ... |
| 388 |
[IP-] [ ] net-dns/avahi-0.6.24-r2 (0) |
388 |
[IP-] [ ] net-dns/avahi-0.6.24-r2 (0) |
| 389 |
[IP-] [ ] net-wireless/wpa_supplicant-0.6.9 (0) |
389 |
[IP-] [ ] net-wireless/wpa_supplicant-0.6.9 (0) |
| 390 |
</pre> |
390 |
</pre> |
|
Lines 396-403
Link Here
|
| 396 |
<body> |
396 |
<body> |
| 397 |
|
397 |
|
| 398 |
<p> |
398 |
<p> |
| 399 |
<c>list</c> is a simple, yet powerful module to list packages that are installed, |
399 |
<c>list</c> is a simple, yet powerful module to list packages that are |
| 400 |
in the Portage tree or in an overlay. |
400 |
installed, in the Portage tree or in an overlay. |
| 401 |
</p> |
401 |
</p> |
| 402 |
|
402 |
|
| 403 |
<pre caption="Listing Installed Packages with list"> |
403 |
<pre caption="Listing Installed Packages with list"> |
|
Lines 420-426
Link Here
|
| 420 |
|
420 |
|
| 421 |
<p> |
421 |
<p> |
| 422 |
The standard query will search installed packages for the given package name. |
422 |
The standard query will search installed packages for the given package name. |
| 423 |
Passing in '*' displays all packages in the set. In the leftmost field, we |
423 |
Passing in '*' displays all packages in the set. In the leftmost field, we |
| 424 |
see that all the above packages are <c>I</c>nstalled and from the <c>P</c>ortage |
424 |
see that all the above packages are <c>I</c>nstalled and from the <c>P</c>ortage |
| 425 |
tree. They're not masked (the second field is blank), and they're all installed |
425 |
tree. They're not masked (the second field is blank), and they're all installed |
| 426 |
in the default slot (0). |
426 |
in the default slot (0). |
|
Lines 447-453
Link Here
|
| 447 |
|
447 |
|
| 448 |
<p> |
448 |
<p> |
| 449 |
In this example you can see version 7.2.182 is installed and there are no |
449 |
In this example you can see version 7.2.182 is installed and there are no |
| 450 |
versions available from an overlay. You can see which versions are keyword |
450 |
versions available from an overlay. You can see which versions are keyword |
| 451 |
masked by the <c>~</c> in the second field. |
451 |
masked by the <c>~</c> in the second field. |
| 452 |
</p> |
452 |
</p> |
| 453 |
|
453 |
|
|
Lines 459-469
Link Here
|
| 459 |
|
459 |
|
| 460 |
<p> |
460 |
<p> |
| 461 |
Each package in the Portage tree provides at least some metadata about |
461 |
Each package in the Portage tree provides at least some metadata about |
| 462 |
its maintainer, herd, etc. Read about <uri |
462 |
its maintainer, herd, etc. Read about <uri |
| 463 |
link="http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=4">Gentoo |
463 |
link="http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=4"> |
| 464 |
Metadata</uri>. The amount of useful information depends on how much package |
464 |
Gentoo Metadata</uri>. The amount of useful information depends on how much |
| 465 |
maintainers decide to provide. With no options, <c>meta</c> returns some basic |
465 |
package maintainers decide to provide. With no options, <c>meta</c> returns |
| 466 |
useful information. |
466 |
some basic useful information. |
| 467 |
</p> |
467 |
</p> |
| 468 |
|
468 |
|
| 469 |
<pre caption="Getting Package Metadata with meta"> |
469 |
<pre caption="Getting Package Metadata with meta"> |
|
Lines 474-481
Link Here
|
| 474 |
Upstream: None specified |
474 |
Upstream: None specified |
| 475 |
Location: /usr/portage/app-office/gnucash |
475 |
Location: /usr/portage/app-office/gnucash |
| 476 |
Keywords: 2.2.9-r1:0: alpha amd64 ppc sparc x86 |
476 |
Keywords: 2.2.9-r1:0: alpha amd64 ppc sparc x86 |
| 477 |
Keywords: 2.2.9-r2:0: |
477 |
Keywords: 2.2.9-r2:0: |
| 478 |
Keywords: 2.3.8:0: |
478 |
Keywords: 2.3.8:0: |
| 479 |
Keywords: 2.3.10:0: ~alpha ~amd64 ~ppc ~sparc ~x86 |
479 |
Keywords: 2.3.10:0: ~alpha ~amd64 ~ppc ~sparc ~x86 |
| 480 |
</pre> |
480 |
</pre> |
| 481 |
|
481 |
|
|
Lines 599-605
Link Here
|
| 599 |
</pre> |
599 |
</pre> |
| 600 |
|
600 |
|
| 601 |
<p> |
601 |
<p> |
| 602 |
Lastly, if none of the above features of <c>equery</c> have answered your |
602 |
Lastly, if none of the above features of <c>equery</c> have answered your |
| 603 |
question, try using <c>which</c> to manually search an ebuild with programs |
603 |
question, try using <c>which</c> to manually search an ebuild with programs |
| 604 |
like <c>cat</c>, <c>less</c> or <c>grep</c>: |
604 |
like <c>cat</c>, <c>less</c> or <c>grep</c>: |
| 605 |
</p> |
605 |
</p> |
|
Lines 610-619
Link Here
|
| 610 |
</pre> |
610 |
</pre> |
| 611 |
|
611 |
|
| 612 |
<warn> |
612 |
<warn> |
| 613 |
Be aware that equery currently changes the format of the output if it is sent |
613 |
Be aware that <c>equery</c> currently changes the format of the output if it |
| 614 |
through a pipe. The piped format is intended to be easier to parse by tools, but |
614 |
is sent through a pipe. The piped format is intended to be easier to parse by |
| 615 |
you can also turn it off by adding the <c>--no-pipe</c> option. If you write |
615 |
tools, but you can also turn it off by adding the <c>--no-pipe</c> option. If |
| 616 |
scripts that employ equery, you should be aware of this. |
616 |
you write scripts that employ <c>equery</c>, you should be aware of this. |
| 617 |
</warn> |
617 |
</warn> |
| 618 |
|
618 |
|
| 619 |
</body> |
619 |
</body> |
