Okay, recently I had to rebuild gtk2, upon which numerous packages depend.
Absolutely zero of those packages had anything to do with KDE.

Why, then, did make update in x11/gtk2 cause the complete deinstall and
subsequent eight hour rebuild of KDE3.4?

Has ANYONE looked at making "make update" a little more sane? say, building
the packages BEFORE nuking everything that's installed? So that in the cases
when it dies halfway through the update because a package maintainer didn't
properly test their package, only that package is affected, and not every
other package ficticiously (in the case of gtk2 and KDE) linked to it? I
think this is behavior that people would like, as it's quite inconvenient to
have a make update on some low-level lib rebuild mozilla 3 times, then
rebuild some other stuff that never needed that lib, then die, leaving some
other stuff deinstalled.

- Sean

--
 _
( ) ASCII Ribbon Campaign
 X
/ \ For Plain Text Email