/[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.51 Revision 1.58
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/2.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.51 2005/05/17 14:39:26 neysx Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.58 2006/08/01 17:35:05 swift Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.46</version> 11<version>1.53</version>
12<date>2005-05-17</date> 12<date>2006-08-01</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. You can also create a directory
203called <path>/etc/portage/package.use</path> and list it in a file inside this
204directory. The <uri
205link="?part=2&amp;chap=2">USE Flags</uri> chapter covers this aspect in detail.
206</p>
207
208<p>
209Once the package installed, its documentation is generally found in a
210subdirectory named after the package under the <path>/usr/share/doc</path>
211directory. You can also list all installed files with the <c>equery</c> tool
212which is part of the <c>app-portage/gentoolkit</c> <uri
213link="/doc/en/gentoolkit.xml">package</uri>.
214</p>
215
216<pre caption="Locating package documentation">
217# <i>ls -l /usr/share/doc/alsa-lib-1.0.9_rc3</i>
218total 28
219-rw-r--r-- 1 root root 669 May 17 21:54 ChangeLog.gz
220-rw-r--r-- 1 root root 9373 May 17 21:54 COPYING.gz
221drwxr-xr-x 2 root root 8560 May 17 21:54 html
222-rw-r--r-- 1 root root 196 May 17 21:54 TODO.gz
223
224<comment>(Alternatively, use equery to locate interesting files:)</comment>
225# <i>equery files alsa-lib | less</i>
226media-libs/alsa-lib-1.0.9_rc3
227* Contents of media-libs/alsa-lib-1.0.9_rc3:
228/usr
229/usr/bin
230/usr/bin/alsalisp
231<comment>(Output truncated)</comment>
232</pre>
233
234</body>
235</subsection>
236<subsection>
183<title>Removing Software</title> 237<title>Removing Software</title>
184<body> 238<body>
185 239
186<p> 240<p>
187When you want to remove a software package from your system, use <c>emerge 241When you want to remove a software package from your system, use <c>emerge
220<p> 274<p>
221To keep your system in perfect shape (and not to mention install the latest 275To keep your system in perfect shape (and not to mention install the latest
222security updates) you need to update your system regularly. Since Portage only 276security updates) you need to update your system regularly. Since Portage only
223checks the ebuilds in your Portage tree you first have to update your Portage 277checks the ebuilds in your Portage tree you first have to update your Portage
224tree. When your Portage tree is updated, you can update your system with 278tree. When your Portage tree is updated, you can update your system with
225<c>emerge --update world</c>: 279<c>emerge --update world</c>. In the next example, we'll also use the
280<c>--ask</c> switch which will tell Portage to display the list of packages it
281wants to upgrade and ask you if you want to continue:
226</p> 282</p>
227 283
228<pre caption="Updating your system"> 284<pre caption="Updating your system">
229# <i>emerge --update world</i> 285# <i>emerge --update --ask world</i>
230</pre> 286</pre>
231 287
232<p> 288<p>
233Portage will then search for newer version of the applications you have 289Portage will then search for newer version of the applications you have
234installed. However, it will only verify the versions for the applications you 290installed. However, it will only verify the versions for the applications you
237</p> 293</p>
238 294
239<pre caption="Updating your entire system"> 295<pre caption="Updating your entire system">
240# <i>emerge --update --deep world</i> 296# <i>emerge --update --deep world</i>
241</pre> 297</pre>
298
299<p>
300Since security updates also happen in packages you have not explicitly installed
301on your system (but that are pulled in as dependencies of other programs), it
302is recommended to run this command once in a while.
303</p>
242 304
243<p> 305<p>
244If you have altered any of your <uri link="?part=2&amp;chap=2">USE flags</uri> 306If 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 307lately 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 308if the change requires the installation of new packages or recompilation of
360<subsection id="blocked"> 422<subsection id="blocked">
361<title>Blocked Packages</title> 423<title>Blocked Packages</title>
362<body> 424<body>
363 425
364<pre caption="Portage warning about blocked packages (with --pretend)"> 426<pre caption="Portage warning about blocked packages (with --pretend)">
365[blocks B ] gnome-base/bonobo-activation (from pkg gnome-base/libbonobo-2.4.0) 427[blocks B ] mail-mta/ssmtp (is blocking mail-mta/postfix-2.2.2-r1)
366</pre> 428</pre>
367 429
368<pre caption="Portage warning about blocked packages (without --pretend)"> 430<pre caption="Portage warning about blocked packages (without --pretend)">
369!!! Error: the gnome-base/bonobo-activation package conflicts with another package. 431!!! Error: the mail-mta/postfix package conflicts with another package.
370!!! both can't be installed on the same system together. 432!!! both can't be installed on the same system together.
371!!! Please use 'emerge --pretend' to determine blockers. 433!!! Please use 'emerge --pretend' to determine blockers.
372</pre> 434</pre>
373 435
374<p> 436<p>
380</p> 442</p>
381 443
382<p> 444<p>
383To fix a blockage, you can choose to not install the package or unmerge the 445To fix a blockage, you can choose to not install the package or unmerge the
384conflicting package first. In the given example, you can opt not to install 446conflicting package first. In the given example, you can opt not to install
385<c>libbonobo</c> or to remove <c>bonobo-activation</c> first. 447<c>postfix</c> or to remove <c>ssmtp</c> first.
448</p>
449
450<p>
451It is also possible that two packages that are yet to be installed are blocking
452each other. In this rare case, you should find out why you need to install both.
453In most cases you can do with one of the packages alone. If not, please file a
454bug on <uri link="http://bugs.gentoo.org">Gentoo's bugtracking system</uri>.
386</p> 455</p>
387 456
388</body> 457</body>
389</subsection> 458</subsection>
390<subsection id="masked"> 459<subsection id="masked">

Legend:
Removed from v.1.51  
changed lines
  Added in v.1.58

  ViewVC Help
Powered by ViewVC 1.1.20