On Friday 02 June 2006 01:29, Neil Bothwick wrote: > On Fri, 2 Jun 2006 00:48:21 +0200, Hemmann, Volker Armin wrote: > > > You'll need to add --update --deep to catch packages affected by the > > > changed USE flags. > > > > no you have not: > > > > emerge -a --newuse world > > > > >>> --newuse implies --update... adding --update to options. > > > > and I can't remember that this was different in the past. > > Yes it was. Adding --update pulled in extra packages, even though they > were the same version as installed. This was somewhat counter-intuitive, > so the new behaviour makes more sense. You should still need --deep > though.
--deep is dangerous! I have stopped using --deep ages ago. As an example: there is an --deep update for libFOO.1 to libFOO.1.1. You make this update which only shows up with --deep Suddenly all apps, linking to libFOO.1 are dead or crashy or acting weired. That happened to me several times. I see NO reason to use deep. Ever. Reduced the occurences where I have to use revdep-rebuilt to almost nil (except that expat tragedy some weeks ago. Man that sucked ;) ). -- [email protected] mailing list
