| 1 |
On Friday 02 June 2006 01:29, Neil Bothwick wrote: |
| 2 |
> On Fri, 2 Jun 2006 00:48:21 +0200, Hemmann, Volker Armin wrote: |
| 3 |
> > > You'll need to add --update --deep to catch packages affected by the |
| 4 |
> > > changed USE flags. |
| 5 |
> > |
| 6 |
> > no you have not: |
| 7 |
> > |
| 8 |
> > emerge -a --newuse world |
| 9 |
> > |
| 10 |
> > >>> --newuse implies --update... adding --update to options. |
| 11 |
> > |
| 12 |
> > and I can't remember that this was different in the past. |
| 13 |
> |
| 14 |
> Yes it was. Adding --update pulled in extra packages, even though they |
| 15 |
> were the same version as installed. This was somewhat counter-intuitive, |
| 16 |
> so the new behaviour makes more sense. You should still need --deep |
| 17 |
> though. |
| 18 |
|
| 19 |
--deep is dangerous! |
| 20 |
|
| 21 |
I have stopped using --deep ages ago. |
| 22 |
As an example: |
| 23 |
|
| 24 |
there is an --deep update for libFOO.1 to libFOO.1.1. |
| 25 |
|
| 26 |
You make this update which only shows up with --deep |
| 27 |
|
| 28 |
Suddenly all apps, linking to libFOO.1 are dead or crashy or acting weired. |
| 29 |
|
| 30 |
That happened to me several times. I see NO reason to use deep. Ever. |
| 31 |
|
| 32 |
Reduced the occurences where I have to use revdep-rebuilt to almost nil |
| 33 |
(except that expat tragedy some weeks ago. Man that sucked ;) ). |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives