Hemmann, Volker Armin schreef: > direct experience. I have seen xine and mplayer break multiple times > or KDE loosing its themes,
Yeah, but mplayer breaks if your breathe on it too hard, and Xine is not all that much better (though better than gstreamer, and overall the best in terms of stability). New releases of KDE often are so buggy that you 1) *have* to upgrade whatever is available to get the bugfixes and 2) can't really be certain that any breakage is related to library updates (or worse yet, only *partial* library updates, not all relevant libraries, because all relevant libraries don't necessarily have updates available at the same time), rather than just one of the bugs. 'Loosing its themes' I've never seen (but then again I try to avoid using KDE as much as possible), but of all the things that KDE might (and has, in my experience) lose after a full, partial, or deep upgrade, "themes" are about the last on my "oh, no, I'm now hysterical" list. But that's just me. > because of qt updates or wesnoth. And that are the ones I remember > without to much brain work. That is why I am healed from --deep > updates OK. It's your box. In my opinion, it's impossible to avoid stuff breaking (on a Gentoo/source-based distro) box; libraries and applications depending on those libraries are *going* to be mis-matched at some point or another, sometimes quite often. It's usually temporary, and usually easy to fix: recompile the app against the updated library, as I did yesterday for Beagle, or run <name_your_language>.updater-- I just found there's an ocaml-updater script; who knew? or run the config utility for gcc, or java or whatever is the problem today. Or switch apps, which is a little-thought-of but often quite effective solution. Helps to be a bit flexible, though, of course, which everybody does not have the liberty to be. But if not, then just stick with stable and don't upgrade at all, --deep or otherwise. Holly -- gentoo-user@gentoo.org mailing list
