| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
William Hubbs wrote: |
| 5 |
>> As of Portage 2.2 the world set does not include the system |
| 6 |
>> set any more. If you want emerge --update --deep @world to |
| 7 |
>> update the system set too, you need to add @system to the new |
| 8 |
>> world_sets file in /var/lib/portage/. For more information on |
| 9 |
>> world_sets see man portage. |
| 10 |
> |
| 11 |
> This brings up a question. I have been doing updates this way: |
| 12 |
> |
| 13 |
> emerge -NDu @installed |
| 14 |
> |
| 15 |
> Does that do the same thing? |
| 16 |
|
| 17 |
It's mostly the same, except for things that are eligible for |
| 18 |
removal by emerge --depclean. I advise people to use @world and |
| 19 |
@system instead of @installed whenever possible since @installed |
| 20 |
makes it impossible for emerge to solve blockers by automatic |
| 21 |
uninstallation of blocked packages [1]. I've recently updated the |
| 22 |
documentation to warn about this undesirable side-effect [2]. |
| 23 |
|
| 24 |
[1] |
| 25 |
http://planet.gentoo.org/developers/zmedico/2008/05/09/blocking_package_file_collisions |
| 26 |
[2] http://sources.gentoo.org/viewcvs.py/portage?view=rev&rev=11318 |
| 27 |
- -- |
| 28 |
Thanks, |
| 29 |
Zac |
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 32 |
|
| 33 |
iEYEARECAAYFAkinlvwACgkQ/ejvha5XGaOv3gCgvdPJY/Nl8Hoxou12Kp2bw7jQ |
| 34 |
6r0AnjiYH/yHs3aC5W9k8KE4f1ySDtLX |
| 35 |
=p+ib |
| 36 |
-----END PGP SIGNATURE----- |
Archives