/[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.15 Revision 1.16
1<!-- The content of this document is licensed under the CC-BY-SA license --> 1<!-- The content of this document is licensed under the CC-BY-SA license -->
2<!-- See http://creativecommons.org/licenses/by-sa/1.0 --> 2<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
3 3
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.15 2004/01/06 15:28:05 swift Exp $ --> 4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.16 2004/01/06 15:39:48 swift Exp $ -->
5 5
6<sections> 6<sections>
7<section> 7<section>
8<title>Obtaining Package Information</title> 8<title>Obtaining Package Information</title>
9<subsection> 9<subsection>
10<title>The Lord of All Tools: emerge</title> 10<title>The Lord of All Tools: emerge</title>
11<body> 11<body>
12 12
13<p> 13<p>
14The main Portage tool that most users will use is <c>emerge</c>. We have already 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 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> 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. 17and teach you how to use <c>emerge</c> to fix all your software-related needs.
18</p> 18</p>
19 19
705left of the filename. The flags <c>!mtime</c>, <c>!empty</c>, and <c>cfgpro</c> 705left of the filename. The flags <c>!mtime</c>, <c>!empty</c>, and <c>cfgpro</c>
706specify reasons why certain files are not being removed while the package is. 706specify reasons why certain files are not being removed while the package is.
707Files listed without any of these three flags are removed from the 707Files listed without any of these three flags are removed from the
708filesystem successfully. The three flags specify the following reasons: 708filesystem successfully. The three flags specify the following reasons:
709</p> 709</p>
710 710
711<ul> 711<ul>
712 <li> 712 <li>
713 <c>!mtime</c> : The listed file has been changed since it was installed, 713 <c>!mtime</c> : The listed file has been changed since it was installed,
714 probably by you or some tool 714 probably by you or some tool
715 </li> 715 </li>
716 <li> 716 <li>
717 <c>!empty</c> : The listed directory is not empty 717 <c>!empty</c> : The listed directory is not empty
718 </li> 718 </li>
719 <li> 719 <li>
720 <c>cfgpro</c> : Another already installed package claims to own this file 720 <c>cfgpro</c> : This file is located inside a protected directory and will
721 not be touched for safety
721 </li> 722 </li>
722</ul> 723</ul>
723 724
724</body> 725</body>
725</subsection> 726</subsection>
726</section> 727</section>
727<section> 728<section>
728<title>Software Availability</title> 729<title>Software Availability</title>
729<subsection> 730<subsection>
730<title>ARCH or not?</title> 731<title>ARCH or not?</title>
731<body> 732<body>
732 733
733<p> 734<p>
734Gentoo places its packages in two possible stadia called <e>ARCH</e> and 735Gentoo places its packages in two possible stadia called <e>ARCH</e> and
735<e>~ARCH</e>. Don't take this literally: the stadia depend on the architecture 736<e>~ARCH</e>. Don't take this literally: the stadia depend on the architecture

Legend:
Removed from v.1.15  
changed lines
  Added in v.1.16

  ViewVC Help
Powered by ViewVC 1.1.20