On Fri, 2 Jun 2006 01:46:09 +0200, Hemmann, Volker Armin wrote: > --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.
Dropping --deep won't stop that happening, only delay it. sooner or later, one of your packages will need libFOO.1.1 and it will be installed. --deep doesn't cause this problem, it only affects the timing. > That happened to me several times. I see NO reason to use deep. Ever. How about this instance? The OP wants all packages affected by the profile change to be updated. Without --deep, that won't happen. > Reduced the occurences where I have to use revdep-rebuilt to almost nil > (except that expat tragedy some weeks ago. Man that sucked ;) ). I do a deep update every day, on various architectures. I run revdep-rebuild -p occasionally, just to make sure everything is consistent, it rarely picks up anything. --deep is an option, and I understand why you choose not to use it, but on this occasion it is necessary to accomplish the OP's goal. -- Neil Bothwick Machine-independent: Does not run on any existing machine.
signature.asc
Description: PGP signature
