|
|
1 | <?xml version='1.0' encoding='UTF-8'?> |
|
|
2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
|
|
3 | |
| 1 | <!-- 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 --> |
| 2 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 3 | |
6 | |
| 4 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.6 2003/11/27 14:45:38 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.19 2004/01/09 10:52:18 dertobi123 Exp $ --> |
| 5 | |
8 | |
| 6 | <sections> |
9 | <sections> |
| 7 | <section> |
10 | <section> |
| 8 | <title>Obtaining Package Information</title> |
11 | <title>Obtaining Package Information</title> |
| 9 | <subsection> |
12 | <subsection> |
| … | |
… | |
| 12 | |
15 | |
| 13 | <p> |
16 | <p> |
| 14 | The main Portage tool that most users will use is <c>emerge</c>. We have already |
17 | 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 |
18 | 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> |
19 | 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. |
20 | and teach you how to use <c>emerge</c> to fix all your software-related needs. |
| 18 | </p> |
21 | </p> |
| 19 | |
22 | |
| 20 | <p> |
23 | <p> |
| 21 | <c>emerge</c> is the command used to install, remove, query and maintain |
24 | <c>emerge</c> is the command used to install, remove, query and maintain |
| 22 | software packages. It is a front-end for <c>ebuild</c>; people interested in |
25 | software packages. It is a front-end for <c>ebuild</c>; people interested in |
| … | |
… | |
| 103 | gnofin/ khacc/ mrproject/ phprojekt/ texmacs/ |
106 | gnofin/ khacc/ mrproject/ phprojekt/ texmacs/ |
| 104 | </pre> |
107 | </pre> |
| 105 | |
108 | |
| 106 | <p> |
109 | <p> |
| 107 | Inside a category you will find the packages belonging to that category, with a |
110 | 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> |
111 | separate directory for each package. Let us take a look at the <c>openoffice</c> |
| 109 | package: |
112 | package: |
| 110 | </p> |
113 | </p> |
| 111 | |
114 | |
| 112 | <pre caption="Viewing a package"> |
115 | <pre caption="Viewing a package"> |
| 113 | # <i>cd openoffice; ls --classify</i> |
116 | # <i>cd openoffice; ls --classify</i> |
| … | |
… | |
| 224 | |
227 | |
| 225 | <p> |
228 | <p> |
| 226 | You see something new? Yes, <e>downloaded files</e>. When you tell Portage to |
229 | 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 |
230 | install a package, it of course needs to have the necessary sources (or |
| 228 | precompiled packages) available. It therefore checks the contents of |
231 | precompiled packages) available. It therefore checks the contents of |
| 229 | <path>/usr/portage/distfiles</path> (for sourcecode) or |
232 | <path>/usr/portage/distfiles</path> (for source code) or |
| 230 | <path>/usr/portage/packages/All</path> (for precompiled packages) to see if the |
233 | <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 |
234 | necessary files are already available. If not, it downloads the necessary files |
| 232 | and places them in those directories. |
235 | and places them in those directories. |
| 233 | </p> |
236 | </p> |
| 234 | |
237 | |
|
|
238 | <!-- |
| 235 | <note> |
239 | <note> |
| 236 | Searching the Portage Tree, especially when using <c>--searchdesc</c>, is very |
240 | Searching the Portage Tree, especially when using <c>- -searchdesc</c>, is very |
| 237 | time consuming. There are other, more performant tools available. We will |
241 | 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 |
242 | describe those in the chapter on <uri link="?part=2&chap=7">Gentoolkit and |
| 239 | Other Tools</uri>. |
243 | Other Tools</uri>. |
| 240 | </note> |
244 | </note> |
|
|
245 | --> |
| 241 | |
246 | |
| 242 | </body> |
247 | </body> |
| 243 | </subsection> |
248 | </subsection> |
| 244 | <subsection> |
249 | <subsection> |
| 245 | <title>Viewing the ChangeLog</title> |
250 | <title>Viewing the ChangeLog</title> |
| 246 | <body> |
251 | <body> |
| 247 | |
252 | |
| 248 | <p> |
253 | <p> |
| 249 | While browsing through the Portage Tree, you saw that there was a ChangeLog for |
254 | 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 |
255 | each package. You can view the ChangeLog entries between the available version |
|
|
256 | and the installed version with <c>emerge</c> too. Use the |
| 251 | <c>--pretend --changelog</c> (<c>-pl</c> in short) options. As an example we |
257 | <c>--pretend --changelog</c> (<c>-pl</c> in short) options. As an example we |
| 252 | will view the ChangeLog entries for <c>gnumeric</c>: |
258 | will view the ChangeLog entries for <c>gnumeric</c>: |
| 253 | </p> |
259 | </p> |
| 254 | |
260 | |
| 255 | <pre caption="Viewing the ChangeLog entries for gnumeric"> |
261 | <pre caption="Viewing the ChangeLog entries for gnumeric"> |
| 256 | # <i>emerge --pretend --changelog gnumeric</i> |
262 | # <i>emerge --pretend --changelog gnumeric</i> |
|
|
263 | <comment>(Some output removed to improve readability)</comment> |
|
|
264 | *gnumeric-1.2.2 |
|
|
265 | |
|
|
266 | 27 Nov 2003; foser <foser@gentoo.org> gnumeric-1.2.2.ebuild : |
|
|
267 | New release, requested in #34492 |
|
|
268 | updated deps |
|
|
269 | |
|
|
270 | 12 Nov 2003; Jason Wever <weeve@gentoo.org> gnumeric-1.2.0.ebuild: |
|
|
271 | Marked stable on sparc, fixes bug #32405. |
|
|
272 | |
|
|
273 | 14 Oct 2003; Jason Wever <weeve@gentoo.org> gnumeric-1.0.8.ebuild: |
|
|
274 | Added ~sparc keyword. Fixes bug #31150. |
| 257 | </pre> |
275 | </pre> |
| 258 | |
276 | |
| 259 | </body> |
277 | </body> |
| 260 | </subsection> |
278 | </subsection> |
| 261 | </section> |
279 | </section> |
| … | |
… | |
| 298 | # <i>emerge --usepkg mirrorselect</i> |
316 | # <i>emerge --usepkg mirrorselect</i> |
| 299 | </pre> |
317 | </pre> |
| 300 | |
318 | |
| 301 | <p> |
319 | <p> |
| 302 | Now run <c>mirrorselect</c> to automatically select mirrors for you (it will |
320 | Now run <c>mirrorselect</c> to automatically select mirrors for you (it will |
| 303 | also setup Portage to use a mirror for the sourcecode): |
321 | also setup Portage to use a mirror for the source code): |
| 304 | </p> |
322 | </p> |
| 305 | |
323 | |
| 306 | <pre caption="Running mirrorselect"> |
324 | <pre caption="Running mirrorselect"> |
| 307 | # <i>mirrorselect -a -s3</i> |
325 | # <i>mirrorselect -a -s3</i> |
| 308 | </pre> |
326 | </pre> |
| … | |
… | |
| 336 | </subsection> |
354 | </subsection> |
| 337 | </section> |
355 | </section> |
| 338 | <section> |
356 | <section> |
| 339 | <title>Maintaining Software</title> |
357 | <title>Maintaining Software</title> |
| 340 | <subsection> |
358 | <subsection> |
| 341 | <title>Building or Prebuild?</title> |
359 | <title>Building or Prebuilt?</title> |
| 342 | <body> |
360 | <body> |
| 343 | |
361 | |
| 344 | <p> |
362 | <p> |
| 345 | Gentoo provides ebuilds, the Gentoo packages if you like. But when you want to |
363 | Gentoo provides ebuilds, the Gentoo packages if you like. But when you want to |
| 346 | install such an ebuild, you can choose between <e>building</e> the package, or |
364 | install such an ebuild, you can choose between <e>building</e> the package and |
| 347 | using a <e>prebuild</e> package. But what are the advantages/disadvantages of |
365 | using a <e>prebuilt</e> package. But what are the advantages/disadvantages of |
| 348 | both approaches, and can they be used next to each other? |
366 | both approaches, and can they be used next to each other? |
| 349 | </p> |
367 | </p> |
| 350 | |
368 | |
| 351 | <p> |
369 | <p> |
| 352 | As you probably have guessed, building packages takes a lot of time (especially |
370 | As you probably have guessed, building packages takes a lot of time (especially |
| … | |
… | |
| 357 | Of course, you can also define high optimization options (in the <c>CFLAGS</c> |
375 | Of course, you can also define high optimization options (in the <c>CFLAGS</c> |
| 358 | and <c>CXXFLAGS</c> variables) to compile the package with. |
376 | and <c>CXXFLAGS</c> variables) to compile the package with. |
| 359 | </p> |
377 | </p> |
| 360 | |
378 | |
| 361 | <p> |
379 | <p> |
| 362 | Using prebuild packages improves the installation time (as no more compilation |
380 | Using prebuilt packages improves the installation time (as no more compilation |
| 363 | is needed), but you will lose the advantages of the <c>USE</c> setting and the |
381 | is needed), but you will lose the advantages of the <c>USE</c> setting and the |
| 364 | <c>CFLAGS</c> & <c>CXXFLAGS</c> variables. |
382 | <c>CFLAGS</c> & <c>CXXFLAGS</c> variables. |
| 365 | </p> |
383 | </p> |
| 366 | |
384 | |
| 367 | <p> |
385 | <p> |
| 368 | As previously stated, prebuild packages are stored in the |
386 | As previously stated, prebuilt packages are stored in the |
| 369 | <path>/usr/portage/packages/All</path> directory, while the sourcecode of the |
387 | <path>/usr/portage/packages/All</path> directory, while the source code of the |
| 370 | packages are placed in <path>/usr/portage/distfiles</path>. If you have finished |
388 | packages is placed in <path>/usr/portage/distfiles</path>. If you have finished |
| 371 | installing a package you can remove the package or sourcecode from the |
389 | installing a package you can remove the package or source code from the |
| 372 | respective directory. However, you might want to keep the package/sourcecode of |
390 | respective directory. However, you might want to keep the package/source code of |
| 373 | the latest version, just in case you want to reinstall the package (so you don't |
391 | the latest version, just in case you want to reinstall the package (so you don't |
| 374 | have to redownload it). |
392 | have to redownload it). |
| 375 | </p> |
393 | </p> |
| 376 | |
394 | |
| 377 | </body> |
395 | </body> |
| … | |
… | |
| 380 | <title>Installing Software from Sources</title> |
398 | <title>Installing Software from Sources</title> |
| 381 | <body> |
399 | <body> |
| 382 | |
400 | |
| 383 | <p> |
401 | <p> |
| 384 | Okay, enough talking, let's cut to the chase. To install a package, you will use |
402 | Okay, enough talking, let's cut to the chase. To install a package, you will use |
| 385 | the <c>emerge</c> command. If you don't want to use any prebuild packages, you |
403 | the <c>emerge</c> command. If you don't want to use any prebuilt packages, you |
| 386 | can just use <c>emerge <package-name></c> or <c>emerge |
404 | can just use <c>emerge <package-name></c> or <c>emerge |
| 387 | <category>/<package-name></c>. As an example we'll install |
405 | <category>/<package-name></c>. As an example we'll install |
| 388 | <c>gnumeric</c>: |
406 | <c>gnumeric</c>: |
| 389 | </p> |
407 | </p> |
| 390 | |
408 | |
| 391 | <pre caption="Building gnumeric"> |
409 | <pre caption="Building gnumeric"> |
| 392 | # <i>emerge gnumeric</i> |
410 | # <i>emerge gnumeric</i> |
| 393 | </pre> |
411 | </pre> |
| 394 | |
412 | |
| 395 | <p> |
413 | <p> |
| 396 | This will download the sourcecode for you and unpacks, compiles and installs the |
414 | This will download the source code for you and unpacks, compiles and installs |
| 397 | package on your system. It will also do the same for all the dependencies. If |
415 | the package on your system. It will also do the same for all the dependencies. |
| 398 | you want to see what dependencies will be installed with it, use the |
416 | If you want to see what dependencies will be installed with it, use the |
| 399 | <c>--pretend</c> option (<c>-p</c> in short): |
417 | <c>--pretend</c> option (<c>-p</c> in short): |
| 400 | </p> |
418 | </p> |
| 401 | |
419 | |
| 402 | <pre caption="Pretending to build gnumeric"> |
420 | <pre caption="Pretending to build gnumeric"> |
| 403 | # <i>emerge --pretend gnumeric</i> |
421 | # <i>emerge --pretend gnumeric</i> |
| 404 | </pre> |
422 | </pre> |
| 405 | |
423 | |
| 406 | <p> |
424 | <p> |
| 407 | If you want to download the sourcecode of the package and its dependencies, |
425 | If you want to download the source code of the package and its dependencies, |
| 408 | but don't want to build the package, use the <c>--fetchonly</c> option |
426 | but don't want to build the package, use the <c>--fetchonly</c> option |
| 409 | (<c>-f</c> in short): |
427 | (<c>-f</c> in short): |
| 410 | </p> |
428 | </p> |
| 411 | |
429 | |
| 412 | <pre caption="Fetching sources for gnumeric"> |
430 | <pre caption="Fetching sources for gnumeric"> |
| … | |
… | |
| 438 | </p> |
456 | </p> |
| 439 | |
457 | |
| 440 | </body> |
458 | </body> |
| 441 | </subsection> |
459 | </subsection> |
| 442 | <subsection> |
460 | <subsection> |
| 443 | <title>Installing Prebuild Packages</title> |
461 | <title>Installing Prebuilt Packages</title> |
| 444 | <body> |
462 | <body> |
| 445 | |
463 | |
| 446 | <p> |
464 | <p> |
| 447 | When you want to install a prebuild package, you should use the <c>--usepkg</c> |
465 | When you want to install a prebuilt package, you should use the <c>--usepkg</c> |
| 448 | option (<c>-k</c> in short). This will use the binary package available in |
466 | option (<c>-k</c> in short). This will use the binary package available in |
| 449 | <path>/usr/portage/packages/All</path> <e>if</e> the package and the version of |
467 | <path>/usr/portage/packages/All</path> <e>if</e> the package and the version of |
| 450 | the application you want to install match. |
468 | the application you want to install match. |
| 451 | </p> |
469 | </p> |
| 452 | |
470 | |
| 453 | <pre caption="Installing a prebuild package for gnumeric"> |
471 | <pre caption="Installing a prebuilt package for gnumeric"> |
| 454 | # <i>emerge --usepkg gnumeric</i> |
472 | # <i>emerge --usepkg gnumeric</i> |
| 455 | </pre> |
473 | </pre> |
| 456 | |
474 | |
| 457 | <p> |
475 | <p> |
| 458 | If you want to use the binary package, even if the versions don't match, use |
476 | If you want to use the binary package, even if the versions don't match, use |
| 459 | <c>--usepkgonly</c> (<c>-K</c> in short). |
477 | <c>--usepkgonly</c> (<c>-K</c> in short). |
| 460 | </p> |
478 | </p> |
| 461 | |
479 | |
| 462 | <pre caption="Installing the prebuild package for gnumeric"> |
480 | <pre caption="Installing the prebuilt package for gnumeric"> |
| 463 | # <i>emerge --usepkgonly gnumeric</i> |
481 | # <i>emerge --usepkgonly gnumeric</i> |
| 464 | </pre> |
482 | </pre> |
| 465 | |
483 | |
| 466 | <!-- TODO When handbook goes life, comment out this parts until the mirrors have |
|
|
| 467 | been updated with online GRP packages. --> |
|
|
| 468 | <p> |
484 | <p> |
| 469 | If you don't have the prebuild package on your system yet, you can have |
485 | If you don't have the prebuilt package on your system yet, you can have |
| 470 | <c>emerge</c> download it from a mirror, defined in the <c>PORTAGE_BINHOST</c> |
486 | <c>emerge</c> download it from a mirror, defined in the <c>PORTAGE_BINHOST</c> |
| 471 | variable declared in <path>/etc/make.conf</path>. |
487 | variable declared in <path>/etc/make.conf</path>. |
| 472 | </p> |
488 | </p> |
| 473 | |
489 | |
| 474 | <p> |
490 | <p> |
| 475 | To download the binary package in case this package doesn't exist on |
491 | To download the binary package in case this package doesn't exist on |
| 476 | your system already, use <c>--getbinpkg</c> (<c>-g</c> in short): |
492 | your system already, use <c>--getbinpkg</c> (<c>-g</c> in short): |
| 477 | </p> |
493 | </p> |
| 478 | |
494 | |
| 479 | <pre caption="Downloading and installing a prebuild package for gnumeric"> |
495 | <pre caption="Downloading and installing a prebuilt package for gnumeric"> |
| 480 | # <i>emerge --getbinpkg gnumeric</i> |
496 | # <i>emerge --getbinpkg gnumeric</i> |
| 481 | </pre> |
497 | </pre> |
| 482 | |
498 | |
| 483 | <p> |
499 | <p> |
| 484 | This will download the package and the package-related information for you and |
500 | This will download the package and the package-related information for you and |
| 485 | install it on your system, together with the dependencies. If you want to see |
501 | install it on your system, together with the dependencies. If you want to see |
| 486 | what dependencies will be installed with it, use the <c>--pretend</c> option |
502 | what dependencies will be installed with it, use the <c>--pretend</c> option |
| 487 | (<c>-p</c> in short): |
503 | (<c>-p</c> in short): |
| 488 | </p> |
504 | </p> |
| 489 | |
505 | |
| 490 | <pre caption="Pretending to download the prebuild packages for gnumeric"> |
506 | <pre caption="Pretending to download the prebuilt packages for gnumeric"> |
| 491 | # <i>emerge --ginbinpkg --pretend gnumeric</i> |
507 | # <i>emerge --getbinpkg --pretend gnumeric</i> |
| 492 | </pre> |
508 | </pre> |
| 493 | |
509 | |
| 494 | <p> |
510 | <p> |
| 495 | You can also opt to download the prebuild package (and the package-related |
511 | You can also opt to download the prebuilt package (and the package-related |
| 496 | information) <e>without</e> checking the information on your local system and |
512 | information) <e>without</e> checking the information on your local system and |
| 497 | <e>without</e> using the prebuild package already on your system (if |
513 | <e>without</e> using the prebuilt package already on your system (if |
| 498 | applicable), use the <c>--getbinpkgonly</c> option (<c>-G</c> in short): |
514 | applicable), use the <c>--getbinpkgonly</c> option (<c>-G</c> in short): |
| 499 | </p> |
515 | </p> |
| 500 | |
516 | |
| 501 | <pre caption="Installing a prebuild package without using local information"> |
517 | <pre caption="Installing a prebuilt package without using local information"> |
| 502 | # <i>emerge --getbinpkgonly gnumeric</i> |
518 | # <i>emerge --getbinpkgonly gnumeric</i> |
| 503 | </pre> |
519 | </pre> |
| 504 | |
|
|
| 505 | <!-- TODO Up until here --> |
|
|
| 506 | |
520 | |
| 507 | <p> |
521 | <p> |
| 508 | You can also opt to install a specific version of a package. |
522 | You can also opt to install a specific version of a package. |
| 509 | For instance, if you want to install a gnumeric version older than 1.2 -- for |
523 | For instance, if you want to install a gnumeric version older than 1.2 -- for |
| 510 | any reason whatsoever :) you would type: |
524 | any reason whatsoever :) you would type: |
| … | |
… | |
| 517 | <p> |
531 | <p> |
| 518 | Other possibilities are of course ">" (later version) and "=" (the exact |
532 | Other possibilities are of course ">" (later version) and "=" (the exact |
| 519 | version). |
533 | version). |
| 520 | </p> |
534 | </p> |
| 521 | |
535 | |
|
|
536 | |
|
|
537 | </body> |
|
|
538 | </subsection> |
|
|
539 | <subsection> |
|
|
540 | <title>Working with Dependencies</title> |
|
|
541 | <body> |
|
|
542 | |
|
|
543 | <p> |
|
|
544 | Portage has an extensive support for dependency handling. Although you usually |
|
|
545 | don't need to even think about this (as dependencies are automatically handled |
|
|
546 | by Portage) some users might want to know how you can work with <c>emerge</c> |
|
|
547 | and dependencies. |
|
|
548 | </p> |
|
|
549 | |
|
|
550 | <p> |
|
|
551 | For instance, if you want Portage to pretend that none of the dependencies of a |
|
|
552 | package are installed, you can use <c>--emptytree</c> (<c>-e</c> in short). This |
|
|
553 | is useful with <c>--pretend</c> to display a complete tree of dependencies for |
|
|
554 | any particular package. Without <c>--pretend</c>, <c>emerge</c> will (re)compile |
|
|
555 | all listed packages. However, <c>glibc</c> will <e>not</e> be listed as |
|
|
556 | dependency for safety reasons. |
|
|
557 | </p> |
|
|
558 | |
|
|
559 | <pre caption="Show all dependencies of gnumeric"> |
|
|
560 | # <i>emerge --emptytree --pretend gnumeric</i> |
|
|
561 | </pre> |
|
|
562 | |
|
|
563 | <p> |
|
|
564 | Another argument is <c>--nodeps</c>, which will ask Portage to try install the |
|
|
565 | given package without taking care of the dependencies. It is trivial that this |
|
|
566 | can lead to failures. |
|
|
567 | </p> |
|
|
568 | |
|
|
569 | <pre caption="Installing gnumeric without taking care of the dependencies"> |
|
|
570 | # <i>emerge --nodeps gnumeric</i> |
|
|
571 | </pre> |
|
|
572 | |
|
|
573 | <p> |
|
|
574 | The opposite of <c>--nodeps</c> is <c>--onlydeps</c>, which will have Portage |
|
|
575 | install all dependencies of a given package, but not the package itself: |
|
|
576 | </p> |
|
|
577 | |
|
|
578 | <pre caption="Installing the dependencies of gnumeric"> |
|
|
579 | # <i>emerge --onlydeps gnumeric</i> |
|
|
580 | </pre> |
| 522 | |
581 | |
| 523 | </body> |
582 | </body> |
| 524 | </subsection> |
583 | </subsection> |
| 525 | <subsection> |
584 | <subsection> |
| 526 | <title>Updating your System</title> |
585 | <title>Updating your System</title> |
| … | |
… | |
| 589 | </li> |
648 | </li> |
| 590 | <li> |
649 | <li> |
| 591 | <e>R</e> (reemerge) The package isn't new, but needs to be reemerged |
650 | <e>R</e> (reemerge) The package isn't new, but needs to be reemerged |
| 592 | </li> |
651 | </li> |
| 593 | <li> |
652 | <li> |
| 594 | <e>F</e> (fetch) The package requires that you download the sourcecode |
653 | <e>F</e> (fetch) The package requires that you download the source code |
| 595 | manually (for instance due to licencing issues) |
654 | manually (for instance due to licencing issues) |
| 596 | </li> |
655 | </li> |
| 597 | <li> |
656 | <li> |
| 598 | <e>U</e> (update) The package already exists on your system but will be |
657 | <e>U</e> (update) The package already exists on your system but will be |
| 599 | upgraded |
658 | upgraded |
| … | |
… | |
| 653 | Portage doesn't verify if a package is a dependency for another |
712 | Portage doesn't verify if a package is a dependency for another |
| 654 | installed package. It also doesn't warn you if the package is part of |
713 | installed package. It also doesn't warn you if the package is part of |
| 655 | <e>system</e>, i.e. a core application necessary for the correct functioning of |
714 | <e>system</e>, i.e. a core application necessary for the correct functioning of |
| 656 | your system! |
715 | your system! |
| 657 | </warn> |
716 | </warn> |
|
|
717 | |
|
|
718 | <p> |
|
|
719 | Once the unmerge begins you will see a long list of filenames belonging to the |
|
|
720 | package. Some of these filenames will have a flag displayed to the |
|
|
721 | left of the filename. The flags <c>!mtime</c>, <c>!empty</c>, and <c>cfgpro</c> |
|
|
722 | specify reasons why certain files are not being removed while the package is. |
|
|
723 | Files listed without any of these three flags are removed from the |
|
|
724 | filesystem successfully. The three flags specify the following reasons: |
|
|
725 | </p> |
|
|
726 | |
|
|
727 | <ul> |
|
|
728 | <li> |
|
|
729 | <c>!mtime</c> : The listed file has been changed since it was installed, |
|
|
730 | probably by you or some tool |
|
|
731 | </li> |
|
|
732 | <li> |
|
|
733 | <c>!empty</c> : The listed directory is not empty |
|
|
734 | </li> |
|
|
735 | <li> |
|
|
736 | <c>cfgpro</c> : This file is located inside a protected directory and will |
|
|
737 | not be touched for safety |
|
|
738 | </li> |
|
|
739 | </ul> |
| 658 | |
740 | |
| 659 | </body> |
741 | </body> |
| 660 | </subsection> |
742 | </subsection> |
| 661 | </section> |
743 | </section> |
| 662 | <section> |
744 | <section> |
| … | |
… | |
| 739 | the same format as is used in <path>/usr/portage/profiles/package.mask</path>). |
821 | the same format as is used in <path>/usr/portage/profiles/package.mask</path>). |
| 740 | </p> |
822 | </p> |
| 741 | |
823 | |
| 742 | <p> |
824 | <p> |
| 743 | Do <e>not</e> alter the <path>/usr/portage/profiles/package.mask</path> file as |
825 | Do <e>not</e> alter the <path>/usr/portage/profiles/package.mask</path> file as |
| 744 | all changes are undone the next time you update your Portage tree. |
826 | all changes are undone the next time you update your Portage tree. If you want |
|
|
827 | to hardmask a package create <path>/etc/portage/package.mask</path> and list the |
|
|
828 | package in it (use the same format as mentioned above). |
| 745 | </p> |
829 | </p> |
| 746 | |
830 | |
| 747 | <p> |
831 | <p> |
| 748 | Another trick to circumvent the "masked package" problem is to install the |
832 | Another trick to circumvent the "masked package" problem is to install the |
| 749 | package using the full path. This will ignore both the <c>ACCEPT_KEYWORD</c> |
833 | package using the full path. This will ignore both the <c>ACCEPT_KEYWORD</c> |
Parent Directory
| 
Revision Log
| 
Patch