| … | |
… | |
| 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.47 2005/01/22 01:24:31 cam Exp $ --> |
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 $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <version>1.43</version> |
11 | <version>1.46</version> |
| 12 | <date>2005-01-22</date> |
12 | <date>2005-05-17</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 | |
| … | |
… | |
| 66 | <title>Updating the Portage Tree</title> |
66 | <title>Updating the Portage Tree</title> |
| 67 | <body> |
67 | <body> |
| 68 | |
68 | |
| 69 | <p> |
69 | <p> |
| 70 | The Portage tree is usually updated with <uri |
70 | The Portage tree is usually updated with <uri |
| 71 | link="http://rsync.gentoo.org">rsync</uri>, a fast incremental file transfer |
71 | link="http://rsync.samba.org/">rsync</uri>, a fast incremental file transfer |
| 72 | utility. Updating is fairly simple as the <c>emerge</c> command provides a |
72 | utility. Updating is fairly simple as the <c>emerge</c> command provides a |
| 73 | front-end for rsync: |
73 | front-end for rsync: |
| 74 | </p> |
74 | </p> |
| 75 | |
75 | |
| 76 | <pre caption="Updating the Portage tree"> |
76 | <pre caption="Updating the Portage tree"> |
| … | |
… | |
| 125 | When you take a look at the output, you'll notice that it gives you a lot of |
125 | When you take a look at the output, you'll notice that it gives you a lot of |
| 126 | information. The fields are clearly labelled so we won't go further into their |
126 | information. The fields are clearly labelled so we won't go further into their |
| 127 | meanings: |
127 | meanings: |
| 128 | </p> |
128 | </p> |
| 129 | |
129 | |
| 130 | <pre caption="Example emerge --search output"> |
130 | <pre caption="Example 'emerge --search' output"> |
| 131 | * net-print/cups-pdf |
131 | * net-print/cups-pdf |
| 132 | Latest version available: 1.5.2 |
132 | Latest version available: 1.5.2 |
| 133 | Latest version installed: [ Not Installed ] |
133 | Latest version installed: [ Not Installed ] |
| 134 | Size of downloaded files: 15 kB |
134 | Size of downloaded files: 15 kB |
| 135 | Homepage: http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/ |
135 | Homepage: http://cip.physik.uni-wuerzburg.de/~vrbehr/cups-pdf/ |
| … | |
… | |
| 252 | </pre> |
252 | </pre> |
| 253 | |
253 | |
| 254 | </body> |
254 | </body> |
| 255 | </subsection> |
255 | </subsection> |
| 256 | <subsection> |
256 | <subsection> |
| 257 | <title>Stub Packages</title> |
257 | <title>Metapackages</title> |
| 258 | <body> |
258 | <body> |
| 259 | |
259 | |
| 260 | <p> |
260 | <p> |
| 261 | Some packages in the Portage tree don't have any real content but are used to |
261 | Some packages in the Portage tree don't have any real content but are used to |
| 262 | install a collection of packages. For instance, the <c>kde</c> package will |
262 | install a collection of packages. For instance, the <c>kde</c> package will |
| … | |
… | |
| 445 | <subsection id="missingdependencies"> |
445 | <subsection id="missingdependencies"> |
| 446 | <title>Missing Dependencies</title> |
446 | <title>Missing Dependencies</title> |
| 447 | <body> |
447 | <body> |
| 448 | |
448 | |
| 449 | <pre caption="Portage warning about missing dependency"> |
449 | <pre caption="Portage warning about missing dependency"> |
| 450 | emerge: there are no ebuilds to satisfy ">=sys-devel/gcc-4.2-r4". |
450 | emerge: there are no ebuilds to satisfy ">=sys-devel/gcc-3.4.2-r4". |
| 451 | |
451 | |
| 452 | !!! Problem with ebuild sys-devel/gcc-3.4.2-r2 |
452 | !!! Problem with ebuild sys-devel/gcc-3.4.2-r2 |
| 453 | !!! Possibly a DEPEND/*DEPEND problem. |
453 | !!! Possibly a DEPEND/*DEPEND problem. |
| 454 | </pre> |
454 | </pre> |
| 455 | |
455 | |