| 1 |
On 11/30/2010 08:26 AM, Sebastian Pipping wrote: |
| 2 |
> * STAGE pkg_preinst (slot 2.7, version 2.7.1) |
| 3 |
> * STAGE pkg_prerm (version 2.7, slot 2.7) <---- |
| 4 |
> * STAGE pkg_postrm (version 2.7, slot 2.7) <---- |
| 5 |
> * STAGE pkg_postinst (slot 2.7, version 2.7.1) |
| 6 |
> |
| 7 |
> Shall we give that approach a try? |
| 8 |
|
| 9 |
It seems like a reasonable approach. |
| 10 |
|
| 11 |
> One case it doesn't seem to catch though is when you just run |
| 12 |
> |
| 13 |
> emerge -C dev-lang/python:X.Y |
| 14 |
> |
| 15 |
> on a machine where Python X.Y was installed with eselect_python_update() |
| 16 |
> still in place. Correct? |
| 17 |
|
| 18 |
True, but that's not nearly as annoying as when it happens during a |
| 19 |
series of updates. |
| 20 |
-- |
| 21 |
Thanks, |
| 22 |
Zac |
Archives