| 1 |
On 14-07-2008 20:23:39 -0500, Jeremy Olexa wrote: |
| 2 |
> Peter Ansell wrote: |
| 3 |
>> What happens when you try emerge --update --deep --newuse world? |
| 4 |
>> |
| 5 |
>> --update on its own doesn't pull in all dependencies, where python is |
| 6 |
>> almost certain to be a deep dependency of one of the world emerged |
| 7 |
>> packages. |
| 8 |
> |
| 9 |
> Bingo, and since python is a dep of portage. It doesn't need to be in |
| 10 |
> the world file. Along with all the other "Implicit System Deps" |
| 11 |
|
| 12 |
To repeat Jeremy's argument with other words: |
| 13 |
In the bootstrap process we only emerge --oneshot packages that are in |
| 14 |
the "system" set. You don't want them to be in your "world" set, as |
| 15 |
we're only emerging them explicitly because at that early stage Portage |
| 16 |
can't determine the correct order of the packages. Lateron in the |
| 17 |
process we "emerge system", which is then recorded in your world-file. |
| 18 |
Hence, implicitly all system packages are in your world-file. |
| 19 |
|
| 20 |
As others pointed out, you need --deep to really update everything which |
| 21 |
can be updated. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Fabian Groffen |
| 26 |
Gentoo on a different level |
| 27 |
-- |
| 28 |
gentoo-alt@l.g.o mailing list |
Archives