/[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.29 Revision 1.30
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE sections SYSTEM "/dtd/book.dtd"> 2<!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3 3
4<!-- The content of this document is licensed under the CC-BY-SA license --> 4<!-- The content of this document is licensed under the CC-BY-SA license -->
5<!-- See http://creativecommons.org/licenses/by-sa/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.29 2004/08/01 13:08:35 swift Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.30 2004/08/01 15:03:27 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>
13<title>The Lord of All Tools: emerge</title> 13<title>The Lord of All Tools: emerge</title>
14<body> 14<body>
15 15
16<p> 16<p>
17The main Portage tool that most users will use is <c>emerge</c>. We have already 17The main Portage tool that most users will use is <c>emerge</c>. We have already
18used it during the Gentoo installation and in the previous chapter, but we just 18used it during the Gentoo installation and in the previous chapter, but we just
19briefly explained how to use it. This chapter will elaborate on <c>emerge</c> 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. 20and teach you how to use <c>emerge</c> to fix all your software-related needs.
21</p> 21</p>
22 22
741 probably by you or some tool 741 probably by you or some tool
742 </li> 742 </li>
743 <li> 743 <li>
744 <c>!empty</c> : The listed directory is not empty 744 <c>!empty</c> : The listed directory is not empty
745 </li> 745 </li>
746 <li> 746 <li>
747 <c>cfgpro</c> : This file is located inside a protected directory and will 747 <c>cfgpro</c> : This file is located inside a protected directory and will
748 not be touched for safety 748 not be touched for safety
749 </li> 749 </li>
750</ul> 750</ul>
751 751
752</body> 752</body>
753</subsection> 753</subsection>
754</section> 754</section>
755<section> 755<section>
756<title>Software Availability</title> 756<title>Working with Masked Packages</title>
757<subsection> 757<subsection>
758<title>ARCH or not?</title> 758<title>ARCH or not?</title>
759<body> 759<body>
760 760
761<p> 761<p>
762Gentoo places its packages in two possible stadia called <e>ARCH</e> and 762Gentoo places its packages in two possible stadia called <e>ARCH</e> and
763<e>~ARCH</e>. Don't take this literally: the stadia depend on the architecture 763<e>~ARCH</e>. Don't take this literally: the stadia depend on the architecture
764you are using. In other words, for x86-based systems you have <e>x86</e> and 764you are using. In other words, for x86-based systems you have <e>x86</e> and
765<e>~x86</e>, for ppc-based systems you have <e>ppc</e> and <e>~ppc</e> etc. 765<e>~x86</e>, for ppc-based systems you have <e>ppc</e> and <e>~ppc</e> etc.
766</p> 766</p>
767 767
768<p> 768<p>
769The <e>~ARCH</e> stadium means that the package works for the developer in 769The <e>~ARCH</e> stadium means that the package works for the developer in
770charge of the package, but that the package hasn't been tested thoroughly enough 770charge of the package, but that the package hasn't been tested thoroughly enough
771by the community to be placed in <e>ARCH</e>. <e>~ARCH</e> packages usually go 771by the community to be placed in <e>ARCH</e>. <e>~ARCH</e> packages usually go

Legend:
Removed from v.1.29  
changed lines
  Added in v.1.30

  ViewVC Help
Powered by ViewVC 1.1.20