| 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.11 2003/11/30 14:36:05 swift Exp $ --> |
4 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.12 2003/12/03 13:42:05 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> |
| 14 | The main Portage tool that most users will use is <c>emerge</c>. We have already |
14 | The main Portage tool that most users will use is <c>emerge</c>. We have already |
| 15 | used it during the Gentoo installation and in the previous chapter, but we just |
15 | used it during the Gentoo installation and in the previous chapter, but we just |
| 16 | briefly explained how to use it. This chapter will elaborate on <c>emerge</c> |
16 | briefly explained how to use it. This chapter will elaborate on <c>emerge</c> |
| 17 | and learn you how to use <c>emerge</c> to fix all your software-related needs. |
17 | and learn you how to use <c>emerge</c> to fix all your software-related needs. |
| 18 | </p> |
18 | </p> |
| 19 | |
19 | |
| … | |
… | |
| 93 | reside. Take a look at, for instance, <path>app-office</path>: |
93 | reside. Take a look at, for instance, <path>app-office</path>: |
| 94 | </p> |
94 | </p> |
| 95 | |
95 | |
| 96 | <pre caption="Viewing a category"> |
96 | <pre caption="Viewing a category"> |
| 97 | # <i>cd app-office; ls --classify</i> |
97 | # <i>cd app-office; ls --classify</i> |
| 98 | abiword/ gnotime/ kmymoney2/ ooodi/ plan/ timestamp.x |
98 | abiword/ gnotime/ kmymoney2/ ooodi/ plan/ timestamp.x |
| 99 | dia/ gnucash/ koffice/ oooqs/ qhacc/ |
99 | dia/ gnucash/ koffice/ oooqs/ qhacc/ |
| 100 | dia2code/ gnumeric/ lxbank/ openoffice/ sc/ |
100 | dia2code/ gnumeric/ lxbank/ openoffice/ sc/ |
| 101 | facturalux/ ical/ lyx/ openoffice-bin/ scribus/ |
101 | facturalux/ ical/ lyx/ openoffice-bin/ scribus/ |
| 102 | gaby/ kbudget/ mdbtools/ openoffice-ximian/ siag/ |
102 | gaby/ kbudget/ mdbtools/ openoffice-ximian/ siag/ |
| 103 | gnofin/ khacc/ mrproject/ phprojekt/ texmacs/ |
103 | gnofin/ khacc/ mrproject/ phprojekt/ texmacs/ |
| 104 | </pre> |
104 | </pre> |
| 105 | |
105 | |
| 106 | <p> |
106 | <p> |
| 107 | Inside a category you will find the packages belonging to that category, with a |
107 | Inside a category you will find the packages belonging to that category, with a |
| 108 | seperate directory for each package. Let us take a look at the <c>openoffice</c> |
108 | separate directory for each package. Let us take a look at the <c>openoffice</c> |
| 109 | package: |
109 | package: |
| 110 | </p> |
110 | </p> |
| 111 | |
111 | |
| 112 | <pre caption="Viewing a package"> |
112 | <pre caption="Viewing a package"> |
| 113 | # <i>cd openoffice; ls --classify</i> |
113 | # <i>cd openoffice; ls --classify</i> |
| 114 | ChangeLog files/ openoffice-1.0.3-r1.ebuild openoffice-1.1.0-r2.ebuild |
114 | ChangeLog files/ openoffice-1.0.3-r1.ebuild openoffice-1.1.0-r2.ebuild |
| 115 | Manifest metadata.xml openoffice-1.1.0-r1.ebuild openoffice-1.1.0.ebuild |
115 | Manifest metadata.xml openoffice-1.1.0-r1.ebuild openoffice-1.1.0.ebuild |
| 116 | </pre> |
116 | </pre> |
| 117 | |
117 | |
| 118 | <p> |
118 | <p> |
| 119 | Remember that we told you that a Gentoo package is called an ebuild? Well, in |
119 | Remember that we told you that a Gentoo package is called an ebuild? Well, in |
| 120 | the example directory four of such ebuilds are stored. Their naming is |
120 | the example directory four of such ebuilds are stored. Their naming is |
| 121 | almost identical: they only differ in the version name. |
121 | almost identical: they only differ in the version name. |
| 122 | You are free to view the contents of such a package: they are plain scripts. We |
122 | You are free to view the contents of such a package: they are plain scripts. We |
| 123 | will not discuss it right now as it isn't important to know if you plan on just |
123 | will not discuss it right now as it isn't important to know if you plan on just |
Parent Directory
| 
Revision Log
| 
Patch