/[gentoo]/xml/htdocs/doc/en/gentoolkit.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoolkit.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.5 Revision 1.10
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoolkit.xml,v 1.10 2004/03/26 12:58:32 cam Exp $ -->
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3 4
4<guide link = "/doc/en/gentoolkit.xml"> 5<guide link="/doc/en/gentoolkit.xml">
5<title>Gentoolkit</title> 6<title>Gentoolkit</title>
6<author title="Author"><mail link="mbutcher@aleph-null.tv"> 7
7Matt Butcher</mail> 8<author title="Author">
9 <mail link="mbutcher@aleph-null.tv">Matt Butcher</mail>
8</author> 10</author>
9 11
10<author title="Editor"><!-- zhen@gentoo.org --> 12<author title="Editor">
11 John P. Davis 13 <!-- zhen@gentoo.org -->John P. Davis
12</author> 14</author>
15
16<author title="Editor">
17 <mail link="erwin@gentoo.org">Erwin</mail>
18</author>
19
13<!-- Licensed under GFDL --> 20<!-- Licensed under GFDL -->
14 21
15<abstract> 22<abstract>
16 Gentoolkit is a suite of tools to ease the administration of a Gentoo system. 23Gentoolkit is a suite of tools to ease the administration of a Gentoo system.
17 This document covers the basics of 24This document covers the basics of some of the tools present in Gentoolkit.
18 some of the tools present in Gentoolkit.
19</abstract> 25</abstract>
20 26
21<version>1.1</version> 27<version>1.2</version>
22<date>25 September 2002</date> 28<date>December 1, 2003</date>
23 29
24<chapter> 30<chapter>
25 <title>Introduction</title> 31<title>Introduction</title>
26 <section> 32<section>
27 <title>What is Gentoolkit?</title> 33<title>What is Gentoolkit?</title>
28 <body> 34<body>
35
36<p>
29 <p>Gentoo is a unique distribution, and presents some complexities that 37Gentoo is a unique distribution, and presents some complexities that simply
30 simply don't exist for other distributions. As Gentoo developers 38don't exist for other distributions. As Gentoo developers and contributors
31 and contributors discovered some of these complexities, they also 39discovered some of these complexities, they also wrote tools to help users and
32 wrote tools to help users and administrators work around them. 40administrators work around them. Many of these tools have been contributed to
33 Many of these tools have been contributed to the Gentoo project, 41the Gentoo project, and are included in the package
34 and are included in the package <path>app-admin/gentoolkit</path>. 42<c>app-portage/gentoolkit</c>.
35 </p> 43</p>
36 44
45<p>
37 <p>Gentoolkit contains a whole bunch of useful tools to help manage 46Gentoolkit contains a whole bunch of useful tools to help manage Portage and the
38 Portage and the ebuild architecture. Most users -- particularly 47ebuild architecture. Most users -- particularly those who update systems often
39 those who update systems often -- will benefit from having 48-- will benefit from having gentoolkit installed.
40 gentoolkit installed.</p> 49</p>
50
41 </body> 51</body>
42 </section> 52</section>
53
43 <section> 54<section>
44 <title>Installation</title> 55<title>Installation</title>
45 <body> 56<body>
57
58<p>
46 <p>Just as with any Gentoo package, installation is just a simple 59Just as with any Gentoo package, installation is just a simple emerge.
47 emerge. 60</p>
48 </p>
49 61
50 <pre> 62<pre>
51<i>emerge gentoolkit </i> 63# <i>emerge gentoolkit</i>
52 </pre> 64</pre>
65
66<note>
53 <note>Many of the tools in gentoolkit reveal important information 67Many of the tools in gentoolkit reveal important information about your system
54 about your system or require root permissions. For that reason, 68or require root permissions. For that reason, some of the programs may only be
55 some of the programs may only be executed (or only function 69executed (or only function properly) if run by a user with root permissions.
56 properly) if run by a user with root permissions.</note> 70</note>
71
57 </body> 72</body>
58 </section> 73</section>
74
59 <section> 75<section>
60 <title>Finding Documentation</title> 76<title>Finding Documentation</title>
61 <body> 77<body>
62 78
63 <p> 79<p>
64 At the time of this writing, not all of the programs in gentoolkit 80At the time of this writing, not all of the programs in gentoolkit are well
65 are well documented. Some have man pages, but not all. Any documentation 81documented. Some have man pages, but not all. Any documentation that a program
66 that a program might have (other than man pages) is stored in 82might have (other than man pages) is stored in
67 <path>/usr/doc/gentoolkit-[version]/[program-name]/</path>. 83<path>/usr/doc/gentoolkit-[version]/[program-name]/</path>.
68 </p> 84</p>
85
69 </body> 86</body>
70 </section> 87</section>
71</chapter> 88</chapter>
89
72<chapter> 90<chapter>
73 <title>Querying Package Data with qpkg</title> 91<title>Querying Package Data with qpkg</title>
74 <section> 92<section>
75
76 <title>Introduction</title> 93<title>Introduction</title>
77 <body> 94<body>
95
96<p>
78 <p><c>qpkg</c> is flexible tool for determining information about ebuilds, 97<c>qpkg</c> is a flexible tool for determining information about ebuilds,
79 whether installed or not. It can provide information about what files belong 98whether installed or not. It can provide information about what files belong
80 to which ebuilds, whether multiple versions of the same package are installed, 99to which ebuilds, whether multiple versions of the same package are installed,
81 and what a particular ebuild does. 100and what a particular ebuild does.
82 </p> 101</p>
102
103<p>
83 <p>Calling <c>qpkg</c> with no arguments prints a list of all ebuilds, with asterisks 104Calling <c>qpkg</c> with no arguments prints a list of all ebuilds, with
84 (*) next to the packages that are installed on the system. 105asterisks (*) next to the packages that are installed on the system.
85 </p> 106</p>
107
108<note>
86 <note>By default, <c>qpkg</c> prints output in color. To turn this off on the command 109By default, <c>qpkg</c> prints output in color. To turn this off on the command
87 line, use the <c>--no-color</c> or <c>-nc</c> flag.</note> 110line, use the <c>--no-color</c> or <c>-nc</c> flag.
111</note>
88 112
89 </body> 113</body>
90 </section> 114</section>
115
91 <section> 116<section>
92 <title>Querying Package Information</title> 117<title>Querying Package Information</title>
93 <body> 118<body>
119
120<p>
94 <p>One of the most common uses for <c>qpkg</c> is determining what a given package 121One of the most common uses for <c>qpkg</c> is determining what a given package
95 is. For instance, while looking through <path>net-misc</path>, I saw a package 122is. For instance, while looking through <path>net-misc</path>, I saw a package
96 called <path>neon</path>. Having no idea what it was, I ran qpkg. 123called <path>neon</path>. Having no idea what it was, I ran qpkg.
97 </p> 124</p>
98 125
99 <pre> 126<pre>
100hebron root # <i>qpkg -i net-misc/neon 127# <i>qpkg -i net-misc/neon</i>
101net-misc/neon-0.15.3-r1 128net-misc/neon-0.15.3-r1
102 HTTP and WebDAV client library [ http://www.webdav.org/neon ] 129 HTTP and WebDAV client library [ http://www.webdav.org/neon ]
103net-misc/neon-0.18.5 130net-misc/neon-0.18.5
104 HTTP and WebDAV client library [ http://www.webdav.org/neon ] 131 HTTP and WebDAV client library [ http://www.webdav.org/neon ]
105net-misc/neon-0.19.2 132net-misc/neon-0.19.2
106 HTTP and WebDAV client library [ http://www.webdav.org/neon ] 133 HTTP and WebDAV client library [ http://www.webdav.org/neon ]
107net-misc/neon-0.19.2-r1 134net-misc/neon-0.19.2-r1
108 HTTP and WebDAV client library [ http://www.webdav.org/neon ] 135 HTTP and WebDAV client library [ http://www.webdav.org/neon ]
109net-misc/neon-0.21.1 136net-misc/neon-0.21.1
110 HTTP and WebDAV client library [ http://www.webdav.org/neon ] </i> 137 HTTP and WebDAV client library [ http://www.webdav.org/neon ]
111 </pre> 138</pre>
112 <p> 139
140<p>
113 <c>qpkg</c> read through the ebuild files for the five <path>net-misc/neon</path> 141<c>qpkg</c> read through the ebuild files for the five
114 ebuilds and printed out the information stored in DESCRIPTION and HOMEPAGE. 142<path>net-misc/neon</path> ebuilds and printed out the information stored in
115 </p> 143DESCRIPTION and HOMEPAGE.
144</p>
145
116 </body> 146</body>
117
118 </section> 147</section>
148
119 <section> 149<section>
120 <title>Listing Files Belonging to an Ebuild</title> 150<title>Listing Files Belonging to an Ebuild</title>
121 <body> 151<body>
122 <p> 152
153<p>
123 <c>qpkg</c> can also list the files that belong to an installed ebuild. I 154<c>qpkg</c> can also list the files that belong to an installed ebuild. I
124 Know that gentoolkit installed several tools, but I don't know what they 155Know that gentoolkit installed several tools, but I don't know what they
125 all are. To find out, I can do a <c>qpkg -l</c> 156all are. To find out, I can do a <c>qpkg -l</c>.
157</p>
126 158
127 </p> 159<pre>
128 <pre> 160# <i>qpkg -l app-portage/gentoolkit</i>
129hebron portage # <i>qpkg -l app-admin/gentoolkit
130app-admin/gentoolkit-0.1.14-r1 * 161app-portage/gentoolkit-0.1.14-r1 *
131CONTENTS: 162CONTENTS:
132/usr 163/usr
133/usr/share 164/usr/share
134/usr/share/gentoolkit 165/usr/share/gentoolkit
135/usr/share/gentoolkit/histogram.awk 166/usr/share/gentoolkit/histogram.awk
160/usr/sbin/mkebuild 191/usr/sbin/mkebuild
161/usr/sbin/emerge-webrsync 192/usr/sbin/emerge-webrsync
162/usr/sbin/epm 193/usr/sbin/epm
163/usr/sbin/etc-update 194/usr/sbin/etc-update
164/etc 195/etc
165/etc/etc-update.conf </i> 196/etc/etc-update.conf
166 </pre> 197</pre>
198
167 </body> 199</body>
168 </section> 200</section>
201
169 <section> 202<section>
170 <title>Finding the Package from Where a File Came</title> 203<title>Finding the Package from Where a File Came</title>
171 <body> 204<body>
172 205
173 <p> 206<p>
174 To find the package that a file came from, use the <c>-f</c> 207To find the package that a file came from, use the <c>-f</c> or
175 or <c>--find-file</c> flag. 208<c>--find-file</c> flag.
176 </p> 209</p>
210
177 <pre> 211<pre>
178 hebron portage # <i>qpkg -f net-www/mozilla * </i> 212# <i>qpkg -fnet-www/mozilla * </i>
179 </pre> 213</pre>
180 214
181 </body> 215</body>
182 </section> 216</section>
217
183 <section> 218<section>
184 <title>Listing Duplicate Packages</title> 219<title>Listing Duplicate Packages</title>
185 <body> 220<body>
186 <p> 221
222<p>
187 Sometimes multiple versions of the same package may exist. <c>qpkg --dup</c> 223Sometimes multiple versions of the same package may exist. <c>qpkg --dup</c>
188
189 will print a list of duplicate packages. The existence of a duplicate package 224will print a list of duplicate packages. The existence of a duplicate package
190 though may not indicate that the older version may be removed. They may fill 225though may not indicate that the older version may be removed. They may fill
191 different slots. To look for duplicates in the same slot, use 226different slots. To look for duplicates in the same slot, use
192 <c>qpkg --dups --slot</c>. I just updated KDE from 3.0 to 3.0.2, so I have some 227<c>qpkg --dups --slot</c>. I just updated KDE from 3.0 to 3.0.2, so I have some
193 duplicates in the same slot. 228duplicates in the same slot.
194 </p> 229</p>
195 <pre> 230
196hebron portage # <i>qpkg --dups --slot 231<pre>
232# <i>qpkg --dups --slot</i>
197app-admin/gentoolkit 233app-portage/gentoolkit
198kde-base/kdeaddons 234kde-base/kdeaddons
199kde-base/kdeadmin 235kde-base/kdeadmin
200kde-base/kdeartwork 236kde-base/kdeartwork
201kde-base/kdebase 237kde-base/kdebase
202kde-base/kdegames 238kde-base/kdegames
204kde-base/kdemultimedia 240kde-base/kdemultimedia
205kde-base/kdenetwork 241kde-base/kdenetwork
206kde-base/kdetoys 242kde-base/kdetoys
207kde-base/kdeutils 243kde-base/kdeutils
208media-libs/freetype 244media-libs/freetype
209x11-libs/qt </i> 245x11-libs/qt
210 </pre> 246</pre>
247
211 </body> 248</body>
212 </section> 249</section>
250
213 <section> 251<section>
214 <title>Verifying Package Integrity</title> 252<title>Verifying Package Integrity</title>
215
216 <body> 253<body>
217 <p> 254
255<p>
218 Sometimes it is useful to check a package's integrity to know that files 256Sometimes it is useful to check a package's integrity to know that files have
219 have not been replaced since they were installed. <c>qpkg</c> can 257not been replaced since they were installed. <c>qpkg</c> can verify md5 sums as
220 verify md5 sums as well as install times to indicate whether or not files 258well as install times to indicate whether or not files for the package might
221 for the package might have been corrupted, replaced, or removed. 259have been corrupted, replaced, or removed.
222 </p> 260</p>
261
262<p>
223 <p>To check both mtimes and md5 sums, use the <c>-c</c> flag.</p> 263To check both mtimes and md5 sums, use the <c>-c</c> flag.
264</p>
265
224 <pre> 266<pre>
225 267# <i>qpkg gnupg -c -v</i>
226hebron portage # <i>qpkg gnupg -c -v
227app-crypt/gnupg-1.0.6 * 268app-crypt/gnupg-1.0.6 *
228/usr/lib/gnupg/rndunix !md5! !mtime! 269/usr/lib/gnupg/rndunix !md5! !mtime!
229/usr/lib/gnupg/rndegd !md5! !mtime! 270/usr/lib/gnupg/rndegd !md5! !mtime!
230/usr/lib/gnupg/tiger !md5! !mtime! 271/usr/lib/gnupg/tiger !md5! !mtime!
231/usr/bin/gpg !md5! !mtime! 272/usr/bin/gpg !md5! !mtime!
250/usr/share/man/man1/gpg.1.gz !md5! !mtime! 291/usr/share/man/man1/gpg.1.gz !md5! !mtime!
251/usr/share/man/man1/gpgv.1.gz !md5! !mtime! 292/usr/share/man/man1/gpgv.1.gz !md5! !mtime!
25224/92 29324/92
253 294
254app-crypt/gnupg-1.0.7 * 295app-crypt/gnupg-1.0.7 *
2550/101 </i> 2960/101
256 </pre> 297</pre>
257 <p> 298
299<p>
258 As you can see, I have more than one version of GnuPG installed. <c>qpkg</c> 300As you can see, I have more than one version of GnuPG installed. <c>qpkg</c>
259 reports that many of the files from the older version have been changed since I 301reports that many of the files from the older version have been changed since I
260 installed it. Those packages were most likely modified when I updated 302installed it. Those packages were most likely modified when I updated from
261 from <path>gnupg-1.0.6</path> to <path>gnupg-1.0.7</path>. Note that the last two 303<path>gnupg-1.0.6</path> to <path>gnupg-1.0.7</path>. Note that the last two
262lines indicate
263 that 0 of 101 files from <path>gnupg-1.0.7</path> have been changed since I 304lines indicate that 0 of 101 files from <path>gnupg-1.0.7</path> have been
264installed. That 305changed since I installed. That is good. If any of them had been changed, I
265 is good. If any of them had been changed, I would be worried. 306would be worried.
266 </p> 307</p>
267 308
268 </body> 309</body>
269 </section> 310</section>
311
270 <section> 312<section>
271 <title>But Wait... There's More</title> 313<title>But Wait... There's More</title>
272 <body> 314<body>
273 <p> 315
316<p>
274 <c>qpkg</c> can be used for other querying tasks that I will not go over here. There 317<c>qpkg</c> can be used for other querying tasks that I will not go over here.
275is a very complete 318There is a very complete manpage for <c>qpkg</c>. Consult that for more
276 manpage for <c>qpkg</c>. Consult that for more information. 319information.
277 </p> 320</p>
278 321
279 </body> 322</body>
280 </section> 323</section>
281</chapter> 324</chapter>
325
282<chapter> 326<chapter>
283 <title>lintool</title> 327<title>lintool</title>
284 <section> 328<section>
285 <title>Introduction</title> 329<title>Introduction</title>
286 <body> 330<body>
287 <p>
288 331
332<p>
333
289 <c>lintool</c> is a program that checks ebuild scripts for conformance to 334<c>lintool</c> is a program that checks ebuild scripts for conformance to
290 standards and requirements. It is important for ebuild developers to use <c>lintool</c> 335standards and requirements. It is important for ebuild developers to use
291 to ensure that they are doing things correctly and not requiring the core team 336<c>lintool</c> to ensure that they are doing things correctly and not requiring
292 to do more than they already have to in order to include the ebuild in the Gentoo 337the core team to do more than they already have to in order to include the
293 repository. 338ebuild in the Gentoo repository.
294 </p> 339</p>
340
295 </body> 341</body>
296 </section> 342</section>
343
297 <section> 344<section>
298 <title>Use</title> 345<title>Use</title>
299
300 <body> 346<body>
301 <p> 347
348<p>
302 Running <c>lintool</c> will produce a nicely formatted list of checks and results that 349Running <c>lintool</c> will produce a nicely formatted list of checks and
303 it performs. 350results that it performs.
304 </p> 351</p>
305 <pre> 352
353<pre>
306hebron portage # <i>lintool app-crypt/gnupg/gnupg-1.0.7.ebuild 354# <i>lintool app-crypt/gnupg/gnupg-1.0.7.ebuild</i>
307app-crypt/gnupg/gnupg-1.0.7.ebuild : Not OK 355app-crypt/gnupg/gnupg-1.0.7.ebuild : Not OK
308 356
309------------------------------------------------------------------------------- 357-------------------------------------------------------------------------------
310 Summary for all 1 ebuild(s) checked # errors/warns 358 Summary for all 1 ebuild(s) checked # errors/warns
311 ------------------------------------------------------------------------------- 359 -------------------------------------------------------------------------------
319 Testing for presence of env vars : 1 / 1 367 Testing for presence of env vars : 1 / 1
320 Testing for sane USE flag usage : 0 / 0 368 Testing for sane USE flag usage : 0 / 0
321 369
322 Total number of ebuilds with errors : 1 (100%) 370 Total number of ebuilds with errors : 1 (100%)
323 Total number of ebuilds with warnings : 1 (100%) 371 Total number of ebuilds with warnings : 1 (100%)
324 </i> </pre> 372</pre>
325 <p> 373
374<p>
326 The first line summarizes whether the ebuild is okay or not. In the case of 375The first line summarizes whether the ebuild is okay or not. In the case of
327 <c>gnupg-1.0.7.ebuild</c>, it's not. Reading through the list of checks, we can see 376<c>gnupg-1.0.7.ebuild</c>, it's not. Reading through the list of checks, we can
328 that it got a warning for malformed headers and an error for presence of env 377see that it got a warning for malformed headers and an error for presence of env
329 vars. 378vars.
330 </p> 379</p>
331 380
332 <p> 381<p>
333 Looking at the ebuild, I see that it is missing a couple of required 382Looking at the ebuild, I see that it is missing a couple of required
334 env vars (LICENSE and RDEPEND). Adding those fixes the error. But there are 383env vars (LICENSE and RDEPEND). Adding those fixes the error. But there are
335 still two warnings -- one for malformed headers and one for env vars. To help 384still two warnings -- one for malformed headers and one for env vars. To help
336 me find those, I can run <c>lintool</c> again with <c>--show-details</c> 385me find those, I can run <c>lintool</c> again with <c>--show-details</c>
337 </p> 386</p>
387
338 <pre> 388<pre>
339hebron gnupg # <i>lintool --show-details ./gnupg-1.0.7.ebuild 389# <i>lintool --show-details ./gnupg-1.0.7.ebuild</i>
340 390
341------------------------------------------------------------------------------- 391-------------------------------------------------------------------------------
342# Some data cut for brevity.... 392# Some data cut for brevity....
343 393
344 Status for ./gnupg-1.0.7.ebuild 394 Status for ./gnupg-1.0.7.ebuild
345* Testing for malformed headers : passed 395* Testing for malformed headers : passed
367 Testing for presence of env vars : 0 / 1 417 Testing for presence of env vars : 0 / 1
368 Testing for sane USE flag usage : 0 / 0 418 Testing for sane USE flag usage : 0 / 0
369 419
370 Total number of ebuilds with errors : 0 (0%) 420 Total number of ebuilds with errors : 0 (0%)
371 Total number of ebuilds with warnings : 1 (100%) 421 Total number of ebuilds with warnings : 1 (100%)
372 </i> </pre> 422</pre>
423
424<p>
373 <p>Now I can see that the year in the ebuild is probably wrong, and that it is 425Now I can see that the year in the ebuild is probably wrong, and that it is
374 missing the SLOT variable. Fixing those eliminates all warnings.</p> 426missing the SLOT variable. Fixing those eliminates all warnings.
427</p>
375 428
376 </body> 429</body>
377 </section> 430</section>
378</chapter> 431</chapter>
432
379<chapter> 433<chapter>
380
381 <title>epm</title> 434<title>epm</title>
382 <section> 435<section>
383 <title>Introduction</title> 436<title>Introduction</title>
384 <body> 437<body>
385 <p> 438
439<p>
386 <c>epm</c> is a package managing tool that clones Red Hat rpm commands. As it stands 440<c>epm</c> is a package managing tool that clones Red Hat rpm commands. As it
387 now, it does not offer all of the features of rpm, but it offers some of the more 441stands now, it does not offer all of the features of rpm, but it offers some of
388 powerful rpm query options. 442the more powerful rpm query options.
389 </p> 443</p>
390 444
391 <p> 445<p>
392 It also handles removing packages, which is not covered here. Use <c>epm --help</c> 446It also handles removing packages, which is not covered here. Use <c>epm
393 to learn more about deleting packages with <c>epm</c>. 447--help</c> to learn more about deleting packages with <c>epm</c>.
394 </p> 448</p>
449
395 </body> 450</body>
396 </section> 451</section>
397 <section> 452<section>
398 453
399 <title>Querying Packages with epm</title> 454<title>Querying Packages with epm</title>
400 <body> 455<body>
401 <p> 456
457<p>
402 <c>epm</c> functions with essentially the same command line functions as Red Hat's 458<c>epm</c> functions with essentially the same command line functions as Red
403 rpm. <c>epm -qa</c> lists all packages installed. <c>epm -ql</c> lists all the 459Hat's rpm. <c>epm -qa</c> lists all packages installed. <c>epm -ql</c> lists all
404 files from a specific ebuild. 460the files from a specific ebuild.
405 </p> 461</p>
406 462
407 <pre> 463<pre>
408hebron etc # <i>epm -ql ethereal 464# <i>epm -ql ethereal</i>
409/usr/lib/ethereal/plugins/0.8.20/gryphon.so 465/usr/lib/ethereal/plugins/0.8.20/gryphon.so
410/usr/lib/ethereal/plugins/0.8.20/gryphon.la 466/usr/lib/ethereal/plugins/0.8.20/gryphon.la
411/usr/lib/ethereal/plugins/0.8.20/gryphon.a 467/usr/lib/ethereal/plugins/0.8.20/gryphon.a
412/usr/lib/ethereal/plugins/0.8.20/mgcp.so 468/usr/lib/ethereal/plugins/0.8.20/mgcp.so
413/usr/lib/ethereal/plugins/0.8.20/mgcp.la 469/usr/lib/ethereal/plugins/0.8.20/mgcp.la
443/usr/share/doc/ethereal-0.8.20/README.irix.gz 499/usr/share/doc/ethereal-0.8.20/README.irix.gz
444/usr/share/doc/ethereal-0.8.20/README.linux.gz 500/usr/share/doc/ethereal-0.8.20/README.linux.gz
445/usr/share/doc/ethereal-0.8.20/README.tru64.gz 501/usr/share/doc/ethereal-0.8.20/README.tru64.gz
446/usr/share/doc/ethereal-0.8.20/README.win32.gz 502/usr/share/doc/ethereal-0.8.20/README.win32.gz
447/usr/share/doc/ethereal-0.8.20/README.vmware.gz 503/usr/share/doc/ethereal-0.8.20/README.vmware.gz
448/etc/ethereal/manuf </i>
449 </pre>
450 <p>
451 <c>epm</c> offers a few advanced query options that are not present in <c>qpkg</c>
452at the
453 time of this writing. For instance, it can query for just configuration files or
454just documentation
455 files.
456 </p>
457 <pre>
458
459hebron etc # <i>epm -qc ethereal
460/etc/ethereal/manuf 504/etc/ethereal/manuf
505</pre>
461 506
462hebron etc # epm -qd ethereal 507<p>
508<c>epm</c> offers a few advanced query options that are not present in
509<c>qpkg</c> at the time of this writing. For instance, it can query for just
510configuration files or just documentation files.
511</p>
512
513<pre>
514# <i>epm -qc ethereal</i>
515/etc/ethereal/manuf
516
517# <i>epm -qd ethereal</i>
463/usr/share/man/man1/idl2eth.1.gz 518/usr/share/man/man1/idl2eth.1.gz
464/usr/share/man/man1/tethereal.1.gz 519/usr/share/man/man1/tethereal.1.gz
465/usr/share/man/man1/text2pcap.1.gz 520/usr/share/man/man1/text2pcap.1.gz
466/usr/share/man/man1/editcap.1.gz 521/usr/share/man/man1/editcap.1.gz
467/usr/share/man/man1/ethereal.1.gz 522/usr/share/man/man1/ethereal.1.gz
479/usr/share/doc/ethereal-0.8.20/README.irix.gz 534/usr/share/doc/ethereal-0.8.20/README.irix.gz
480/usr/share/doc/ethereal-0.8.20/README.linux.gz 535/usr/share/doc/ethereal-0.8.20/README.linux.gz
481/usr/share/doc/ethereal-0.8.20/README.tru64.gz 536/usr/share/doc/ethereal-0.8.20/README.tru64.gz
482/usr/share/doc/ethereal-0.8.20/README.win32.gz 537/usr/share/doc/ethereal-0.8.20/README.win32.gz
483/usr/share/doc/ethereal-0.8.20/README.vmware.gz 538/usr/share/doc/ethereal-0.8.20/README.vmware.gz
484 </i> </pre> 539</pre>
540
485 <note> 541<note>
486 <c>emp --help</c> lists the options that epm <e>will eventually</e> support. Note, 542<c>epm --help</c> lists the options that epm <e>will eventually</e> support.
487however, that
488 options prefixed with asterisks (*) are not yet implemented. 543Note, however, that options prefixed with asterisks (*) are not yet implemented.
489 </note> 544</note>
545
490 </body> 546</body>
491 </section> 547</section>
492</chapter> 548</chapter>
493 549
494<chapter> 550<chapter>
495 <title>Others</title> 551<title>Others</title>
496 <section> 552<section>
497 <title>etc-update</title> 553<title>etc-update</title>
498 <body> 554<body>
499 <!-- 555<!--
500 - Feel free to add more to this. It probably deserves its own chapter, but I don't 556- Feel free to add more to this. It probably deserves its own chapter, but I don't
501 - use it, so I can't really write much about it. 557- use it, so I can't really write much about it.
502 --> 558-->
503 <p> 559
560<p>
504 <c>etc-update</c> provides a convenient alternative to updating configuration 561<c>etc-update</c> provides a convenient alternative to updating configuration
505 files by hand. After running an emerge that changes configuration files, you 562files by hand. After running an emerge that changes configuration files, you
506 can run etc-update to step you through the process of updating all impacted 563can run etc-update to step you through the process of updating all impacted
507 configuration files. 564configuration files.
508 </p> 565</p>
509 566
510 <p> 567<p>
511 It is driven by a menu-based interface and includes the ability to view and merge 568It is driven by a menu-based interface and includes the ability to view and
512 in config files before deciding what to do. 569merge in config files before deciding what to do.
513 </p> 570</p>
571
514 </body> 572</body>
515 </section> 573</section>
574
516 <section> 575<section>
517 <title>gentool</title> 576<title>gentool</title>
518 <body> 577<body>
578
579<p>
519 <p>gentool is a collective name for several small scripts that analyze ebuild 580gentool is a collective name for several small scripts that analyze ebuild
520statistics. 581statistics.
521 For instance, gentool-total-coverage prints a list of email addresses and the 582For instance, gentool-total-coverage prints a list of email addresses and the
522 number of ebuilds each has in the portage tree. 583number of ebuilds each has in the portage tree.
523 </p> 584</p>
524 585
525 </body> 586</body>
526 </section> 587</section>
588
527 <section> 589<section>
528 <title>pkg-size</title> 590<title>pkg-size</title>
529 <body> 591<body>
592
593<p>
530 <p><c>pkg-size</c> prints the size of the installed files in a given package. 594<c>pkg-size</c> prints the size of the installed files in a given package.
531 </p> 595</p>
596
532 <pre> 597<pre>
533 598# <i>pkg-size nmap</i>
534hebron portage # <i>pkg-size nmap
535net-analyzer/nmap-2.54_beta24-r1 897024 (876KB) </i> 599net-analyzer/nmap-2.54_beta24-r1 897024 (876KB)
536 </pre> 600</pre>
601
537 </body> 602</body>
538 </section> 603</section>
604
539 <section> 605<section>
540 <title>mkebuild</title> 606<title>mkebuild</title>
541 <body> 607<body>
608
609<p>
542 <p><c>mkebuild</c> simplifies the process of creating a new ebuild by automating as 610<c>mkebuild</c> simplifies the process of creating a new ebuild by automating as
543much
544 of the process as possible. Running <c>mkebuild [filename]</c> will create an 611much of the process as possible. Running <c>mkebuild [filename]</c> will create
545 ebuild for that file. the file should be an archive of some kind. As it works, it 612an ebuild for that file. the file should be an archive of some kind. As it
546 will provide
547 feedback about changes you may need to make. 613works, it will provide feedback about changes you may need to make.
548 </p> 614</p>
549 615
550 </body> 616</body>
551 </section> 617</section>
618
552 <section> 619<section>
553 <title>emerge-webrsync</title> 620<title>emerge-webrsync</title>
554 <body> 621<body>
555 <!-- Can't find any documentation on this anywhere... not even a comment in the 622<!-- Can't find any documentation on this anywhere... not even a comment in the
556code. --> 623code. -->
624
625<p>
557 <p>Downloads the daily snapshot over HTTP with wget, and (optionally) syncs with 626Downloads the daily snapshot over HTTP with wget, and (optionally) syncs with
558portage. 627portage.
559 </p> 628</p>
629
560 </body> 630</body>
561
562 </section> 631</section>
563</chapter> 632</chapter>
564</guide> 633</guide>
565

Legend:
Removed from v.1.5  
changed lines
  Added in v.1.10

  ViewVC Help
Powered by ViewVC 1.1.20