| 1 |
But isn't that a little dangerous? What if you emerge -U when you install |
| 2 |
new packages? unmerging anything installed will result in you losing stuff |
| 3 |
that might have been installed previously and only upgraded with your |
| 4 |
botched emerge. |
| 5 |
|
| 6 |
|
| 7 |
On Wed, Apr 14, 2004 at 11:04:29AM -0300, lema wrote: |
| 8 |
> Sorry, I reply to Mike instead of the list. |
| 9 |
> |
| 10 |
> A slightly different issue, that could improve emerge usage. |
| 11 |
> Suppose you do an emerge with many dependencies (eg. 'emerge gnome') but |
| 12 |
> in the process something fails (lets say apmd don't emerge). It could be |
| 13 |
> useful to be able to do a kind of "rollback" (unmerging the so far |
| 14 |
> merged dependencies for gnome) instead of aborting directly from the |
| 15 |
> emerge session. I think this could be far more ease to implement ( I did |
| 16 |
> it by hand keeping track of what emerge -p gnome said before). |
| 17 |
> Just another idea. |
| 18 |
> Fabi?n |
Archives