| 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.13 2003/12/04 22:26:19 swift Exp $ --> |
4 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.14 2003/12/16 17:59:46 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 teach you how to use <c>emerge</c> to fix all your software-related needs. |
17 | and teach you how to use <c>emerge</c> to fix all your software-related needs. |
| 18 | </p> |
18 | </p> |
| 19 | |
19 | |
| … | |
… | |
| 218 | |
218 | |
| 219 | <p> |
219 | <p> |
| 220 | As you can see, the output of <c>emerge</c> informs you about the category and |
220 | As you can see, the output of <c>emerge</c> informs you about the category and |
| 221 | name of the package, the available version, the currently installed version, |
221 | name of the package, the available version, the currently installed version, |
| 222 | the size of the downloaded files, the homepage and the small description. |
222 | the size of the downloaded files, the homepage and the small description. |
| 223 | </p> |
223 | </p> |
| 224 | |
224 | |
| 225 | <p> |
225 | <p> |
| 226 | You see something new? Yes, <e>downloaded files</e>. When you tell Portage to |
226 | You see something new? Yes, <e>downloaded files</e>. When you tell Portage to |
| 227 | install a package, it of course needs to have the necessary sources (or |
227 | install a package, it of course needs to have the necessary sources (or |
| 228 | precompiled packages) available. It therefore checks the contents of |
228 | precompiled packages) available. It therefore checks the contents of |
| 229 | <path>/usr/portage/distfiles</path> (for sourcecode) or |
229 | <path>/usr/portage/distfiles</path> (for sourcecode) or |
| 230 | <path>/usr/portage/packages/All</path> (for precompiled packages) to see if the |
230 | <path>/usr/portage/packages/All</path> (for precompiled packages) to see if the |
| 231 | necessary files are already available. If not, it downloads the necessary files |
231 | necessary files are already available. If not, it downloads the necessary files |
| 232 | and places them in those directories. |
232 | and places them in those directories. |
| 233 | </p> |
233 | </p> |
| 234 | |
234 | |
|
|
235 | <!-- |
| 235 | <note> |
236 | <note> |
| 236 | Searching the Portage Tree, especially when using <c>--searchdesc</c>, is very |
237 | Searching the Portage Tree, especially when using <c>- -searchdesc</c>, is very |
| 237 | time consuming. There are other, more performant tools available. We will |
238 | time consuming. There are other, more performant tools available. We will |
| 238 | describe those in the chapter on <uri link="?part=2&chap=7">Gentoolkit and |
239 | describe those in the chapter on <uri link="?part=2&chap=7">Gentoolkit and |
| 239 | Other Tools</uri>. |
240 | Other Tools</uri>. |
| 240 | </note> |
241 | </note> |
|
|
242 | --> |
| 241 | |
243 | |
| 242 | </body> |
244 | </body> |
| 243 | </subsection> |
245 | </subsection> |
| 244 | <subsection> |
246 | <subsection> |
| 245 | <title>Viewing the ChangeLog</title> |
247 | <title>Viewing the ChangeLog</title> |
| 246 | <body> |
248 | <body> |
| 247 | |
249 | |
| 248 | <p> |
250 | <p> |
| 249 | While browsing through the Portage Tree, you saw that there was a ChangeLog for |
251 | While browsing through the Portage Tree, you saw that there was a ChangeLog for |
| 250 | each package. You can view this ChangeLog with <c>emerge</c> too. Use the |
252 | each package. You can view this ChangeLog with <c>emerge</c> too. Use the |
| 251 | <c>--pretend --changelog</c> (<c>-pl</c> in short) options. As an example we |
253 | <c>--pretend --changelog</c> (<c>-pl</c> in short) options. As an example we |
| 252 | will view the ChangeLog entries for <c>gnumeric</c>: |
254 | will view the ChangeLog entries for <c>gnumeric</c>: |
| 253 | </p> |
255 | </p> |
| 254 | |
256 | |
| 255 | <pre caption="Viewing the ChangeLog entries for gnumeric"> |
257 | <pre caption="Viewing the ChangeLog entries for gnumeric"> |
Parent Directory
| 
Revision Log
| 
Patch