/[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.2 Revision 1.19
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/1.0 -->
3 6
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.2 2003/11/25 17:34:47 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.19 2004/01/09 10:52:18 dertobi123 Exp $ -->
5 8
6<sections> 9<sections>
7<section> 10<section>
8<title>Obtaining Package Information</title> 11<title>Obtaining Package Information</title>
9<subsection> 12<subsection>
10<title>The Lord of All Tools: emerge</title> 13<title>The Lord of All Tools: emerge</title>
11<body> 14<body>
12 15
13<p> 16<p>
14We have briefly encountered <c>emerge</c> in the previous chapter, but not to 17The main Portage tool that most users will use is <c>emerge</c>. We have already
15the extent that you are now able to work with it to its fullest potential. We 18used it during the Gentoo installation and in the previous chapter, but we just
16will fix that right now ;-) 19briefly explained how to use it. This chapter will elaborate on <c>emerge</c>
20and teach you how to use <c>emerge</c> to fix all your software-related needs.
17</p> 21</p>
18 22
19<p> 23<p>
20<c>emerge</c> is the command used to install, remove, query and maintain 24<c>emerge</c> is the command used to install, remove, query and maintain
21software packages. It is a front-end for <c>ebuild</c>; people interested in 25software packages. It is a front-end for <c>ebuild</c>; people interested in
42<body> 46<body>
43 47
44<p> 48<p>
45Before we continue describing <c>emerge</c>, let us first take a look at the 49Before we continue describing <c>emerge</c>, let us first take a look at the
46Portage Tree. Go to <path>/usr/portage</path> and do a listing of the available 50Portage Tree. Go to <path>/usr/portage</path> and do a listing of the available
47directories. 51directories. We use <c>ls --classify</c> to list the contents of a
52directory as it will show directories with a trailing "/".
48</p> 53</p>
49 54
50<pre caption="Viewing the Portage Tree"> 55<pre caption="Viewing the Portage Tree">
51# <i>cd /usr/portage; ls --classify</i> 56# <i>cd /usr/portage; ls --classify</i>
52<comment>(The --classify will append a special character to note the filetype)</comment>
53app-admin/ dev-ml/ gnome-libs/ net-print/ 57app-admin/ dev-ml/ gnome-libs/ net-print/
54app-arch/ dev-perl/ gnome-office/ net-wireless/ 58app-arch/ dev-perl/ gnome-office/ net-wireless/
55app-benchmarks/ dev-php/ header.txt net-www/ 59app-benchmarks/ dev-php/ header.txt net-www/
56app-cdr/ dev-python/ incoming/ net-zope/ 60app-cdr/ dev-python/ incoming/ net-zope/
57app-crypt/ dev-ruby/ jython/ packages/ 61app-crypt/ dev-ruby/ jython/ packages/
102gnofin/ khacc/ mrproject/ phprojekt/ texmacs/ 106gnofin/ khacc/ mrproject/ phprojekt/ texmacs/
103</pre> 107</pre>
104 108
105<p> 109<p>
106Inside a category you will find the packages belonging to that category, with a 110Inside a category you will find the packages belonging to that category, with a
107seperate directory for each package. Let us take a look at the <c>openoffice</c> 111separate directory for each package. Let us take a look at the <c>openoffice</c>
108package: 112package:
109</p> 113</p>
110 114
111<pre caption="Viewing a package"> 115<pre caption="Viewing a package">
112# <i>cd openoffice; ls --classify</i> 116# <i>cd openoffice; ls --classify</i>
126<p> 130<p>
127The other files are the <path>ChangeLog</path> (which contains a listing of all 131The other files are the <path>ChangeLog</path> (which contains a listing of all
128the changes done to the ebuilds), <path>Manifest</path> (which contains the 132the changes done to the ebuilds), <path>Manifest</path> (which contains the
129checksums and permissions of all the files in the directory) and 133checksums and permissions of all the files in the directory) and
130<path>metadata.xml</path> (which contains more information about the package, 134<path>metadata.xml</path> (which contains more information about the package,
131such as the responsible development group -- called <e>herd</e> and a more 135such as the responsible development group -- called <e>herd</e> -- and a more
132extensive description). 136extensive description).
133</p> 137</p>
134 138
135<p> 139<p>
136Inside the <path>files</path> directory you will find extra files, needed by 140Inside the <path>files</path> directory you will find extra files, needed by
221the size of the downloaded files, the homepage and the small description. 225the size of the downloaded files, the homepage and the small description.
222</p> 226</p>
223 227
224<p> 228<p>
225You see something new? Yes, <e>downloaded files</e>. When you tell Portage to 229You see something new? Yes, <e>downloaded files</e>. When you tell Portage to
226install a package, it ofcourse needs to have the necessary sources (or 230install a package, it of course needs to have the necessary sources (or
227precompiled packages) available. It therefor checks the contents of 231precompiled packages) available. It therefore checks the contents of
228<path>/usr/portage/distfiles</path> (for sourcecode) or 232<path>/usr/portage/distfiles</path> (for source code) or
229<path>/usr/portage/packages/All</path> (for precompiled packages) to see if the 233<path>/usr/portage/packages/All</path> (for precompiled packages) to see if the
230necessary files are already available. If not, it downloads the necessary files 234necessary files are already available. If not, it downloads the necessary files
231and places them in those directories. 235and places them in those directories.
232</p> 236</p>
233 237
238<!--
234<note> 239<note>
235Searching the Portage Tree, especially when using <c>--searchdesc</c>, is very 240Searching the Portage Tree, especially when using <c>- -searchdesc</c>, is very
236time consuming. There are other, more performant tools available. We will 241time consuming. There are other, more performant tools available. We will
237describe those in the chapter on <uri link="?part=2&amp;chap=7">Gentoolkit and 242describe those in the chapter on <uri link="?part=2&amp;chap=7">Gentoolkit and
238Other Tools</uri>. 243Other Tools</uri>.
239</note> 244</note>
245-->
246
247</body>
248</subsection>
249<subsection>
250<title>Viewing the ChangeLog</title>
251<body>
252
253<p>
254While browsing through the Portage Tree, you saw that there was a ChangeLog for
255each package. You can view the ChangeLog entries between the available version
256and the installed version with <c>emerge</c> too. Use the
257<c>--pretend --changelog</c> (<c>-pl</c> in short) options. As an example we
258will view the ChangeLog entries for <c>gnumeric</c>:
259</p>
260
261<pre caption="Viewing the ChangeLog entries for gnumeric">
262# <i>emerge --pretend --changelog gnumeric</i>
263<comment>(Some output removed to improve readability)</comment>
264*gnumeric-1.2.2
265
266 27 Nov 2003; foser &lt;foser@gentoo.org&gt; gnumeric-1.2.2.ebuild :
267 New release, requested in #34492
268 updated deps
269
270 12 Nov 2003; Jason Wever &lt;weeve@gentoo.org&gt; gnumeric-1.2.0.ebuild:
271 Marked stable on sparc, fixes bug #32405.
272
273 14 Oct 2003; Jason Wever &lt;weeve@gentoo.org&gt; gnumeric-1.0.8.ebuild:
274 Added ~sparc keyword. Fixes bug #31150.
275</pre>
240 276
241</body> 277</body>
242</subsection> 278</subsection>
243</section> 279</section>
244<section> 280<section>
248<body> 284<body>
249 285
250<p> 286<p>
251Searching through Portage is nice, but if you don't update your Portage Tree 287Searching through Portage is nice, but if you don't update your Portage Tree
252regularly, you will be stuck with the packages and versions available on your 288regularly, you will be stuck with the packages and versions available on your
253system. This means that your system will get outdated pretty soon, and that 289system. This means that your system will get outdated pretty soon and that
254packages with possible security problems will remain on your system. 290you will be missing bugfixes and remedies for possible security problems.
255</p> 291</p>
256 292
257<p> 293<p>
258There are several ways to update your Portage Tree. The most popular method is 294There are several ways to update your Portage Tree. The most popular method is
259by using one of our <uri link="/main/en/mirrors.xml">rsync mirrors</uri>. 295by using one of our <uri link="/main/en/mirrors.xml">rsync mirrors</uri>.
280# <i>emerge --usepkg mirrorselect</i> 316# <i>emerge --usepkg mirrorselect</i>
281</pre> 317</pre>
282 318
283<p> 319<p>
284Now run <c>mirrorselect</c> to automatically select mirrors for you (it will 320Now run <c>mirrorselect</c> to automatically select mirrors for you (it will
285also setup Portage to use a mirror for the sourcecode): 321also setup Portage to use a mirror for the source code):
286</p> 322</p>
287 323
288<pre caption="Running mirrorselect"> 324<pre caption="Running mirrorselect">
289# <i>mirrorselect -a -s3</i> 325# <i>mirrorselect -a -s3</i>
290</pre> 326</pre>
318</subsection> 354</subsection>
319</section> 355</section>
320<section> 356<section>
321<title>Maintaining Software</title> 357<title>Maintaining Software</title>
322<subsection> 358<subsection>
323<title>Installing Software</title> 359<title>Building or Prebuilt?</title>
324<body>
325
326</body> 360<body>
327</subsection> 361
362<p>
363Gentoo provides ebuilds, the Gentoo packages if you like. But when you want to
364install such an ebuild, you can choose between <e>building</e> the package and
365using a <e>prebuilt</e> package. But what are the advantages/disadvantages of
366both approaches, and can they be used next to each other?
367</p>
368
369<p>
370As you probably have guessed, building packages takes a lot of time (especially
371if you have little resources or want to build big packages, such as <uri
372link="http://www.kde.org">KDE</uri>, <uri
373link="http://www.openoffice.org">OpenOffice.org</uri>, etc.). By building the
374package, you can use the <c>USE</c> setting to tweak the package to your system.
375Of course, you can also define high optimization options (in the <c>CFLAGS</c>
376and <c>CXXFLAGS</c> variables) to compile the package with.
377</p>
378
379<p>
380Using prebuilt packages improves the installation time (as no more compilation
381is needed), but you will lose the advantages of the <c>USE</c> setting and the
382<c>CFLAGS</c> &amp; <c>CXXFLAGS</c> variables.
383</p>
384
385<p>
386As previously stated, prebuilt packages are stored in the
387<path>/usr/portage/packages/All</path> directory, while the source code of the
388packages is placed in <path>/usr/portage/distfiles</path>. If you have finished
389installing a package you can remove the package or source code from the
390respective directory. However, you might want to keep the package/source code of
391the latest version, just in case you want to reinstall the package (so you don't
392have to redownload it).
393</p>
394
395</body>
328<subsection> 396</subsection>
329<title>Updating Software</title> 397<subsection>
398<title>Installing Software from Sources</title>
399<body>
400
401<p>
402Okay, enough talking, let's cut to the chase. To install a package, you will use
403the <c>emerge</c> command. If you don't want to use any prebuilt packages, you
404can just use <c>emerge &lt;package-name&gt;</c> or <c>emerge
405&lt;category&gt;/&lt;package-name&gt;</c>. As an example we'll install
406<c>gnumeric</c>:
407</p>
408
409<pre caption="Building gnumeric">
410# <i>emerge gnumeric</i>
411</pre>
412
413<p>
414This will download the source code for you and unpacks, compiles and installs
415the package on your system. It will also do the same for all the dependencies.
416If you want to see what dependencies will be installed with it, use the
417<c>--pretend</c> option (<c>-p</c> in short):
418</p>
419
420<pre caption="Pretending to build gnumeric">
421# <i>emerge --pretend gnumeric</i>
422</pre>
423
424<p>
425If you want to download the source code of the package and its dependencies,
426but don't want to build the package, use the <c>--fetchonly</c> option
427(<c>-f</c> in short):
428</p>
429
430<pre caption="Fetching sources for gnumeric">
431# <i>emerge --fetchonly gnumeric</i>
432</pre>
433
434<p>
435If you want to see where <c>emerge</c> downloads the sources from, combine the
436<c>--fetchonly</c> and <c>--pretend</c> options:
437</p>
438
439<pre caption="Showing URLs of the sources for gnumeric">
440# <i>emerge --fetchonly --pretend gnumeric</i>
441</pre>
442
443<p>
444You can also opt to install a specific version of a package.
445For instance, if you want to install a gnumeric version older than 1.2 -- for
446any reason whatsoever :) you would type:
447</p>
448
449<pre caption="Installing a specific gnumeric version">
450# <i>emerge "&lt;gnumeric-1.2"</i>
451</pre>
452
453<p>
454Other possibilities are of course "&gt;" (later version) and "=" (the exact
455version).
456</p>
457
330<body> 458</body>
459</subsection>
460<subsection>
461<title>Installing Prebuilt Packages</title>
462<body>
463
464<p>
465When you want to install a prebuilt package, you should use the <c>--usepkg</c>
466option (<c>-k</c> in short). This will use the binary package available in
467<path>/usr/portage/packages/All</path> <e>if</e> the package and the version of
468the application you want to install match.
469</p>
470
471<pre caption="Installing a prebuilt package for gnumeric">
472# <i>emerge --usepkg gnumeric</i>
473</pre>
474
475<p>
476If you want to use the binary package, even if the versions don't match, use
477<c>--usepkgonly</c> (<c>-K</c> in short).
478</p>
479
480<pre caption="Installing the prebuilt package for gnumeric">
481# <i>emerge --usepkgonly gnumeric</i>
482</pre>
483
484<p>
485If you don't have the prebuilt package on your system yet, you can have
486<c>emerge</c> download it from a mirror, defined in the <c>PORTAGE_BINHOST</c>
487variable declared in <path>/etc/make.conf</path>.
488</p>
489
490<p>
491To download the binary package in case this package doesn't exist on
492your system already, use <c>--getbinpkg</c> (<c>-g</c> in short):
493</p>
494
495<pre caption="Downloading and installing a prebuilt package for gnumeric">
496# <i>emerge --getbinpkg gnumeric</i>
497</pre>
498
499<p>
500This will download the package and the package-related information for you and
501install it on your system, together with the dependencies. If you want to see
502what dependencies will be installed with it, use the <c>--pretend</c> option
503(<c>-p</c> in short):
504</p>
505
506<pre caption="Pretending to download the prebuilt packages for gnumeric">
507# <i>emerge --getbinpkg --pretend gnumeric</i>
508</pre>
509
510<p>
511You can also opt to download the prebuilt package (and the package-related
512information) <e>without</e> checking the information on your local system and
513<e>without</e> using the prebuilt package already on your system (if
514applicable), use the <c>--getbinpkgonly</c> option (<c>-G</c> in short):
515</p>
516
517<pre caption="Installing a prebuilt package without using local information">
518# <i>emerge --getbinpkgonly gnumeric</i>
519</pre>
520
521<p>
522You can also opt to install a specific version of a package.
523For instance, if you want to install a gnumeric version older than 1.2 -- for
524any reason whatsoever :) you would type:
525</p>
526
527<pre caption="Installing a specific gnumeric version">
528# <i>emerge --usepkg "&lt;gnumeric-1.2"</i>
529</pre>
530
531<p>
532Other possibilities are of course "&gt;" (later version) and "=" (the exact
533version).
534</p>
535
536
537</body>
538</subsection>
539<subsection>
540<title>Working with Dependencies</title>
541<body>
542
543<p>
544Portage has an extensive support for dependency handling. Although you usually
545don't need to even think about this (as dependencies are automatically handled
546by Portage) some users might want to know how you can work with <c>emerge</c>
547and dependencies.
548</p>
549
550<p>
551For instance, if you want Portage to pretend that none of the dependencies of a
552package are installed, you can use <c>--emptytree</c> (<c>-e</c> in short). This
553is useful with <c>--pretend</c> to display a complete tree of dependencies for
554any particular package. Without <c>--pretend</c>, <c>emerge</c> will (re)compile
555all listed packages. However, <c>glibc</c> will <e>not</e> be listed as
556dependency for safety reasons.
557</p>
558
559<pre caption="Show all dependencies of gnumeric">
560# <i>emerge --emptytree --pretend gnumeric</i>
561</pre>
562
563<p>
564Another argument is <c>--nodeps</c>, which will ask Portage to try install the
565given package without taking care of the dependencies. It is trivial that this
566can lead to failures.
567</p>
568
569<pre caption="Installing gnumeric without taking care of the dependencies">
570# <i>emerge --nodeps gnumeric</i>
571</pre>
572
573<p>
574The opposite of <c>--nodeps</c> is <c>--onlydeps</c>, which will have Portage
575install all dependencies of a given package, but not the package itself:
576</p>
577
578<pre caption="Installing the dependencies of gnumeric">
579# <i>emerge --onlydeps gnumeric</i>
580</pre>
581
582</body>
583</subsection>
584<subsection>
585<title>Updating your System</title>
586<body>
587
588<p>
589Portage knows two special tags to denote a set of software packages:
590<e>system</e> and <e>world</e>. You have already seen the former while
591installing Gentoo if you didn't use a <e>stage3</e> installation. To refresh
592things: <e>system</e> is the collection of <e>core</e> packages, necessary to
593have a working Gentoo system.
594</p>
595
596<p>
597The <e>world</e> tag consists of all software you have installed yourself on
598your system plus the <e>system</e> information. In other words, every time you
599emerge a package using <c>emerge &lt;package-name&gt;</c>, the
600<c>&lt;package-name&gt;</c> is registered in the <e>world</e> file
601(<path>/var/cache/edb/world</path>). Dependencies are <e>not</e> part of the
602<e>world</e> file, but we will get to that later.
603</p>
604
605<p>
606If you want to update the system packages, use the <c>--update</c> option
607(<c>-u</c> in short):
608</p>
609
610<pre caption="Updating the system packages">
611# <i>emerge --update system</i>
612</pre>
613
614<p>
615An identical approach can be used for the world packages:
616</p>
617
618<pre caption="Updating your entire system">
619# <i>emerge --update world</i>
620</pre>
621
622<p>
623Again, if you want to see what <c>emerge</c> wants to update, use the
624<c>--pretend</c> option together with the <c>--update</c> option:
625</p>
626
627<pre caption="Pretending to update your entire system">
628# <i>emerge --pretend --update world</i>
629<comment>(Some output removed to improve readability)</comment>
630[ebuild U ] net-misc/wget-1.9-r1 [1.9]
631[ebuild UD] media-video/dvdauthor-0.5.0 [0.5.3]
632[ebuild U ] net-analyzer/ethereal-0.9.16 [0.9.14]
633</pre>
634
635<p>
636Right next to the word "ebuild" you will notice a letter (or combination of
637letters) which gives you more information about the package:
638</p>
639
640<ul>
641 <li>
642 <e>B</e> (blocks) The package listed to the left is blocking the emerge of
643 the package listed to the right
644 </li>
645 <li>
646 <e>N</e> (new) The package is new to your system and will be emerged for the
647 first time
648 </li>
649 <li>
650 <e>R</e> (reemerge) The package isn't new, but needs to be reemerged
651 </li>
652 <li>
653 <e>F</e> (fetch) The package requires that you download the source code
654 manually (for instance due to licencing issues)
655 </li>
656 <li>
657 <e>U</e> (update) The package already exists on your system but will be
658 upgraded
659 </li>
660 <li>
661 <e>UD</e> (downgrade) The package already exists on your system but will be
662 downgraded
663 </li>
664 <li>
665 <e>U-</e> (slot warning) The package you have installed on your system
666 is listed as a package that can not coexist with a different version, but
667 your update does. The update will be installed and the older version will be
668 removed.
669 </li>
670</ul>
671
672<p>
673In certain cases, an update may mean a downgrade (i.e. install an older version
674instead of a newer version). If you don't want this to happen, use the
675<c>--upgradeonly</c> option (<c>-U</c> in short):
676</p>
677
678<pre caption="Upgrading your entire system">
679# <i>emerge --update --upgradeonly world</i>
680</pre>
681
682<p>
683Of course, we are talking here about <e>system</e> and <e>world</e>, but you can
684perform the same actions for individual software packages.
685</p>
331 686
332</body> 687</body>
333</subsection> 688</subsection>
334<subsection> 689<subsection>
335<title>Removing Software</title> 690<title>Removing Software</title>
336<body> 691<body>
692
693<p>
694If you want to remove software from your system, you can use the <c>unmerge</c>
695option (<c>-C</c> - capital C - in short):
696</p>
697
698<pre caption="Uninstalling software">
699# <i>emerge unmerge gnumeric</i>
700</pre>
701
702<p>
703If you want to test a removal (but not perform it), you can use <c>--pretend</c>
704again:
705</p>
706
707<pre caption="Pretending to uninstall software">
708# <i>emerge --pretend unmerge gnumeric</i>
709</pre>
710
711<warn>
712Portage doesn't verify if a package is a dependency for another
713installed package. It also doesn't warn you if the package is part of
714<e>system</e>, i.e. a core application necessary for the correct functioning of
715your system!
716</warn>
717
718<p>
719Once the unmerge begins you will see a long list of filenames belonging to the
720package. Some of these filenames will have a flag displayed to the
721left of the filename. The flags <c>!mtime</c>, <c>!empty</c>, and <c>cfgpro</c>
722specify reasons why certain files are not being removed while the package is.
723Files listed without any of these three flags are removed from the
724filesystem successfully. The three flags specify the following reasons:
725</p>
726
727<ul>
728 <li>
729 <c>!mtime</c> : The listed file has been changed since it was installed,
730 probably by you or some tool
731 </li>
732 <li>
733 <c>!empty</c> : The listed directory is not empty
734 </li>
735 <li>
736 <c>cfgpro</c> : This file is located inside a protected directory and will
737 not be touched for safety
738 </li>
739</ul>
337 740
338</body> 741</body>
339</subsection> 742</subsection>
340</section> 743</section>
341<section> 744<section>
342<title>Software Availability</title> 745<title>Software Availability</title>
343<subsection> 746<subsection>
344<title>ARCH or not?</title> 747<title>ARCH or not?</title>
345<body> 748<body>
346 749
750<p>
751Gentoo places its packages in two possible stadia called <e>ARCH</e> and
752<e>~ARCH</e>. Don't take this literally: the stadia depend on the architecture
753you are using. In other words, for x86-based systems you have <e>x86</e> and
754<e>~x86</e>, for ppc-based systems you have <e>ppc</e> and <e>~ppc</e> etc.
755</p>
756
757<p>
758The <e>~ARCH</e> stadium means that the package works for the developer in
759charge of the package, but that the package hasn't been tested thoroughly enough
760by the community to be placed in <e>ARCH</e>. <e>~ARCH</e> packages usually go
761to <e>ARCH</e> after being bugfree for a sufficient amount of time.
762</p>
763
764<p>
765Your system will use <e>ARCH</e> packages per default. If you want to live on
766the edge, don't mind having a broken package once in a while, and you like
767submitting bugreports to <uri
768link="http://bugs.gentoo.org">bugs.gentoo.org</uri>, then you can opt to use
769<e>~ARCH</e> packages. To "move" your system to a <e>~ARCH</e>-using system,
770edit the <c>ACCEPT_KEYWORDS</c> variable in <path>/etc/make.conf</path> so that
771it reads <e>~ARCH</e> (again: for x86-based systems: <e>~x86</e>, etc.).
772</p>
773
774<p>
775If you want to update your system now, you will notice that <e>a lot</e> of
776packages will be updated!
777</p>
778
347</body> 779</body>
348</subsection> 780</subsection>
349<subsection> 781<subsection>
350<title>Masked Packages</title> 782<title>Masked Packages</title>
351<body> 783<body>
352 784
785<p>
786When you want to install a package, you might come across the following message:
787</p>
788
789<pre caption="Message about masked packages">
790Calculating dependencies
791!!! <comment>all ebuilds that could satisfy </comment>&lt;your package&gt;<comment> have been masked.</comment>
792</pre>
793
794<p>
795A package can be masked due to two reasons:
796</p>
797
798<ol>
799 <li>The package is in <e>~ARCH</e> while you use <e>ARCH</e></li>
800 <li>The package is hard-masked explicitly</li>
801</ol>
802
803<p>
804If the package is masked because of the first reason, and you <e>really</e> want
805to install it (knowing that there <e>is</e> a reason why it isn't available in
806<e>ARCH</e>), you can temporarily accept <e>~ARCH</e> packages:
807</p>
808
809<pre caption="Temporarily accepting ~ARCH packages">
810# <i>ACCEPT_KEYWORDS="~x86" emerge gnumeric</i>
811</pre>
812
813<p>
814A package is hardmasked if it is listed in
815<path>/usr/portage/profiles/package.mask</path>. If you read this file, you
816will also read the reason why the package is hardmasked (it is usually added as
817a comment). If you want to install the package nevertheless (despite all the
818possible warnings we could ever throw at your head about "breaking your system",
819"breaks other packages", or "badly needs testing"), create the
820<path>/etc/portage/package.unmask</path> file and list the package in it (use
821the same format as is used in <path>/usr/portage/profiles/package.mask</path>).
822</p>
823
824<p>
825Do <e>not</e> alter the <path>/usr/portage/profiles/package.mask</path> file as
826all changes are undone the next time you update your Portage tree. If you want
827to hardmask a package create <path>/etc/portage/package.mask</path> and list the
828package in it (use the same format as mentioned above).
829</p>
830
831<p>
832Another trick to circumvent the "masked package" problem is to install the
833package using the full path. This will ignore both the <c>ACCEPT_KEYWORD</c>
834settings and the <path>package.mask</path> listing.
835</p>
836
837<pre caption="Installing a package without checking for stadium / masking">
838# <i>emerge /usr/portage/app-office/gnumeric/gnumeric-1.2.0.ebuild</i>
839</pre>
840
353</body> 841</body>
354</subsection> 842</subsection>
355<subsection> 843<subsection>
356<title>Blocked Packages</title> 844<title>Blocked Packages</title>
357<body> 845<body>
846
847<p>
848You have a situation when you receive the following error on your screen:
849</p>
850
851<pre caption="Blocking package">
852[blocks B ] gnome-base/bonobo-activation (from pkg gnome-base/libbonobo-2.4.0)
853</pre>
854
855<p>
856In the above example, the package <c>bonobo-activation</c> is blocking the
857emerge of <c>libbonobo</c>. To resolve this issue, remove the
858<c>bonobo-activation</c> package and continue:
859</p>
860
861<pre caption="Resolving a blocking situation">
862# <i>emerge unmerge bonobo-activation</i>
863</pre>
358 864
359</body> 865</body>
360</subsection> 866</subsection>
361</section> 867</section>
362</sections> 868</sections>

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.19

  ViewVC Help
Powered by ViewVC 1.1.20