/[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.19 Revision 1.26
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/1.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
6 6
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 $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.26 2004/07/16 09:37:11 neysx Exp $ -->
8 8
9<sections> 9<sections>
10<section> 10<section>
11<title>Obtaining Package Information</title> 11<title>Obtaining Package Information</title>
12<subsection> 12<subsection>
128</p> 128</p>
129 129
130<p> 130<p>
131The 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
132the changes done to the ebuilds), <path>Manifest</path> (which contains the 132the changes done to the ebuilds), <path>Manifest</path> (which contains the
133checksums and permissions of all the files in the directory) and 133checksums and filesizes of all the files in the directory) and
134<path>metadata.xml</path> (which contains more information about the package, 134<path>metadata.xml</path> (which contains more information about the package,
135such 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
136extensive description). 136extensive description).
137</p> 137</p>
138 138
236</p> 236</p>
237 237
238<!-- 238<!--
239<note> 239<note>
240Searching the Portage Tree, especially when using <c>- -searchdesc</c>, is very 240Searching the Portage Tree, especially when using <c>- -searchdesc</c>, is very
241time consuming. There are other, more performant tools available. We will 241time consuming. There are other, best performing tools available. We will
242describe 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
243Other Tools</uri>. 243Other Tools</uri>.
244</note> 244</note>
245--> 245-->
246 246
550<p> 550<p>
551For instance, if you want Portage to pretend that none of the dependencies of a 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 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 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 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 555all listed packages.
556dependency for safety reasons.
557</p> 556</p>
558 557
559<pre caption="Show all dependencies of gnumeric"> 558<pre caption="Show all dependencies of gnumeric">
560# <i>emerge --emptytree --pretend gnumeric</i> 559# <i>emerge --emptytree --pretend gnumeric</i>
561</pre> 560</pre>
678<pre caption="Upgrading your entire system"> 677<pre caption="Upgrading your entire system">
679# <i>emerge --update --upgradeonly world</i> 678# <i>emerge --update --upgradeonly world</i>
680</pre> 679</pre>
681 680
682<p> 681<p>
682We have mentioned that the <e>world</e> file doesn't contain dependencies. When
683you run <c>emerge --update world</c> only the packages mentioned in the
684<e>world</e> file and it's immediate dependencies are checked and, if necessary,
685upgraded. If you want <c>emerge</c> to check <e>all</e> the dependencies
686(including the dependencies of the dependencies), add the <c>--deep</c> flag:
687</p>
688
689<pre caption="Upgrading your entire system, including all dependencies">
690# <i>emerge --update --deep world</i>
691</pre>
692
693<p>
683Of course, we are talking here about <e>system</e> and <e>world</e>, but you can 694Of course, we are talking here about <e>system</e> and <e>world</e>, but you can
684perform the same actions for individual software packages. 695perform the same actions for individual software packages.
685</p> 696</p>
686 697
687</body> 698</body>
761to <e>ARCH</e> after being bugfree for a sufficient amount of time. 772to <e>ARCH</e> after being bugfree for a sufficient amount of time.
762</p> 773</p>
763 774
764<p> 775<p>
765Your system will use <e>ARCH</e> packages per default. If you want to live on 776Your 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 777the edge, don't mind having a broken package once in a while, know how to deal
767submitting bugreports to <uri 778with a broken system and you like submitting bugreports to <uri
768link="http://bugs.gentoo.org">bugs.gentoo.org</uri>, then you can opt to use 779link="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, 780<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 781edit 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.). 782it reads <e>~ARCH</e> (again: for x86-based systems: <e>~x86</e>, etc.).
783</p>
784
785<p>
786Note though that it is far from trivial (if even impossible) to go back to
787<e>ARCH</e> from <e>~ARCH</e>.
772</p> 788</p>
773 789
774<p> 790<p>
775If you want to update your system now, you will notice that <e>a lot</e> of 791If you want to update your system now, you will notice that <e>a lot</e> of
776packages will be updated! 792packages will be updated!
826all changes are undone the next time you update your Portage tree. If you want 842all 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 843to hardmask a package create <path>/etc/portage/package.mask</path> and list the
828package in it (use the same format as mentioned above). 844package in it (use the same format as mentioned above).
829</p> 845</p>
830 846
847<!--
831<p> 848<p>
832Another trick to circumvent the "masked package" problem is to install the 849Another 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> 850package using the full path. This will ignore both the <c>ACCEPT_KEYWORD</c>
834settings and the <path>package.mask</path> listing. 851settings and the <path>package.mask</path> listing.
835</p> 852</p>
836 853
837<pre caption="Installing a package without checking for stadium / masking"> 854<pre caption="Installing a package without checking for stadium / masking">
838# <i>emerge /usr/portage/app-office/gnumeric/gnumeric-1.2.0.ebuild</i> 855# <i>emerge /usr/portage/app-office/gnumeric/gnumeric-1.2.0.ebuild</i>
839</pre> 856</pre>
857-->
840 858
841</body> 859</body>
842</subsection> 860</subsection>
843<subsection> 861<subsection>
844<title>Blocked Packages</title> 862<title>Blocked Packages</title>

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

  ViewVC Help
Powered by ViewVC 1.1.20