| 1 |
On 17-04-2009 17:58:47 +0200, Markus Duft wrote: |
| 2 |
> ok... following this upgrade path from an old prefix should work: |
| 3 |
> |
| 4 |
> emerge -avuDe world |
| 5 |
> emerge -avuD world |
| 6 |
> |
| 7 |
> :) |
| 8 |
> |
| 9 |
> this merges the last hybrid portage (the other one is masked by EAPI, at |
| 10 |
> least thats true for me...(??)), and after that uses that portage to |
| 11 |
> reinstall/update all packages. after that a normal update will give the |
| 12 |
> newest portage. |
| 13 |
> |
| 14 |
> if the new portage is not masked by EAPI, that would be a problem. you'd |
| 15 |
> need to manually mask it while doing the -avuDe world. |
| 16 |
> |
| 17 |
> the only problem is that the -avuDe world should never be stopped, since |
| 18 |
> otherwise a recalculation of dependencies will cause the non-hybrid |
| 19 |
> portage to be merged, which will (possibly) destroy (some) installed |
| 20 |
> packages - or at least prevents upgrades to run through smooth. |
| 21 |
> |
| 22 |
> Should we provide some docs somewhere about this? |
| 23 |
|
| 24 |
We can, however, I fear that within not too much time, the last hybrid |
| 25 |
version of portage will have to go, as I can't generate a manifest for |
| 26 |
it any more. This means there's no way to do it like you did here, for |
| 27 |
people that need. Our only alternative is cleaning up environment.bz2, |
| 28 |
I'm affraid. |
| 29 |
|
| 30 |
|
| 31 |
-- |
| 32 |
Fabian Groffen |
| 33 |
Gentoo on a different level |
Archives