/[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.50 Revision 1.54
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/2.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.50 2005/05/09 21:15:49 yoswink Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.54 2005/06/11 12:16:14 swift Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.45</version> 11<version>1.49</version>
12<date>2005-05-09</date> 12<date>2005-06-11</date>
13 13
14<section> 14<section>
15<title>Welcome to Portage</title> 15<title>Welcome to Portage</title>
16<body> 16<body>
17 17
178</pre> 178</pre>
179 179
180</body> 180</body>
181</subsection> 181</subsection>
182<subsection> 182<subsection>
183<title>Finding Installed Package Documentation</title>
184<body>
185
186<p>
187Many packages come with their own documentation. Sometimes, the <c>doc</c> USE
188flag determines whether the package documentation should be installed or not.
189You can check the existence of a <c>doc</c> USE flag with the <c>emerge -vp
190&lt;package name&gt;</c> command.
191</p>
192
193<pre caption="Checking the existence of a doc USE flag">
194<comment>(alsa-lib is just an example, of course.)</comment>
195# <i>emerge -vp alsa-lib</i>
196[ebuild N ] media-libs/alsa-lib-1.0.9_rc3 +doc -jack 674 kB
197</pre>
198
199<p>
200You can enable or disable the <c>doc</c> USE flag either globally in the
201<path>/etc/make.conf</path> file or per package in the
202<path>/etc/portage/package.use</path> file. The <uri
203link="?part=2&amp;chap=2">USE Flags</uri> chapter covers this aspect in detail.
204</p>
205
206<p>
207Once the package installed, its documentation is generally found in a
208subdirectory named after the package under the <path>/usr/share/doc</path>
209directory. You can also list all installed files with the <c>equery</c> tool
210which is part of the <c>app-portage/gentoolkit</c> <uri
211link="/doc/en/gentoolkit.xml">package</uri>.
212</p>
213
214<pre caption="Locating package documentation">
215# <i>ls -l /usr/share/doc/alsa-lib-1.0.9_rc3</i>
216total 28
217-rw-r--r-- 1 root root 669 May 17 21:54 ChangeLog.gz
218-rw-r--r-- 1 root root 9373 May 17 21:54 COPYING.gz
219drwxr-xr-x 2 root root 8560 May 17 21:54 html
220-rw-r--r-- 1 root root 196 May 17 21:54 TODO.gz
221
222<comment>(Alternatively, use equery to locate interesting files:)</comment>
223# <i>equery files alsa-lib | less</i>
224media-libs/alsa-lib-1.0.9_rc3
225* Contents of media-libs/alsa-lib-1.0.9_rc3:
226/usr
227/usr/bin
228/usr/bin/alsalisp
229<comment>(Output truncated)</comment>
230</pre>
231
232</body>
233</subsection>
234<subsection>
183<title>Removing Software</title> 235<title>Removing Software</title>
184<body> 236<body>
185 237
186<p> 238<p>
187When you want to remove a software package from your system, use <c>emerge 239When you want to remove a software package from your system, use <c>emerge
239<pre caption="Updating your entire system"> 291<pre caption="Updating your entire system">
240# <i>emerge --update --deep world</i> 292# <i>emerge --update --deep world</i>
241</pre> 293</pre>
242 294
243<p> 295<p>
296Since security updates also happen in packages you have not explicitly installed
297on your system (but that are pulled in as dependencies of other programs), it
298is recommended to run this command once in a while.
299</p>
300
301<p>
244If you have altered any of your <uri link="?part=2&amp;chap=2">USE flags</uri> 302If you have altered any of your <uri link="?part=2&amp;chap=2">USE flags</uri>
245lately you might want to add <c>--newuse</c> as well. Portage will then verify 303lately you might want to add <c>--newuse</c> as well. Portage will then verify
246if the change requires the installation of new packages or recompilation of 304if the change requires the installation of new packages or recompilation of
247existing ones: 305existing ones:
248</p> 306</p>
252</pre> 310</pre>
253 311
254</body> 312</body>
255</subsection> 313</subsection>
256<subsection> 314<subsection>
257<title>Stub Packages</title> 315<title>Metapackages</title>
258<body> 316<body>
259 317
260<p> 318<p>
261Some packages in the Portage tree don't have any real content but are used to 319Some packages in the Portage tree don't have any real content but are used to
262install a collection of packages. For instance, the <c>kde</c> package will 320install a collection of packages. For instance, the <c>kde</c> package will

Legend:
Removed from v.1.50  
changed lines
  Added in v.1.54

  ViewVC Help
Powered by ViewVC 1.1.20