/[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.13 Revision 1.66
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
1<!-- 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 -->
2<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
3 6
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.13 2003/12/04 22:26:19 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.66 2007/11/01 01:02:41 yoswink Exp $ -->
5 8
6<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.60</version>
17<date>2007-11-01</date>
18
7<section> 19<section>
8<title>Obtaining Package Information</title> 20<title>Welcome to Portage</title>
9<subsection>
10<title>The Lord of All Tools: emerge</title>
11<body> 21<body>
12 22
13<p>
14The main Portage tool that most users will use is <c>emerge</c>. We have already
15used it during the Gentoo installation and in the previous chapter, but we just
16briefly explained how to use it. This chapter will elaborate on <c>emerge</c>
17and teach you how to use <c>emerge</c> to fix all your software-related needs.
18</p> 23<p>
19 24Portage is probably Gentoo's most notable innovation in software management.
25With its high flexibility and enormous amount of features it is frequently seen
26as the best software management tool available for Linux.
20<p> 27</p>
21<c>emerge</c> is the command used to install, remove, query and maintain 28
22software packages. It is a front-end for <c>ebuild</c>; people interested in
23becoming Gentoo professionals will learn how to use <c>ebuild</c> later on. For
24now, we will focus on <c>emerge</c> as it has functionality that <c>ebuild</c>
25lacks (such as resolving dependencies, searching the Portage tree, etc.).
26</p> 29<p>
27 30Portage is completely written in <uri link="http://www.python.org">Python</uri>
31and <uri link="http://www.gnu.org/software/bash">Bash</uri> and therefore fully
32visible to the users as both are scripting languages.
28<p> 33</p>
29Since <c>emerge</c> is the most important tool for Gentoo users, it has an 34
30extensive manpage you can read by issuing <c>man emerge</c>. You can also view
31the in-command help by running <c>emerge --help</c>.
32</p> 35<p>
36Most users will work with Portage through the <c>emerge</c> tool. This chapter
37is not meant to duplicate the information available from the emerge man page.
38For a complete rundown of emerge's options, please consult the man page:
39</p>
33 40
34<pre caption="Retrieving help for emerge"> 41<pre caption="Reading the emerge man page">
35# <i>man emerge</i> 42$ <i>man emerge</i>
36# <i>emerge --help</i>
37</pre> 43</pre>
38 44
39</body>
40</subsection>
41<subsection>
42<title>The Portage Tree</title>
43<body> 45</body>
44
45<p>
46Before we continue describing <c>emerge</c>, let us first take a look at the
47Portage Tree. Go to <path>/usr/portage</path> and do a listing of the available
48directories. We use <c>ls --classify</c> to list the contents of a
49directory as it will show directories with a trailing "/".
50</p>
51
52<pre caption="Viewing the Portage Tree">
53# <i>cd /usr/portage; ls --classify</i>
54app-admin/ dev-ml/ gnome-libs/ net-print/
55app-arch/ dev-perl/ gnome-office/ net-wireless/
56app-benchmarks/ dev-php/ header.txt net-www/
57app-cdr/ dev-python/ incoming/ net-zope/
58app-crypt/ dev-ruby/ jython/ packages/
59app-dicts/ dev-tcltk/ kde-apps/ profiles/
60app-doc/ dev-tex/ kde-base/ releases/
61app-editors/ dev-util/ kde-i18n/ scripts/
62app-emacs/ distfiles/ kde-libs/ sec-policy/
63app-emulation/ eclass/ licenses/ skel.ChangeLog
64app-games/ experimental/ media-fonts/ skel.ebuild
65app-gnustep/ files/ media-gfx/ skel.metadata.xml
66app-i18n/ fresco-base/ media-libs/ snapshots/
67app-misc/ games-action/ media-plugins/ sys-apps/
68app-office/ games-arcade/ media-radio/ sys-build/
69app-pda/ games-board/ media-sound/ sys-cluster/
70app-portage/ games-emulation/ media-tv/ sys-devel/
71app-sci/ games-engines/ media-video/ sys-fs/
72app-shells/ games-fps/ metadata/ sys-kernel/
73app-text/ games-kids/ net-analyzer/ sys-kmods/
74app-vim/ games-misc/ net-apache/ sys-libs/
75app-xemacs/ games-mud/ net-dialup/ unix2tcp/
76berlin-base/ games-puzzle/ net-dns/ x11-base/
77dev-ada/ games-roguelike/ net-firewall/ x11-libs/
78dev-cpp/ games-rpg/ net-fs/ x11-misc/
79dev-db/ games-server/ net-ftp/ x11-plugins/
80dev-dotnet/ games-simulation/ net-im/ x11-terms/
81dev-embedded/ games-sports/ net-irc/ x11-themes/
82dev-games/ games-strategy/ net-libs/ x11-wm/
83dev-haskell/ games-util/ net-mail/ xfce-base/
84dev-java/ glep/ net-misc/ xfce-extra/
85dev-lang/ gnome-apps/ net-nds/
86dev-libs/ gnome-base/ net-news/
87dev-lisp/ gnome-extra/ net-p2p/
88</pre>
89
90<p>
91As you can see, the Portage tree has several subdirectories. Most of them are
92the <e>categories</e> in which the Gentoo packages, called <e>ebuilds</e>,
93reside. Take a look at, for instance, <path>app-office</path>:
94</p>
95
96<pre caption="Viewing a category">
97# <i>cd app-office; ls --classify</i>
98abiword/ gnotime/ kmymoney2/ ooodi/ plan/ timestamp.x
99dia/ gnucash/ koffice/ oooqs/ qhacc/
100dia2code/ gnumeric/ lxbank/ openoffice/ sc/
101facturalux/ ical/ lyx/ openoffice-bin/ scribus/
102gaby/ kbudget/ mdbtools/ openoffice-ximian/ siag/
103gnofin/ khacc/ mrproject/ phprojekt/ texmacs/
104</pre>
105
106<p>
107Inside a category you will find the packages belonging to that category, with a
108separate directory for each package. Let us take a look at the <c>openoffice</c>
109package:
110</p>
111
112<pre caption="Viewing a package">
113# <i>cd openoffice; ls --classify</i>
114ChangeLog files/ openoffice-1.0.3-r1.ebuild openoffice-1.1.0-r2.ebuild
115Manifest metadata.xml openoffice-1.1.0-r1.ebuild openoffice-1.1.0.ebuild
116</pre>
117
118<p>
119Remember that we told you that a Gentoo package is called an ebuild? Well, in
120the example directory four of such ebuilds are stored. Their naming is
121almost identical: they only differ in the version name.
122You are free to view the contents of such a package: they are plain scripts. We
123will not discuss it right now as it isn't important to know if you plan on just
124using Gentoo.
125</p>
126
127<p>
128The other files are the <path>ChangeLog</path> (which contains a listing of all
129the changes done to the ebuilds), <path>Manifest</path> (which contains the
130checksums and permissions of all the files in the directory) and
131<path>metadata.xml</path> (which contains more information about the package,
132such as the responsible development group -- called <e>herd</e> -- and a more
133extensive description).
134</p>
135
136<p>
137Inside the <path>files</path> directory you will find extra files, needed by
138Portage: digests (checksums and permissions of the files needed by a single
139version of the package), patches, example configuration files, etc.
140</p>
141
142<pre caption="Viewing the extra files">
143# <i>cd files; ls --classify</i>
1441.0.3/ digest-openoffice-1.0.3-r1 digest-openoffice-1.1.0-r1
1451.1.0/ digest-openoffice-1.1.0 digest-openoffice-1.1.0-r2
146# <i>cd 1.1.0; ls --classify</i>
147fixed-gcc.patch ooffice-wrapper-1.3
148newstlportfix.patch openoffice-1.1.0-linux-2.6-fix.patch
149no-mozab.patch openoffice-1.1.0-sparc64-fix.patch
150nptl.patch
151</pre>
152
153<p>
154If you go back to the root of the Portage tree (<path>/usr/portage</path>) you
155will notice that there are other, non-category directories too. We will discuss
156those later in this chapter.
157</p>
158
159</body>
160</subsection>
161<subsection>
162<title>Search for a Package</title>
163<body>
164
165<p>
166If you are new to Linux or Gentoo, you might not know what tool you need for
167what job. To facilitate searching, <c>emerge</c> provides you with a way to
168search through the available packages on your system. There are two ways you can
169search through packages: by <e>name</e>, or by <e>name</e> and
170<e>description</e>.
171</p>
172
173<p>
174To search through the Portage tree by name, use <c>emerge search</c>. For
175instance, to find out more about <c>mozilla</c>:
176</p>
177
178<pre caption="Showing information about mozilla">
179# <i>emerge search mozilla</i>
180Searching...
181[ Results for search key : mozilla ]
182[ Applications found : 5 ]
183<comment>(Some output removed to improve readability)</comment>
184* net-www/mozilla
185 Latest version available: 1.5-r1
186 Latest version installed: 1.4-r3
187 Size of downloaded files: 29,153 kB
188 Homepage: http://www.mozilla.org
189 Description: The Mozilla Web Browser
190
191* net-www/mozilla-firebird
192 Latest version available: 0.7
193 Latest version installed: [ Not Installed ]
194 Size of downloaded files: 37,850 kB
195 Homepage: http://www.mozilla.org/projects/firebird/
196 Description: The Mozilla Firebird Web Browser
197<comment>(...)</comment>
198</pre>
199
200<p>
201If you want to include a search through the descriptions too, use the
202<c>--searchdesc</c> argument:
203</p>
204
205<pre caption="Search through the descriptions too">
206# <i>emerge --searchdesc mozilla</i>
207Searching...
208[ Results for search key : mozilla ]
209[ Applications found : 10 ]
210<comment>(Some output removed to improve readability)</comment>
211* dev-libs/nss-3.8
212 Latest version available: 3.8
213 Latest version installed: 3.8
214 Size of downloaded files: 2,782 kB
215 Homepage: http://www.mozilla.org/projects/security/pki/nss/
216 Description: Mozilla's Netscape Security Services Library that implements PKI support
217</pre>
218
219<p>
220As you can see, the output of <c>emerge</c> informs you about the category and
221name of the package, the available version, the currently installed version,
222the size of the downloaded files, the homepage and the small description.
223</p>
224
225<p>
226You see something new? Yes, <e>downloaded files</e>. When you tell Portage to
227install a package, it of course needs to have the necessary sources (or
228precompiled packages) available. It therefore checks the contents of
229<path>/usr/portage/distfiles</path> (for sourcecode) or
230<path>/usr/portage/packages/All</path> (for precompiled packages) to see if the
231necessary files are already available. If not, it downloads the necessary files
232and places them in those directories.
233</p>
234
235<note>
236Searching the Portage Tree, especially when using <c>--searchdesc</c>, is very
237time consuming. There are other, more performant tools available. We will
238describe those in the chapter on <uri link="?part=2&amp;chap=7">Gentoolkit and
239Other Tools</uri>.
240</note>
241
242</body>
243</subsection>
244<subsection>
245<title>Viewing the ChangeLog</title>
246<body>
247
248<p>
249While browsing through the Portage Tree, you saw that there was a ChangeLog for
250each package. You can view this ChangeLog with <c>emerge</c> too. Use the
251<c>--pretend --changelog</c> (<c>-pl</c> in short) options. As an example we
252will view the ChangeLog entries for <c>gnumeric</c>:
253</p>
254
255<pre caption="Viewing the ChangeLog entries for gnumeric">
256# <i>emerge --pretend --changelog gnumeric</i>
257</pre>
258
259</body>
260</subsection>
261</section> 46</section>
262<section> 47<section>
263<title>Updating Portage</title> 48<title>The Portage Tree</title>
264<subsection>
265<title>Introduction</title>
266<body>
267
268<p>
269Searching through Portage is nice, but if you don't update your Portage Tree
270regularly, you will be stuck with the packages and versions available on your
271system. This means that your system will get outdated pretty soon and that
272you will be missing bugfixes and remedies for possible security problems.
273</p>
274
275<p>
276There are several ways to update your Portage Tree. The most popular method is
277by using one of our <uri link="/main/en/mirrors.xml">rsync mirrors</uri>.
278Another one is by using a Portage snapshot (in case a firewall or unavailability
279of a network prohibits the use of the rsync server).
280</p>
281
282</body>
283</subsection> 49<subsection>
50<title>Ebuilds</title>
51<body>
52
53<p>
54When we talk about packages, we often mean software titles that are available to
55the Gentoo users through the Portage tree. The Portage tree is a collection of
56<e>ebuilds</e>, files that contain all information Portage needs to maintain
57software (install, search, query, ...). These ebuilds reside in
58<path>/usr/portage</path> by default.
59</p>
60
61<p>
62Whenever you ask Portage to perform some action regarding software titles, it
63will use the ebuilds on your system as a base. It is therefore important that
64you regularly update the ebuilds on your system so Portage knows about new
65software, security updates, etc.
66</p>
67
68</body>
284<subsection> 69</subsection>
285<title>Selecting a Mirror for rsync</title>
286<body>
287
288<p>
289It is adviseable to first select a fast <uri
290link="/main/en/mirrors.xml">mirror</uri> close to you. You can do this manually
291(by setting the <c>SYNC</c> variable in <path>/etc/make.conf</path>) or use
292<c>mirrorselect</c> to do this for you automatically. As the <c>SYNC</c>
293variable will be discussed later on, we will focus on using <c>mirrorselect</c>.
294First install <c>mirrorselect</c> by emerging it:
295</p>
296
297<pre caption="Installing mirrorselect">
298# <i>emerge --usepkg mirrorselect</i>
299</pre>
300
301<p>
302Now run <c>mirrorselect</c> to automatically select mirrors for you (it will
303also setup Portage to use a mirror for the sourcecode):
304</p>
305
306<pre caption="Running mirrorselect">
307# <i>mirrorselect -a -s3</i>
308</pre>
309
310</body>
311</subsection> 70<subsection>
312<subsection>
313<title>Updating Portage</title> 71<title>Updating the Portage Tree</title>
314<body> 72<body>
315 73
316<p>
317To update Portage using rsync, simply run <c>emerge sync</c>:
318</p> 74<p>
75The Portage tree is usually updated with <uri
76link="http://rsync.samba.org/">rsync</uri>, a fast incremental file transfer
77utility. Updating is fairly simple as the <c>emerge</c> command provides a
78front-end for rsync:
79</p>
319 80
320<pre caption="Updating Portage using emerge sync"> 81<pre caption="Updating the Portage tree">
321# <i>emerge sync</i> 82# <i>emerge --sync</i>
322</pre> 83</pre>
323 84
324<p>
325If this fails (due to network problems, or a firewall), you can try using
326<c>emerge-webrsync</c> which will download a Portage Tree snapshot using
327<c>wget</c>. This also means that you can use proxies if you want. We discussed
328how to setup your system to use proxies during the Gentoo installation.
329</p> 85<p>
86If you are unable to rsync due to firewall restrictions you can still update
87your Portage tree by using our daily generated Portage tree snapshots. The
88<c>emerge-webrsync</c> tool automatically fetches and installs the latest
89snapshot on your system:
90</p>
330 91
331<pre caption="Updating Portage using emerge-webrsync"> 92<pre caption="Running emerge-webrsync">
332# <i>emerge-webrsync</i> 93# <i>emerge-webrsync</i>
333</pre> 94</pre>
334 95
335</body> 96</body>
336</subsection> 97</subsection>
337</section> 98</section>
338<section> 99<section>
339<title>Maintaining Software</title> 100<title>Maintaining Software</title>
340<subsection> 101<subsection>
341<title>Building or Prebuilt?</title> 102<title>Searching for Software</title>
342<body>
343
344<p>
345Gentoo provides ebuilds, the Gentoo packages if you like. But when you want to
346install such an ebuild, you can choose between <e>building</e> the package, or
347using a <e>prebuilt</e> package. But what are the advantages/disadvantages of
348both approaches, and can they be used next to each other?
349</p>
350
351<p>
352As you probably have guessed, building packages takes a lot of time (especially
353if you have little resources or want to build big packages, such as <uri
354link="http://www.kde.org">KDE</uri>, <uri
355link="http://www.openoffice.org">OpenOffice.org</uri>, etc.). By building the
356package, you can use the <c>USE</c> setting to tweak the package to your system.
357Of course, you can also define high optimization options (in the <c>CFLAGS</c>
358and <c>CXXFLAGS</c> variables) to compile the package with.
359</p>
360
361<p>
362Using prebuilt packages improves the installation time (as no more compilation
363is needed), but you will lose the advantages of the <c>USE</c> setting and the
364<c>CFLAGS</c> &amp; <c>CXXFLAGS</c> variables.
365</p>
366
367<p>
368As previously stated, prebuilt packages are stored in the
369<path>/usr/portage/packages/All</path> directory, while the sourcecode of the
370packages are placed in <path>/usr/portage/distfiles</path>. If you have finished
371installing a package you can remove the package or sourcecode from the
372respective directory. However, you might want to keep the package/sourcecode of
373the latest version, just in case you want to reinstall the package (so you don't
374have to redownload it).
375</p>
376
377</body> 103<body>
378</subsection> 104
105<p>
106To search through the Portage tree after software titles, you can use
107<c>emerge</c> built-in search capabilities. By default, <c>emerge --search</c>
108returns the names of packages whose title matches (either fully or partially)
109the given search term.
110</p>
111
112<p>
113For instance, to search for all packages who have "pdf" in their name:
114</p>
115
116<pre caption="Searching for pdf-named packages">
117$ <i>emerge --search pdf</i>
118</pre>
119
120<p>
121If you want to search through the descriptions as well you can use the
122<c>--searchdesc</c> (or <c>-S</c>) switch:
123</p>
124
125<pre caption="Searching for pdf-related packages">
126$ <i>emerge --searchdesc pdf</i>
127</pre>
128
129<p>
130When you take a look at the output, you'll notice that it gives you a lot of
131information. The fields are clearly labelled so we won't go further into their
132meanings:
133</p>
134
135<pre caption="Example 'emerge --search' output">
136* net-print/cups-pdf
137 Latest version available: 1.5.2
138 Latest version installed: [ Not Installed ]
139 Size of downloaded files: 15 kB
140 Homepage: http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/
141 Description: Provides a virtual printer for CUPS to produce PDF files.
142 License: GPL-2
143</pre>
144
145</body>
379<subsection> 146</subsection>
147<subsection>
380<title>Installing Software from Sources</title> 148<title>Installing Software</title>
381<body> 149<body>
382 150
383<p> 151<p>
384Okay, enough talking, let's cut to the chase. To install a package, you will use 152Once you've found a software title to your liking, you can easily install it
385the <c>emerge</c> command. If you don't want to use any prebuilt packages, you 153with <c>emerge</c>: just add the package name. For instance, to install
386can just use <c>emerge &lt;package-name&gt;</c> or <c>emerge
387&lt;category&gt;/&lt;package-name&gt;</c>. As an example we'll install
388<c>gnumeric</c>: 154<c>gnumeric</c>:
389</p> 155</p>
390 156
391<pre caption="Building gnumeric"> 157<pre caption="Installing gnumeric">
392# <i>emerge gnumeric</i> 158# <i>emerge gnumeric</i>
393</pre> 159</pre>
394 160
395<p> 161<p>
396This will download the sourcecode for you and unpacks, compiles and installs the 162Since many applications depend on each other, any attempt to install a certain
397package on your system. It will also do the same for all the dependencies. If 163software package might result in the installation of several dependencies as
398you want to see what dependencies will be installed with it, use the 164well. Don't worry, Portage handles dependencies well. If you want to find out
399<c>--pretend</c> option (<c>-p</c> in short): 165what Portage <e>would</e> install when you ask it to install a certain package,
166add the <c>--pretend</c> switch. For instance:
400</p> 167</p>
401 168
402<pre caption="Pretending to build gnumeric"> 169<pre caption="Pretend to install gnumeric">
403# <i>emerge --pretend gnumeric</i> 170# <i>emerge --pretend gnumeric</i>
404</pre> 171</pre>
405 172
406<p> 173<p>
407If you want to download the sourcecode of the package and its dependencies, 174When you ask Portage to install a package, it will download the necessary source
408but don't want to build the package, use the <c>--fetchonly</c> option 175code from the internet (if necessary) and store it by default in
409(<c>-f</c> in short): 176<path>/usr/portage/distfiles</path>. After this it will unpack, compile and
177install the package. If you want Portage to only download the sources without
178installing them, add the <c>--fetchonly</c> option to the <c>emerge</c> command:
410</p> 179</p>
411 180
412<pre caption="Fetching sources for gnumeric"> 181<pre caption="Download the sourcecode for gnumeric">
413# <i>emerge --fetchonly gnumeric</i> 182# <i>emerge --fetchonly gnumeric</i>
414</pre> 183</pre>
415 184
416<p>
417If you want to see where <c>emerge</c> downloads the sources from, combine the
418<c>--fetchonly</c> and <c>--pretend</c> options:
419</p>
420
421<pre caption="Showing URLs of the sources for gnumeric">
422# <i>emerge --fetchonly --pretend gnumeric</i>
423</pre>
424
425<p>
426You can also opt to install a specific version of a package.
427For instance, if you want to install a gnumeric version older than 1.2 -- for
428any reason whatsoever :) you would type:
429</p>
430
431<pre caption="Installing a specific gnumeric version">
432# <i>emerge "&lt;gnumeric-1.2"</i>
433</pre>
434
435<p>
436Other possibilities are of course "&gt;" (later version) and "=" (the exact
437version).
438</p>
439
440</body> 185</body>
441</subsection>
442<subsection> 186</subsection>
443<title>Installing Prebuilt Packages</title>
444<body>
445
446<p>
447When you want to install a prebuilt package, you should use the <c>--usepkg</c>
448option (<c>-k</c> in short). This will use the binary package available in
449<path>/usr/portage/packages/All</path> <e>if</e> the package and the version of
450the application you want to install match.
451</p>
452
453<pre caption="Installing a prebuilt package for gnumeric">
454# <i>emerge --usepkg gnumeric</i>
455</pre>
456
457<p>
458If you want to use the binary package, even if the versions don't match, use
459<c>--usepkgonly</c> (<c>-K</c> in short).
460</p>
461
462<pre caption="Installing the prebuilt package for gnumeric">
463# <i>emerge --usepkgonly gnumeric</i>
464</pre>
465
466<p>
467If you don't have the prebuilt package on your system yet, you can have
468<c>emerge</c> download it from a mirror, defined in the <c>PORTAGE_BINHOST</c>
469variable declared in <path>/etc/make.conf</path>.
470</p>
471
472<p>
473To download the binary package in case this package doesn't exist on
474your system already, use <c>--getbinpkg</c> (<c>-g</c> in short):
475</p>
476
477<pre caption="Downloading and installing a prebuilt package for gnumeric">
478# <i>emerge --getbinpkg gnumeric</i>
479</pre>
480
481<p>
482This will download the package and the package-related information for you and
483install it on your system, together with the dependencies. If you want to see
484what dependencies will be installed with it, use the <c>--pretend</c> option
485(<c>-p</c> in short):
486</p>
487
488<pre caption="Pretending to download the prebuilt packages for gnumeric">
489# <i>emerge --getbinpkg --pretend gnumeric</i>
490</pre>
491
492<p>
493You can also opt to download the prebuilt package (and the package-related
494information) <e>without</e> checking the information on your local system and
495<e>without</e> using the prebuilt package already on your system (if
496applicable), use the <c>--getbinpkgonly</c> option (<c>-G</c> in short):
497</p>
498
499<pre caption="Installing a prebuilt package without using local information">
500# <i>emerge --getbinpkgonly gnumeric</i>
501</pre>
502
503<p>
504You can also opt to install a specific version of a package.
505For instance, if you want to install a gnumeric version older than 1.2 -- for
506any reason whatsoever :) you would type:
507</p>
508
509<pre caption="Installing a specific gnumeric version">
510# <i>emerge --usepkg "&lt;gnumeric-1.2"</i>
511</pre>
512
513<p>
514Other possibilities are of course "&gt;" (later version) and "=" (the exact
515version).
516</p>
517
518
519</body>
520</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.14_rc1 -debug +doc 698 kB
202</pre>
203
204<p>
205The best way of enable the <c>doc</c> USE flag is doing it per package, in
206<path>/etc/portage/package.use</path>, so you get documentation for the packages
207you are interested in. Enable the flag globally is known to give problems with
208circular dependencies. You can read the chapter about <uri
209link="?part=2&amp;chap=2">USE Flags</uri> for more information about them.
210</p>
211
212<p>
213Once the package installed, its documentation is generally found in a
214subdirectory named after the package under the <path>/usr/share/doc</path>
215directory. You can also list all installed files with the <c>equery</c> tool
216which is part of the <c>app-portage/gentoolkit</c> <uri
217link="/doc/en/gentoolkit.xml">package</uri>.
218</p>
219
220<pre caption="Locating package documentation">
221# <i>ls -l /usr/share/doc/alsa-lib-1.0.14_rc1</i>
222total 28
223-rw-r--r-- 1 root root 669 May 17 21:54 ChangeLog.gz
224-rw-r--r-- 1 root root 9373 May 17 21:54 COPYING.gz
225drwxr-xr-x 2 root root 8560 May 17 21:54 html
226-rw-r--r-- 1 root root 196 May 17 21:54 TODO.gz
227
228<comment>(Alternatively, use equery to locate interesting files:)</comment>
229# <i>equery files alsa-lib | less</i>
230media-libs/alsa-lib-1.0.14_rc1
231* Contents of media-libs/alsa-lib-1.0.14_rc1:
232/usr
233/usr/bin
234/usr/bin/alsalisp
235<comment>(Output truncated)</comment>
236</pre>
237
238</body>
521<subsection> 239</subsection>
522<title>Working with Dependencies</title> 240<subsection>
241<title>Removing Software</title>
523<body> 242<body>
524 243
525<p>
526Portage has an extensive support for dependency handling. Although you usually
527don't need to even think about this (as dependencies are automatically handled
528by Portage) some users might want to know how you can work with <c>emerge</c>
529and dependencies.
530</p> 244<p>
531 245When you want to remove a software package from your system, use <c>emerge
246--unmerge</c>. This will tell Portage to remove all files installed by that
247package from your system <e>except</e> the configuration files of that
248application if you have altered those after the installation. Leaving the
249configuration files allows you to continue working with the package if you ever
250decide to install it again.
532<p> 251</p>
533For instance, if you want Portage to pretend that none of the dependencies of a 252
534package are installed, you can use <c>--emptytree</c> (<c>-e</c> in short). This
535is useful with <c>--pretend</c> to display a complete tree of dependencies for
536any particular package. Without <c>--pretend</c>, <c>emerge</c> will (re)compile
537all listed packages. However, <c>glibc</c> will <e>not</e> be listed as
538dependency for safety reasons.
539</p> 253<p>
540 254However, a <brite>big warning</brite> applies: Portage will <e>not</e> check if
541<pre caption="Show all dependencies of gnumeric"> 255the package you want to remove is required by another package. It will however
542# <i>emerge --emptytree --pretend gnumeric</i> 256warn you when you want to remove an important package that breaks your system
543</pre> 257if you unmerge it.
544
545<p> 258</p>
546Another argument is <c>--nodeps</c>, which will ask Portage to try install the
547given package without taking care of the dependencies. It is trivial that this
548can lead to failures.
549</p>
550 259
551<pre caption="Installing gnumeric without taking care of the dependencies"> 260<pre caption="Removing gnumeric from the system">
552# <i>emerge --nodeps gnumeric</i> 261# <i>emerge --unmerge gnumeric</i>
553</pre> 262</pre>
554 263
555<p>
556To opposite of <c>--nodeps</c> is <c>--onlydeps</c>, which will have Portage
557install all dependencies of a given package, but not the package itself:
558</p> 264<p>
559 265When you remove a package from your system, the dependencies of that package
560<pre caption="Installing the dependencies of gnumeric"> 266that were installed automatically when you installed the software are left. To
561# <i>emerge --onlydeps gnumeric</i> 267have Portage locate all dependencies that can now be removed, use
268<c>emerge</c>'s <c>--depclean</c> functionality. We will talk about this later
269on.
562</pre> 270</p>
563 271
564</body> 272</body>
565</subsection> 273</subsection>
566<subsection> 274<subsection>
567<title>Updating your System</title> 275<title>Updating your System</title>
568<body> 276<body>
569 277
570<p> 278<p>
571Portage knows two special tags to denote a set of software packages: 279To keep your system in perfect shape (and not to mention install the latest
572<e>system</e> and <e>world</e>. You have already seen the former while 280security updates) you need to update your system regularly. Since Portage only
573installing Gentoo if you didn't use a <e>stage3</e> installation. To refresh 281checks the ebuilds in your Portage tree you first have to update your Portage
574things: <e>system</e> is the collection of <e>core</e> packages, necessary to 282tree. When your Portage tree is updated, you can update your system with
575have a working Gentoo system. 283<c>emerge --update world</c>. In the next example, we'll also use the
576</p> 284<c>--ask</c> switch which will tell Portage to display the list of packages it
577 285wants to upgrade and ask you if you want to continue:
578<p> 286</p>
579The <e>world</e> tag consists of all software you have installed yourself on 287
580your system plus the <e>system</e> information. In other words, every time you 288<pre caption="Updating your system">
581emerge a package using <c>emerge &lt;package-name&gt;</c>, the 289# <i>emerge --update --ask world</i>
582<c>&lt;package-name&gt;</c> is registered in the <e>world</e> file 290</pre>
583(<path>/var/cache/edb/world</path>). Dependencies are <e>not</e> part of the 291
584<e>world</e> file, but we will get to that later.
585</p> 292<p>
586 293Portage will then search for newer version of the applications you have
587<p> 294installed. However, it will only verify the versions for the applications you
588If you want to update the system packages, use the <c>--update</c> option 295have <e>explicitly</e> installed (the applications listed in
589(<c>-u</c> in short): 296<path>/var/lib/portage/world</path>) - it does not thoroughly check their
590</p> 297dependencies. If you want to update <e>every single package</e> on your system,
591 298add the <c>--deep</c> argument:
592<pre caption="Updating the system packages">
593# <i>emerge --update system</i>
594</pre>
595
596<p>
597An identical approach can be used for the world packages:
598</p> 299</p>
599 300
600<pre caption="Updating your entire system"> 301<pre caption="Updating your entire system">
601# <i>emerge --update world</i> 302# <i>emerge --update --deep world</i>
602</pre> 303</pre>
603 304
604<p>
605Again, if you want to see what <c>emerge</c> wants to update, use the
606<c>--pretend</c> option together with the <c>--update</c> option:
607</p> 305<p>
608 306Since security updates also happen in packages you have not explicitly installed
609<pre caption="Pretending to update your entire system"> 307on your system (but that are pulled in as dependencies of other programs), it
610# <i>emerge --pretend --update world</i> 308is recommended to run this command once in a while.
611<comment>(Some output removed to improve readability)</comment>
612[ebuild U ] net-misc/wget-1.9-r1 [1.9]
613[ebuild UD] media-video/dvdauthor-0.5.0 [0.5.3]
614[ebuild U ] net-analyzer/ethereal-0.9.16 [0.9.14]
615</pre>
616
617<p> 309</p>
618Right next to the word "ebuild" you will notice a letter (or combination of 310
619letters) which gives you more information about the package: 311<p>
312If you have altered any of your <uri link="?part=2&amp;chap=2">USE flags</uri>
313lately you might want to add <c>--newuse</c> as well. Portage will then verify
314if the change requires the installation of new packages or recompilation of
315existing ones:
316</p>
317
318<pre caption="Performing a full update">
319# <i>emerge --update --deep --newuse world</i>
320</pre>
321
322</body>
323</subsection>
324<subsection>
325<title>Metapackages</title>
326<body>
327
328<p>
329Some packages in the Portage tree don't have any real content but are used to
330install a collection of packages. For instance, the <c>kde</c> package will
331install a complete KDE environment on your system by pulling in various
332KDE-related packages as dependencies.
333</p>
334
335<p>
336If you ever want to remove such a package from your system, running <c>emerge
337--unmerge</c> on the package won't have much effect as the dependencies remain
338on the system.
339</p>
340
341<p>
342Portage has the functionality to remove orphaned dependencies as well, but since
343the availability of software is dynamically dependent you first need to update
344your entire system fully, including the new changes you applied when changing
345USE flags. After this you can run <c>emerge --depclean</c> to remove the
346orphaned dependencies. When this is done, you need to rebuild the applications
347that were dynamically linked to the now-removed software titles but don't
348require them anymore.
349</p>
350
351<p>
352All this is handled with the following three commands:
353</p>
354
355<pre caption="Removing orphaned dependencies">
356# <i>emerge --update --deep --newuse world</i>
357# <i>emerge --depclean</i>
358# <i>revdep-rebuild</i>
359</pre>
360
361<p>
362<c>revdep-rebuild</c> is provided by the <c>gentoolkit</c> package; don't forget
363to emerge it first:
364</p>
365
366<pre caption="Installing the gentoolkit package">
367# <i>emerge gentoolkit</i>
368</pre>
369
370</body>
371</subsection>
372</section>
373<section>
374<title>When Portage is Complaining...</title>
375<subsection>
376<title>About SLOTs, Virtuals, Branches, Architectures and Profiles</title>
377<body>
378
379<p>
380As we stated before, Portage is extremely powerful and supports many features
381that other software management tools lack. To understand this, we explain a few
382aspects of Portage without going into too much detail.
383</p>
384
385<p>
386With Portage different versions of a single package can coexist on a system.
387While other distributions tend to name their package to those versions (like
388<c>freetype</c> and <c>freetype2</c>) Portage uses a technology called
389<e>SLOT</e>s. An ebuild declares a certain SLOT for its version. Ebuilds with
390different SLOTs can coexist on the same system. For instance, the
391<c>freetype</c> package has ebuilds with <c>SLOT="1"</c> and <c>SLOT="2"</c>.
392</p>
393
394<p>
395There are also packages that provide the same functionality but are implemented
396differently. For instance, <c>metalogd</c>, <c>sysklogd</c> and <c>syslog-ng</c>
397are all system loggers. Applications that rely on the availability of "a system
398logger" cannot depend on, for instance, <c>metalogd</c>, as the other system
399loggers are as good a choice as any. Portage allows for <e>virtuals</e>: each
400system logger provides <c>virtual/syslog</c> so that applications can depend on
401<c>virtual/syslog</c>.
402</p>
403
404<p>
405Software in the Portage tree can reside in different branches. By default your
406system only accepts packages that Gentoo deems stable. Most new software titles,
407when committed, are added to the testing branch, meaning more testing needs to
408be done before it is marked as stable. Although you will see the ebuilds for
409those software in the Portage tree, Portage will not update them before they are
410placed in the stable branch.
411</p>
412
413<p>
414Some software is only available for a few architectures. Or the software doesn't
415work on the other architectures, or it needs more testing, or the developer that
416committed the software to the Portage tree is unable to verify if the package
417works on different architectures.
418</p>
419
420<p>
421Each Gentoo installation adheres to a certain <c>profile</c> which contains,
422amongst other information, the list of packages that are required for a system
423to function normally.
424</p>
425
426</body>
427</subsection>
428<subsection id="blocked">
429<title>Blocked Packages</title>
430<body>
431
432<pre caption="Portage warning about blocked packages (with --pretend)">
433[blocks B ] mail-mta/ssmtp (is blocking mail-mta/postfix-2.2.2-r1)
434</pre>
435
436<pre caption="Portage warning about blocked packages (without --pretend)">
437!!! Error: the mail-mta/postfix package conflicts with another package.
438!!! both can't be installed on the same system together.
439!!! Please use 'emerge --pretend' to determine blockers.
440</pre>
441
442<p>
443Ebuilds contain specific fields that inform Portage about its dependencies.
444There are two possible dependencies: build dependencies, declared in
445<c>DEPEND</c> and run-time dependencies, declared in <c>RDEPEND</c>. When one of
446these dependencies explicitly marks a package or virtual as being <e>not</e>
447compatible, it triggers a blockage.
448</p>
449
450<p>
451To fix a blockage, you can choose to not install the package or unmerge the
452conflicting package first. In the given example, you can opt not to install
453<c>postfix</c> or to remove <c>ssmtp</c> first.
454</p>
455
456<p>
457You may also see blocking packages with specific atoms, such as
458<b>&lt;</b>media-video/mplayer-bin-1.0_rc1-r2. In this case, updating to a more
459recent version of the blocking package would remove the block.
460</p>
461
462<p>
463It is also possible that two packages that are yet to be installed are blocking
464each other. In this rare case, you should find out why you need to install both.
465In most cases you can do with one of the packages alone. If not, please file a
466bug on <uri link="http://bugs.gentoo.org">Gentoo's bugtracking system</uri>.
467</p>
468
469</body>
470</subsection>
471<subsection id="masked">
472<title>Masked Packages</title>
473<body>
474
475<pre caption="Portage warning about masked packages">
476!!! all ebuilds that could satisfy "bootsplash" have been masked.
477</pre>
478
479<pre caption="Portage warning about masked packages - reason">
480!!! possible candidates are:
481
482- gnome-base/gnome-2.8.0_pre1 (masked by: <i>~x86 keyword</i>)
483- lm-sensors/lm-sensors-2.8.7 (masked by: <i>-sparc keyword</i>)
484- sys-libs/glibc-2.3.4.20040808 (masked by: <i>-* keyword</i>)
485- dev-util/cvsd-1.0.2 (masked by: <i>missing keyword</i>)
486- games-fps/unreal-tournament-451 (masked by: <i>package.mask</i>)
487- sys-libs/glibc-2.3.2-r11 (masked by: <i>profile</i>)
488</pre>
489
490<p>
491When you want to install a package that isn't available for your system, you
492will receive this masking error. You should try installing a different
493application that is available for your system or wait until the package is put
494available. There is always a reason why a package is masked:
620</p> 495</p>
621 496
622<ul> 497<ul>
623 <li> 498 <li>
624 <e>B</e> (blocks) The package listed to the left is blocking the emerge of 499 <b>~arch keyword</b> means that the application is not tested sufficiently
625 the package listed to the right 500 to be put in the stable branch. Wait a few days or weeks and try again.
626 </li> 501 </li>
627 <li> 502 <li>
628 <e>N</e> (new) The package is new to your system and will be emerged for the 503 <b>-arch keyword</b> or <b>-* keyword</b> means that the application does
629 first time 504 not work on your architecture. If you believe the package does work file
505 a bug at our <uri link="http://bugs.gentoo.org">bugzilla</uri> website.
630 </li> 506 </li>
631 <li> 507 <li>
632 <e>R</e> (reemerge) The package isn't new, but needs to be reemerged 508 <b>missing keyword</b> means that the application has not been tested on
509 your architecture yet. Ask the architecture porting team to test the package
510 or test it for them and report your findings on our <uri
511 link="http://bugs.gentoo.org">bugzilla</uri> website.
633 </li> 512 </li>
634 <li> 513 <li>
635 <e>F</e> (fetch) The package requires that you download the sourcecode 514 <b>package.mask</b> means that the package has been found corrupt, unstable
636 manually (for instance due to licencing issues) 515 or worse and has been deliberately marked as do-not-use.
637 </li> 516 </li>
638 <li> 517 <li>
639 <e>U</e> (update) The package already exists on your system but will be 518 <b>profile</b> means that the package has been found not suitable for your
640 upgraded 519 profile. The application might break your system if you installed it or is
641 </li> 520 just not compatible with the profile you use.
642 <li>
643 <e>UD</e> (downgrade) The package already exists on your system but will be
644 downgraded
645 </li>
646 <li>
647 <e>U-</e> (slot warning) The package you have installed on your system
648 is listed as a package that can not coexist with a different version, but
649 your update does. The update will be installed and the older version will be
650 removed.
651 </li> 521 </li>
652</ul> 522</ul>
653 523
654<p>
655In certain cases, an update may mean a downgrade (i.e. install an older version
656instead of a newer version). If you don't want this to happen, use the
657<c>--upgradeonly</c> option (<c>-U</c> in short):
658</p>
659
660<pre caption="Upgrading your entire system">
661# <i>emerge --update --upgradeonly world</i>
662</pre>
663
664<p>
665Of course, we are talking here about <e>system</e> and <e>world</e>, but you can
666perform the same actions for individual software packages.
667</p>
668
669</body> 524</body>
670</subsection>
671<subsection> 525</subsection>
672<title>Removing Software</title> 526<subsection id="missingdependencies">
673<body> 527<title>Missing Dependencies</title>
674
675<p>
676If you want to remove software from your system, you can use the <c>unmerge</c>
677option (<c>-C</c> - capital C - in short):
678</p>
679
680<pre caption="Uninstalling software">
681# <i>emerge unmerge gnumeric</i>
682</pre>
683
684<p>
685If you want to test a removal (but not perform it), you can use <c>--pretend</c>
686again:
687</p>
688
689<pre caption="Pretending to uninstall software">
690# <i>emerge --pretend unmerge gnumeric</i>
691</pre>
692
693<warn>
694Portage doesn't verify if a package is a dependency for another
695installed package. It also doesn't warn you if the package is part of
696<e>system</e>, i.e. a core application necessary for the correct functioning of
697your system!
698</warn>
699
700<p>
701Once the unmerge begins you will see a long list of filenames belonging to the
702package. Some of these filenames will have a flag displayed to the
703left of the filename. The flags <c>!mtime</c>, <c>!empty</c>, and <c>cfgpro</c>
704specify reasons why certain files are not being removed while the package is.
705Files listed without any of these three flags are removed from the
706filesystem successfully. The three flags specify the following reasons:
707</p>
708
709<ul>
710 <li>
711 <c>!mtime</c> : The listed file has been changed since it was installed,
712 probably by you or some tool
713 </li>
714 <li>
715 <c>!empty</c> : The listed directory is not empty
716 </li>
717 <li>
718 <c>cfgpro</c> : Another already installed package claims to own this file
719 </li>
720</ul>
721
722</body> 528<body>
723</subsection> 529
724</section> 530<pre caption="Portage warning about missing dependency">
725<section> 531emerge: there are no ebuilds to satisfy "&gt;=sys-devel/gcc-3.4.2-r4".
726<title>Software Availability</title> 532
533!!! Problem with ebuild sys-devel/gcc-3.4.2-r2
534!!! Possibly a DEPEND/*DEPEND problem.
535</pre>
536
537<p>
538The application you are trying to install depends on another package that is not
539available for your system. Please check <uri
540link="http://bugs.gentoo.org">bugzilla</uri> if the issue is known and if not,
541please report it. Unless you are mixing branches this should not occur and is
542therefore a bug.
543</p>
544
545</body>
727<subsection> 546</subsection>
728<title>ARCH or not?</title> 547<subsection id="ambiguousebuild">
729<body> 548<title>Ambiguous Ebuild Name</title>
730
731<p>
732Gentoo places its packages in two possible stadia called <e>ARCH</e> and
733<e>~ARCH</e>. Don't take this literally: the stadia depend on the architecture
734you are using. In other words, for x86-based systems you have <e>x86</e> and
735<e>~x86</e>, for ppc-based systems you have <e>ppc</e> and <e>~ppc</e> etc.
736</p>
737
738<p>
739The <e>~ARCH</e> stadium means that the package works for the developer in
740charge of the package, but that the package hasn't been tested thoroughly enough
741by the community to be placed in <e>ARCH</e>. <e>~ARCH</e> packages usually go
742to <e>ARCH</e> after being bugfree for a sufficient amount of time.
743</p>
744
745<p>
746Your system will use <e>ARCH</e> packages per default. If you want to live on
747the edge, don't mind having a broken package once in a while, and you like
748submitting bugreports to <uri
749link="http://bugs.gentoo.org">bugs.gentoo.org</uri>, then you can opt to use
750<e>~ARCH</e> packages. To "move" your system to a <e>~ARCH</e>-using system,
751edit the <c>ACCEPT_KEYWORDS</c> variable in <path>/etc/make.conf</path> so that
752it reads <e>~ARCH</e> (again: for x86-based systems: <e>~x86</e>, etc.).
753</p>
754
755<p>
756If you want to update your system now, you will notice that <e>a lot</e> of
757packages will be updated!
758</p>
759
760</body> 549<body>
761</subsection> 550
551<pre caption="Portage warning about ambiguous ebuild names">
552!!! The short ebuild name "aterm" is ambiguous. Please specify
553!!! one of the following fully-qualified ebuild names instead:
554
555 dev-libs/aterm
556 x11-terms/aterm
557</pre>
558
559<p>
560The application you want to install has a name that corresponds with more than
561one package. You need to supply the category name as well. Portage will inform
562you of possible matches to choose from.
563</p>
564
565</body>
762<subsection> 566</subsection>
763<title>Masked Packages</title> 567<subsection id="circulardependencies">
764<body> 568<title>Circular Dependencies</title>
765
766<p>
767When you want to install a package, you might come across the following message:
768</p>
769
770<pre caption="Message about masked packages">
771Calculating dependencies
772!!! <comment>all ebuilds that could satisfy </comment>&lt;your package&gt;<comment> have been masked.</comment>
773</pre>
774
775<p>
776A package can be masked due to two reasons:
777</p>
778
779<ol>
780 <li>The package is in <e>~ARCH</e> while you use <e>ARCH</e></li>
781 <li>The package is hard-masked explicitly</li>
782</ol>
783
784<p>
785If the package is masked because of the first reason, and you <e>really</e> want
786to install it (knowing that there <e>is</e> a reason why it isn't available in
787<e>ARCH</e>), you can temporarily accept <e>~ARCH</e> packages:
788</p>
789
790<pre caption="Temporarily accepting ~ARCH packages">
791# <i>ACCEPT_KEYWORDS="~x86" emerge gnumeric</i>
792</pre>
793
794<p>
795A package is hardmasked if it is listed in
796<path>/usr/portage/profiles/package.mask</path>. If you read this file, you
797will also read the reason why the package is hardmasked (it is usually added as
798a comment). If you want to install the package nevertheless (despite all the
799possible warnings we could ever throw at your head about "breaking your system",
800"breaks other packages", or "badly needs testing"), create the
801<path>/etc/portage/package.unmask</path> file and list the package in it (use
802the same format as is used in <path>/usr/portage/profiles/package.mask</path>).
803</p>
804
805<p>
806Do <e>not</e> alter the <path>/usr/portage/profiles/package.mask</path> file as
807all changes are undone the next time you update your Portage tree.
808</p>
809
810<p>
811Another trick to circumvent the "masked package" problem is to install the
812package using the full path. This will ignore both the <c>ACCEPT_KEYWORD</c>
813settings and the <path>package.mask</path> listing.
814</p>
815
816<pre caption="Installing a package without checking for stadium / masking">
817# <i>emerge /usr/portage/app-office/gnumeric/gnumeric-1.2.0.ebuild</i>
818</pre>
819
820</body> 569<body>
821</subsection> 570
571<pre caption="Portage warning about circular dependencies">
572!!! Error: circular dependencies:
573
574ebuild / net-print/cups-1.1.15-r2 depends on ebuild / app-text/ghostscript-7.05.3-r1
575ebuild / app-text/ghostscript-7.05.3-r1 depends on ebuild / net-print/cups-1.1.15-r2
576</pre>
577
578<p>
579Two (or more) packages you want to install depend on each other and can
580therefore not be installed. This is most likely a bug in the Portage tree.
581Please resync after a while and try again. You can also check <uri
582link="http://bugs.gentoo.org">bugzilla</uri> if the issue is known and if not,
583report it.
584</p>
585
586</body>
822<subsection> 587</subsection>
823<title>Blocked Packages</title> 588<subsection id="fetchfailed">
589<title>Fetch failed</title>
590<body>
591
592<pre caption="Portage warning about fetch failed">
593!!! Fetch failed for sys-libs/ncurses-5.4-r5, continuing...
594<comment>(...)</comment>
595!!! Some fetch errors were encountered. Please see above for details.
596</pre>
597
598<p>
599Portage was unable to download the sources for the given application and will
600try to continue installing the other applications (if applicable). This failure
601can be due to a mirror that has not synchronised correctly or because the ebuild
602points to an incorrect location. The server where the sources reside can also be
603down for some reason.
604</p>
605
606<p>
607Retry after one hour to see if the issue still persists.
608</p>
609
824<body> 610</body>
611</subsection>
612<subsection id="profileprotect">
613<title>System Profile Protection</title>
614<body>
825 615
826<p> 616<pre caption="Portage warning about profile-protected package">
827You have a situation when you receive the following error on your screen: 617!!! Trying to unmerge package(s) in system profile. 'sys-apps/portage'
618!!! This could be damaging to your system.
619</pre>
620
828</p> 621<p>
829 622You have asked to remove a package that is part of your system's core packages.
830<pre caption="Blocking package"> 623It is listed in your profile as required and should therefore not be removed
831[blocks B ] gnome-base/bonobo-activation (from pkg gnome-base/libbonobo-2.4.0) 624from the system.
832</pre>
833
834<p> 625</p>
835In the above example, the package <c>bonobo-activation</c> is blocking the 626
836emerge of <c>libbonobo</c>. To resolve this issue, remove the 627</body>
837<c>bonobo-activation</c> package and continue: 628</subsection>
629<subsection id="digesterror">
630<title>Digest Verification Failures</title>
631<body>
632
838</p> 633<p>
839 634Sometimes, when you attempt to emerge a package, it will fail with the message:
840<pre caption="Resolving a blocking situation">
841# <i>emerge unmerge bonobo-activation</i>
842</pre> 635</p>
636
637<pre caption="Digest verification failure">
638&gt;&gt;&gt; checking ebuild checksums
639!!! Digest verification failed:
640</pre>
641
642<p>
643This is a sign that something is wrong with the Portage tree -- often, it is
644because a developer may have made a mistake when committing a package to the
645tree.
646</p>
647
648<p>
649When the digest verification fails, do <e>not</e> try to re-digest the package
650yourself. Running <c>ebuild foo digest</c> will not fix the problem; it will
651almost certainly make it worse!
652</p>
653
654<p>
655Instead, wait an hour or two for the tree to settle down. It's likely that the
656error was noticed right away, but it can take a little time for the fix to
657trickle down the Portage tree. While you're waiting, check <uri
658link="http://bugs.gentoo.org">Bugzilla</uri> and see if anyone has reported
659the problem yet. If not, go ahead and file a bug for the broken package.
660</p>
661
662<p>
663Once you see that the bug has been fixed, you may want to re-sync to pick up
664the fixed digest.
665</p>
666
667<impo>
668This does <e>not</e> mean that you can re-sync your tree multiple times! As
669stated in the rsync policy (when you run <c>emerge --sync</c>), users who sync
670too often will be banned! In fact, it's better to just wait until your next
671scheduled sync, so that you don't overload the rsync servers.
672</impo>
843 673
844</body> 674</body>
845</subsection> 675</subsection>
846</section> 676</section>
847</sections> 677</sections>

Legend:
Removed from v.1.13  
changed lines
  Added in v.1.66

  ViewVC Help
Powered by ViewVC 1.1.20