| 1 |
On Fri, 6 Jan 2006 12:57:07 +0530, Abhay Kedia wrote: |
| 2 |
|
| 3 |
> > version _after_ the new version has been merged into place. One |
| 4 |
> > possible solution would be to have a special feature that, when |
| 5 |
> > enabled, allows portage to automatically unmerge an old version |
| 6 |
> > _before_ the new one is installed (with protection against unmerging |
| 7 |
> > system packages of course). |
| 8 |
> > |
| 9 |
> That is no solution AT ALL!!! What if portage unmerges the package and |
| 10 |
> while compiling the new package it gets into an error? You are left |
| 11 |
> with no installed packages. |
| 12 |
|
| 13 |
Portage could remove the old package after compilation |
| 14 |
|
| 15 |
ebuild package-new.ebuild compile |
| 16 |
ebuild package-old.ebuild unmerge |
| 17 |
ebuild package-new.ebuild install |
| 18 |
|
| 19 |
This would reduce the chances of something bad happening, but not remove |
| 20 |
it altogether. So it would have to package up the old files first and |
| 21 |
re-install them if the new install failed, more than a little messy IMO. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
Borg -- James Borg -- licensed to assimilate. |
Archives