/[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.31 Revision 1.32
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.31 2004/08/04 07:01:58 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.32 2004/08/21 18:08:12 swift 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>
90dev-lisp/ gnome-extra/ net-p2p/ 90dev-lisp/ gnome-extra/ net-p2p/
91</pre> 91</pre>
92 92
93<p> 93<p>
94As you can see, the Portage tree has several subdirectories. Most of them are 94As you can see, the Portage tree has several subdirectories. Most of them are
95the <e>categories</e> in which the Gentoo packages, called <e>ebuilds</e>, 95the <e>categories</e> in which the Gentoo packages reside. Take a look at, for
96reside. Take a look at, for instance, <path>app-office</path>: 96instance, <path>app-office</path>:
97</p> 97</p>
98 98
99<pre caption="Viewing a category"> 99<pre caption="Viewing a category">
100# <i>cd app-office; ls --classify</i> 100# <i>cd app-office; ls --classify</i>
101abiword/ gnotime/ kmymoney2/ ooodi/ plan/ timestamp.x 101abiword/ gnotime/ kmymoney2/ ooodi/ plan/ timestamp.x
117ChangeLog files/ openoffice-1.0.3-r1.ebuild openoffice-1.1.0-r2.ebuild 117ChangeLog files/ openoffice-1.0.3-r1.ebuild openoffice-1.1.0-r2.ebuild
118Manifest metadata.xml openoffice-1.1.0-r1.ebuild openoffice-1.1.0.ebuild 118Manifest metadata.xml openoffice-1.1.0-r1.ebuild openoffice-1.1.0.ebuild
119</pre> 119</pre>
120 120
121<p> 121<p>
122Remember that we told you that a Gentoo package is called an ebuild? Well, in 122In the example directory, four ebuilds are stored. An <e>ebuild</e> is a script
123the example directory, four of such ebuilds are stored. Their naming is 123which contains all the necessary information about a specific version of a
124almost identical; they only differ in the version name. 124package. The naming for the ebuilds is almost identical; they only differ in
125the version name.
125You are free to view the contents of such a package: they are plain scripts. We 126You are free to view the contents of such an ebuild: they are plain scripts. We
126will not discuss it right now as it isn't important to know if you plan on just 127will not discuss it right now as it isn't important to know if you plan on just
127using Gentoo. 128using Gentoo.
128</p> 129</p>
129 130
130<p> 131<p>
136extensive description). 137extensive description).
137</p> 138</p>
138 139
139<p> 140<p>
140Inside the <path>files</path> directory, you will find extra files, needed by 141Inside the <path>files</path> directory, you will find extra files, needed by
141Portage: digests (checksums and permissions of the files needed by a single 142Portage: digests (names, sizes and checksums of the files needed by a single
142version of the package), patches, example configuration files, etc. 143version of the package), patches, example configuration files, etc.
143</p> 144</p>
144 145
145<pre caption="Viewing the extra files"> 146<pre caption="Viewing the extra files">
146# <i>cd files; ls --classify</i> 147# <i>cd files; ls --classify</i>
227 228
228<p> 229<p>
229You see something new? Yes, <e>downloaded files</e>. When you tell Portage to 230You see something new? Yes, <e>downloaded files</e>. When you tell Portage to
230install a package, it of course needs to have the necessary sources (or 231install a package, it of course needs to have the necessary sources (or
231precompiled packages) available. It therefore checks the contents of 232precompiled packages) available. It therefore checks the contents of
232<path>/usr/portage/distfiles</path> (for source code) or 233<path>/usr/portage/distfiles</path> to see if the
233<path>/usr/portage/packages/All</path> (for precompiled packages) to see if the
234necessary files are already available. If not, it downloads the necessary files 234necessary files are already available. If not, it downloads the necessary files
235and places them in those directories. 235and places them in thay directory.
236</p> 236</p>
237
238<!--
239<note>
240Searching the Portage Tree, especially when using <c>- -searchdesc</c>, is very
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
243Other Tools</uri>.
244</note>
245-->
246 237
247</body> 238</body>
248</subsection> 239</subsection>
249<subsection> 240<subsection>
250<title>Viewing the ChangeLog</title> 241<title>Viewing the ChangeLog</title>
484<p> 475<p>
485If you don't have the prebuilt package on your system yet, you can have 476If 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> 477<c>emerge</c> download it from a mirror, defined in the <c>PORTAGE_BINHOST</c>
487variable declared in <path>/etc/make.conf</path>. 478variable declared in <path>/etc/make.conf</path>.
488</p> 479</p>
480
481<note>
482Gentoo does not have any server or mirror containing such prebuilt packages.
483Portage has been extended with this feature to fullfil the community request.
484</note>
489 485
490<p> 486<p>
491To download the binary package in case this package doesn't exist on 487To download the binary package in case this package doesn't exist on
492your system already, use <c>--getbinpkg</c> (<c>-g</c> in short): 488your system already, use <c>--getbinpkg</c> (<c>-g</c> in short):
493</p> 489</p>
644 <li> 640 <li>
645 <e>N</e> (new) The package is new to your system and will be emerged for the 641 <e>N</e> (new) The package is new to your system and will be emerged for the
646 first time 642 first time
647 </li> 643 </li>
648 <li> 644 <li>
649 <e>R</e> (replace) The package isn't new, but needs to be reemerged 645 <e>R</e> (replace) The package isn't new, but will be reemerged
650 </li> 646 </li>
651 <li> 647 <li>
652 <e>F</e> (fetch) The package requires that you download the source code 648 <e>F</e> (fetch) The package requires that you download the source code
653 manually (for instance due to licencing issues) 649 manually (for instance due to licencing issues)
654 </li> 650 </li>
658 </li> 654 </li>
659 <li> 655 <li>
660 <e>UD</e> (downgrade) The package already exists on your system but will be 656 <e>UD</e> (downgrade) The package already exists on your system but will be
661 downgraded 657 downgraded
662 </li> 658 </li>
663 <li>
664 <e>U-</e> (slot warning) The package you have installed on your system
665 is listed as a package that can not coexist with a different version, but
666 your update does. The update will be installed and the older version will be
667 removed.
668 </li>
669</ul> 659</ul>
670 660
671<p> 661<p>
672We have mentioned that the <e>world</e> file doesn't contain dependencies. When 662We have mentioned that the <e>world</e> file doesn't contain dependencies. When
673you run <c>emerge --update world</c> only the packages mentioned in the 663you run <c>emerge --update world</c> only the packages mentioned in the
796Calculating dependencies 786Calculating dependencies
797!!! <comment>all ebuilds that could satisfy </comment>&lt;your package&gt;<comment> have been masked.</comment> 787!!! <comment>all ebuilds that could satisfy </comment>&lt;your package&gt;<comment> have been masked.</comment>
798</pre> 788</pre>
799 789
800<p> 790<p>
801A package can be masked due to two reasons: 791A package can be masked due to several reasons:
802</p> 792</p>
803 793
804<ol> 794<ol>
805 <li>The package is in <e>~ARCH</e> while you use <e>ARCH</e></li> 795 <li>The package is in <e>~ARCH</e> while you use <e>ARCH</e></li>
806 <li>The package is hard-masked explicitly</li> 796 <li>The package is hard-masked explicitly</li>
797 <li>The package isn't available for your ARCH entirely</li>
798 <li>The package is masked by your profile</li>
807</ol> 799</ol>
808 800
809<p> 801<p>
810If the package is masked because of the first reason, and you <e>really</e> 802If the package is masked because of the first reason, and you <e>really</e>
811want to install it (knowing that there <e>is</e> a reason why it isn't 803want to install it (knowing that there <e>is</e> a reason why it isn't

Legend:
Removed from v.1.31  
changed lines
  Added in v.1.32

  ViewVC Help
Powered by ViewVC 1.1.20