/[gentoo]/xml/htdocs/doc/en/handbook/hb-working-portage.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-working-portage.xml

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

Revision 1.40 Revision 1.61
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.40 2004/10/21 16:34:46 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.61 2006/11/12 21:28:30 nightmorph Exp $ -->
8 8
9<sections> 9<sections>
10
11<abstract>
12This chapter explains the "simple" steps a user definitely needs to know to
13maintain the software on his system.
14</abstract>
15
16<version>1.55</version>
17<date>2006-11-12</date>
18
10<section> 19<section>
11<title>Welcome to Portage</title> 20<title>Welcome to Portage</title>
12<body> 21<body>
13 22
14<p> 23<p>
62<title>Updating the Portage Tree</title> 71<title>Updating the Portage Tree</title>
63<body> 72<body>
64 73
65<p> 74<p>
66The Portage tree is usually updated with <uri 75The Portage tree is usually updated with <uri
67link="http://rsync.gentoo.org">rsync</uri>, a fast incremental file transfer 76link="http://rsync.samba.org/">rsync</uri>, a fast incremental file transfer
68utility. Updating is fairly simple as the <c>emerge</c> command provides a 77utility. Updating is fairly simple as the <c>emerge</c> command provides a
69front-end for rsync: 78front-end for rsync:
70</p> 79</p>
71 80
72<pre caption="Updating the Portage tree"> 81<pre caption="Updating the Portage tree">
93<title>Searching for Software</title> 102<title>Searching for Software</title>
94<body> 103<body>
95 104
96<p> 105<p>
97To search through the Portage tree after software titles, you can use 106To search through the Portage tree after software titles, you can use
98<c>emerge</c> built-in search capabilities. By default, <c>emerge search</c> 107<c>emerge</c> built-in search capabilities. By default, <c>emerge --search</c>
99returns package names whos title corresponds with (either fully or partially) 108returns the names of packages whose title matches (either fully or partially)
100the given search term. 109the given search term.
101</p> 110</p>
102 111
103<p> 112<p>
104For instance, to search for all packages who have "pdf" in their name: 113For instance, to search for all packages who have "pdf" in their name:
105</p> 114</p>
106 115
107<pre caption="Searching for pdf-named packages"> 116<pre caption="Searching for pdf-named packages">
108$ <i>emerge search pdf</i> 117$ <i>emerge --search pdf</i>
109</pre> 118</pre>
110 119
111<p> 120<p>
112If you want to search through the descriptions as well you can use the 121If you want to search through the descriptions as well you can use the
113<c>--searchdesc</c> (or <c>-S</c>) switch: 122<c>--searchdesc</c> (or <c>-S</c>) switch:
121When you take a look at the output, you'll notice that it gives you a lot of 130When you take a look at the output, you'll notice that it gives you a lot of
122information. The fields are clearly labelled so we won't go further into their 131information. The fields are clearly labelled so we won't go further into their
123meanings: 132meanings:
124</p> 133</p>
125 134
126<pre caption="Example emerge search output"> 135<pre caption="Example 'emerge --search' output">
127* net-print/cups-pdf 136* net-print/cups-pdf
128 Latest version available: 1.5.2 137 Latest version available: 1.5.2
129 Latest version installed: [ Not Installed ] 138 Latest version installed: [ Not Installed ]
130 Size of downloaded files: 15 kB 139 Size of downloaded files: 15 kB
131 Homepage: http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/ 140 Homepage: http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/
174</pre> 183</pre>
175 184
176</body> 185</body>
177</subsection> 186</subsection>
178<subsection> 187<subsection>
188<title>Finding Installed Package Documentation</title>
189<body>
190
191<p>
192Many packages come with their own documentation. Sometimes, the <c>doc</c> USE
193flag determines whether the package documentation should be installed or not.
194You can check the existence of a <c>doc</c> USE flag with the <c>emerge -vp
195&lt;package name&gt;</c> command.
196</p>
197
198<pre caption="Checking the existence of a doc USE flag">
199<comment>(alsa-lib is just an example, of course.)</comment>
200# <i>emerge -vp alsa-lib</i>
201[ebuild N ] media-libs/alsa-lib-1.0.9_rc3 +doc -jack 674 kB
202</pre>
203
204<p>
205You can enable or disable the <c>doc</c> USE flag either globally in the
206<path>/etc/make.conf</path> file or per package in the
207<path>/etc/portage/package.use</path> file. You can also create a directory
208called <path>/etc/portage/package.use</path> and list it in a file inside this
209directory. The <uri
210link="?part=2&amp;chap=2">USE Flags</uri> chapter covers this aspect in detail.
211</p>
212
213<p>
214Once the package installed, its documentation is generally found in a
215subdirectory named after the package under the <path>/usr/share/doc</path>
216directory. You can also list all installed files with the <c>equery</c> tool
217which is part of the <c>app-portage/gentoolkit</c> <uri
218link="/doc/en/gentoolkit.xml">package</uri>.
219</p>
220
221<pre caption="Locating package documentation">
222# <i>ls -l /usr/share/doc/alsa-lib-1.0.9_rc3</i>
223total 28
224-rw-r--r-- 1 root root 669 May 17 21:54 ChangeLog.gz
225-rw-r--r-- 1 root root 9373 May 17 21:54 COPYING.gz
226drwxr-xr-x 2 root root 8560 May 17 21:54 html
227-rw-r--r-- 1 root root 196 May 17 21:54 TODO.gz
228
229<comment>(Alternatively, use equery to locate interesting files:)</comment>
230# <i>equery files alsa-lib | less</i>
231media-libs/alsa-lib-1.0.9_rc3
232* Contents of media-libs/alsa-lib-1.0.9_rc3:
233/usr
234/usr/bin
235/usr/bin/alsalisp
236<comment>(Output truncated)</comment>
237</pre>
238
239</body>
240</subsection>
241<subsection>
179<title>Removing Software</title> 242<title>Removing Software</title>
180<body> 243<body>
181 244
182<p> 245<p>
183When you want to remove a software package from your system, use <c>emerge 246When you want to remove a software package from your system, use <c>emerge
184unmerge</c>. This will tell Portage to remove all files installed by that 247--unmerge</c>. This will tell Portage to remove all files installed by that
185package from your system <e>except</e> the configuration files of that 248package from your system <e>except</e> the configuration files of that
186application if you have altered those after the installation. Leaving the 249application if you have altered those after the installation. Leaving the
187configuration files allows you to continue working with the package if you ever 250configuration files allows you to continue working with the package if you ever
188decide to install it again. 251decide to install it again.
189</p> 252</p>
194warn you when you want to remove an important package that breaks your system 257warn you when you want to remove an important package that breaks your system
195if you unmerge it. 258if you unmerge it.
196</p> 259</p>
197 260
198<pre caption="Removing gnumeric from the system"> 261<pre caption="Removing gnumeric from the system">
199# <i>emerge unmerge gnumeric</i> 262# <i>emerge --unmerge gnumeric</i>
200</pre> 263</pre>
201 264
202<p> 265<p>
203When you remove a package from your system, the dependencies of that package 266When you remove a package from your system, the dependencies of that package
204that were installed automatically when you installed the software are left. To 267that were installed automatically when you installed the software are left. To
205have Portage locate all dependencies that can now be removed, use 268have Portage locate all dependencies that can now be removed, use
206<c>emerge</c>'s <c>depclean</c> functionality. We will talk about this later on. 269<c>emerge</c>'s <c>--depclean</c> functionality. We will talk about this later
270on.
207</p> 271</p>
208 272
209</body> 273</body>
210</subsection> 274</subsection>
211<subsection> 275<subsection>
215<p> 279<p>
216To keep your system in perfect shape (and not to mention install the latest 280To keep your system in perfect shape (and not to mention install the latest
217security updates) you need to update your system regularly. Since Portage only 281security updates) you need to update your system regularly. Since Portage only
218checks the ebuilds in your Portage tree you first have to update your Portage 282checks the ebuilds in your Portage tree you first have to update your Portage
219tree. When your Portage tree is updated, you can update your system with 283tree. When your Portage tree is updated, you can update your system with
220<c>emerge --update world</c>: 284<c>emerge --update world</c>. In the next example, we'll also use the
285<c>--ask</c> switch which will tell Portage to display the list of packages it
286wants to upgrade and ask you if you want to continue:
221</p> 287</p>
222 288
223<pre caption="Updating your system"> 289<pre caption="Updating your system">
224# <i>emerge --update world</i> 290# <i>emerge --update --ask world</i>
225</pre> 291</pre>
226 292
227<p> 293<p>
228Portage will then search for newer version of the applications you have 294Portage will then search for newer version of the applications you have
229installed. However, it will only verify the versions for the applications you 295installed. However, it will only verify the versions for the applications you
230have explicitly installed - not the dependencies. If you want to update every 296have <e>explicitly</e> installed (the applications listed in
231single package on your system, add the <c>--deep</c> argument: 297<path>/var/lib/portage/world</path>) - it does not thoroughly check their
298dependencies. If you want to update <e>every single package</e> on your system,
299add the <c>--deep</c> argument:
232</p> 300</p>
233 301
234<pre caption="Updating your entire system"> 302<pre caption="Updating your entire system">
235# <i>emerge --update --deep world</i> 303# <i>emerge --update --deep world</i>
236</pre> 304</pre>
305
306<p>
307Since security updates also happen in packages you have not explicitly installed
308on your system (but that are pulled in as dependencies of other programs), it
309is recommended to run this command once in a while.
310</p>
237 311
238<p> 312<p>
239If you have altered any of your <uri link="?part=2&amp;chap=2">USE flags</uri> 313If you have altered any of your <uri link="?part=2&amp;chap=2">USE flags</uri>
240lately you might want to add <c>--newuse</c> as well. Portage will then verify 314lately you might want to add <c>--newuse</c> as well. Portage will then verify
241if the change requires the installation of new packages or recompilation of 315if the change requires the installation of new packages or recompilation of
247</pre> 321</pre>
248 322
249</body> 323</body>
250</subsection> 324</subsection>
251<subsection> 325<subsection>
252<title>Stub Packages</title> 326<title>Metapackages</title>
253<body> 327<body>
254 328
255<p> 329<p>
256Some packages in the Portage tree don't have any real content but are used to 330Some packages in the Portage tree don't have any real content but are used to
257install a collection of packages. For instance, the <c>kde</c> package will 331install a collection of packages. For instance, the <c>kde</c> package will
259KDE-related packages as dependencies. 333KDE-related packages as dependencies.
260</p> 334</p>
261 335
262<p> 336<p>
263If you ever want to remove such a package from your system, running <c>emerge 337If you ever want to remove such a package from your system, running <c>emerge
264unmerge</c> on the package won't have much effect as the dependencies remain on 338--unmerge</c> on the package won't have much effect as the dependencies remain
265the system. 339on the system.
266</p> 340</p>
267 341
268<p> 342<p>
269Portage has the functionality to remove orphaned dependencies as well, but since 343Portage has the functionality to remove orphaned dependencies as well, but since
270the availability of software is dynamically dependent you first need to update 344the availability of software is dynamically dependent you first need to update
271your entire system fully, including the new changes you applied when changing 345your entire system fully, including the new changes you applied when changing
272USE flags. After this you can run <c>emerge depclean</c> to remove the orphaned 346USE flags. After this you can run <c>emerge --depclean</c> to remove the
273dependencies. When this is done, you need to rebuild the applications that were 347orphaned dependencies. When this is done, you need to rebuild the applications
274dynamically linked to the now-removed software titles but don't require them 348that were dynamically linked to the now-removed software titles but don't
275anymore. 349require them anymore.
276</p> 350</p>
277 351
278<p> 352<p>
279All this is handled with the following three commands: 353All this is handled with the following three commands:
280</p> 354</p>
281 355
282<pre caption="Removing orphaned dependencies"> 356<pre caption="Removing orphaned dependencies">
283# <i>emerge --update --deep --newuse world</i> 357# <i>emerge --update --deep --newuse world</i>
284# <i>emerge depclean</i> 358# <i>emerge --depclean</i>
285# <i>revdep-rebuild</i> 359# <i>revdep-rebuild</i>
286</pre> 360</pre>
287 361
288<p> 362<p>
289<c>revdep-rebuild</c> is provided by the <c>gentoolkit</c> package; don't forget 363<c>revdep-rebuild</c> is provided by the <c>gentoolkit</c> package; don't forget
304<body> 378<body>
305 379
306<p> 380<p>
307As we stated before, Portage is extremely powerful and supports many features 381As we stated before, Portage is extremely powerful and supports many features
308that other software management tools lack. To understand this, we explain a few 382that other software management tools lack. To understand this, we explain a few
309aspects of Portage without going in too much detail. 383aspects of Portage without going into too much detail.
310</p> 384</p>
311 385
312<p> 386<p>
313With Portage different versions of a single package can coexist on a system. 387With Portage different versions of a single package can coexist on a system.
314While other distributions tend to name their package to those versions (like 388While other distributions tend to name their package to those versions (like
355<subsection id="blocked"> 429<subsection id="blocked">
356<title>Blocked Packages</title> 430<title>Blocked Packages</title>
357<body> 431<body>
358 432
359<pre caption="Portage warning about blocked packages (with --pretend)"> 433<pre caption="Portage warning about blocked packages (with --pretend)">
360[blocks B ] gnome-base/bonobo-activation (from pkg gnome-base/libbonobo-2.4.0) 434[blocks B ] mail-mta/ssmtp (is blocking mail-mta/postfix-2.2.2-r1)
361</pre> 435</pre>
362 436
363<pre caption="Portage warning about blocked packages (without --pretend)"> 437<pre caption="Portage warning about blocked packages (without --pretend)">
364!!! Error: the gnome-base/bonobo-activation package conflicts with another package. 438!!! Error: the mail-mta/postfix package conflicts with another package.
365!!! both can't be installed on the same system together. 439!!! both can't be installed on the same system together.
366!!! Please use 'emerge --pretend' to determine blockers. 440!!! Please use 'emerge --pretend' to determine blockers.
367</pre> 441</pre>
368 442
369<p> 443<p>
370Ebuilds contain specific fields that inform Portage about it's dependencies. 444Ebuilds contain specific fields that inform Portage about its dependencies.
371There are two possible dependencies: build dependencies, declared in 445There are two possible dependencies: build dependencies, declared in
372<c>DEPEND</c> and run-time dependencies, declared in <c>RDEPEND</c>. When one of 446<c>DEPEND</c> and run-time dependencies, declared in <c>RDEPEND</c>. When one of
373these dependencies explicitly marks a package or virtual as being <e>not</e> 447these dependencies explicitly marks a package or virtual as being <e>not</e>
374compatible, it triggers a blockage. 448compatible, it triggers a blockage.
375</p> 449</p>
376 450
377<p> 451<p>
378To fix a blockage, you can choose to not install the package or unmerge the 452To fix a blockage, you can choose to not install the package or unmerge the
379conflicting package first. In the given example, you can opt not to install 453conflicting package first. In the given example, you can opt not to install
380<c>libbonobo</c> or to remove <c>bonobo-activation</c> first. 454<c>postfix</c> or to remove <c>ssmtp</c> first.
455</p>
456
457<p>
458It is also possible that two packages that are yet to be installed are blocking
459each other. In this rare case, you should find out why you need to install both.
460In most cases you can do with one of the packages alone. If not, please file a
461bug on <uri link="http://bugs.gentoo.org">Gentoo's bugtracking system</uri>.
381</p> 462</p>
382 463
383</body> 464</body>
384</subsection> 465</subsection>
385<subsection id="masked"> 466<subsection id="masked">
440<subsection id="missingdependencies"> 521<subsection id="missingdependencies">
441<title>Missing Dependencies</title> 522<title>Missing Dependencies</title>
442<body> 523<body>
443 524
444<pre caption="Portage warning about missing dependency"> 525<pre caption="Portage warning about missing dependency">
445emerge: there are no ebuilds to satisfy "&gt;=sys-devel/gcc-4.2-r4". 526emerge: there are no ebuilds to satisfy "&gt;=sys-devel/gcc-3.4.2-r4".
446 527
447!!! Problem with ebuild sys-devel/gcc-3.4.2-r2 528!!! Problem with ebuild sys-devel/gcc-3.4.2-r2
448!!! Possibly a DEPEND/*DEPEND problem. 529!!! Possibly a DEPEND/*DEPEND problem.
449</pre> 530</pre>
450 531
538from the system. 619from the system.
539</p> 620</p>
540 621
541</body> 622</body>
542</subsection> 623</subsection>
624<subsection id="digesterror">
625<title>Digest Verification Failures</title>
626<body>
627
628<p>
629Sometimes, when you attempt to emerge a package, it will fail with the message:
630</p>
631
632<pre caption="Digest verification failure">
633&gt;&gt;&gt; checking ebuild checksums
634!!! Digest verification failed:
635</pre>
636
637<p>
638This is a sign that something is wrong with the Portage tree -- often, it is
639because a developer may have made a mistake when committing a package to the
640tree.
641</p>
642
643<p>
644When the digest verification fails, do <e>not</e> try to re-digest the package
645yourself. Running <c>ebuild foo digest</c> will not fix the problem; it will
646almost certainly make it worse!
647</p>
648
649<p>
650Instead, wait an hour or two for the tree to settle down. It's likely that the
651error was noticed right away, but it can take a little time for the fix to
652trickle down the Portage tree. While you're waiting, check <uri
653link="http://bugs.gentoo.org">Bugzilla</uri> and see if anyone has reported
654the problem yet. If not, go ahead and file a bug for the broken package.
655</p>
656
657<p>
658Once you see that the bug has been fixed, you may want to re-sync to pick up
659the fixed digest.
660</p>
661
662<impo>
663This does <e>not</e> mean that you can re-sync your tree multiple times! As
664stated in the rsync policy (when you run <c>emerge --sync</c>), users who sync
665too often will be banned! In fact, it's better to just wait until your next
666scheduled sync, so that you don't overload the rsync servers.
667</impo>
668
669</body>
670</subsection>
543</section> 671</section>
544</sections> 672</sections>

Legend:
Removed from v.1.40  
changed lines
  Added in v.1.61

  ViewVC Help
Powered by ViewVC 1.1.20