/[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.27 Revision 1.28
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.27 2004/07/18 10:41:51 neysx Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.28 2004/07/26 11:41:23 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
108 108
109<p> 109<p>
110Inside 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
111separate 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>
112package: 112package:
113</p> 113</p>
114 114
115<pre caption="Viewing a package"> 115<pre caption="Viewing a package">
116# <i>cd openoffice; ls --classify</i> 116# <i>cd openoffice; ls --classify</i>
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 122Remember that we told you that a Gentoo package is called an ebuild? Well, in
123the example directory four of such ebuilds are stored. Their naming is 123the example directory, four of such ebuilds are stored. Their naming is
124almost identical: they only differ in the version name. 124almost identical; they only differ in the version name.
125You are free to view the contents of such a package: they are plain scripts. We 125You are free to view the contents of such a package: they are plain scripts. We
126will not discuss it right now as it isn't important to know if you plan on just 126will not discuss it right now as it isn't important to know if you plan on just
127using Gentoo. 127using Gentoo.
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 filesizes 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
139<p> 139<p>
140Inside 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
141Portage: digests (checksums and permissions of the files needed by a single 141Portage: digests (checksums and permissions of the files needed by a single
142version of the package), patches, example configuration files, etc. 142version of the package), patches, example configuration files, etc.
143</p> 143</p>
144 144
145<pre caption="Viewing the extra files"> 145<pre caption="Viewing the extra files">
146# <i>cd files; ls --classify</i> 146# <i>cd files; ls --classify</i>
1471.0.3/ digest-openoffice-1.0.3-r1 digest-openoffice-1.1.0-r1 1471.0.3/ digest-openoffice-1.0.3-r1 digest-openoffice-1.1.0-r1
1481.1.0/ digest-openoffice-1.1.0 digest-openoffice-1.1.0-r2 1481.1.0/ digest-openoffice-1.1.0 digest-openoffice-1.1.0-r2
149# <i>cd 1.1.0; ls --classify</i> 149# <i>cd 1.1.0; ls --classify</i>
150fixed-gcc.patch ooffice-wrapper-1.3 150fixed-gcc.patch ooffice-wrapper-1.3
151newstlportfix.patch openoffice-1.1.0-linux-2.6-fix.patch 151newstlportfix.patch openoffice-1.1.0-linux-2.6-fix.patch
152no-mozab.patch openoffice-1.1.0-sparc64-fix.patch 152no-mozab.patch openoffice-1.1.0-sparc64-fix.patch
153nptl.patch 153nptl.patch
154</pre> 154</pre>
155 155
156<p> 156<p>
157If you go back to the root of the Portage tree (<path>/usr/portage</path>) you 157If you go back to the root of the Portage tree (<path>/usr/portage</path>) you
158will notice that there are other, non-category directories too. We will discuss 158will notice that there are other, non-category directories, too. We will discuss
159those later in this chapter. 159those later in this chapter.
160</p> 160</p>
161 161
162</body> 162</body>
163</subsection> 163</subsection>
164<subsection> 164<subsection>
165<title>Search for a Package</title> 165<title>Search for a Package</title>
166<body> 166<body>
167 167
168<p> 168<p>
169If you are new to Linux or Gentoo, you might not know what tool you need for 169If you are new to Linux or Gentoo, you might not know what tool you need for
170what job. To facilitate searching, <c>emerge</c> provides you with a way to 170what job. To facilitate searching, <c>emerge</c> provides you with a way to
171search through the available packages on your system. There are two ways you can 171search through the available packages on your system. There are two ways you can
172search through packages: by <e>name</e>, or by <e>name</e> and 172search through packages: by <e>name</e>, or by <e>name</e> and
173<e>description</e>. 173<e>description</e>.

Legend:
Removed from v.1.27  
changed lines
  Added in v.1.28

  ViewVC Help
Powered by ViewVC 1.1.20