"(see the recent "Rolling upgrades" thread)" ...excuse me but where can i find this thread to read about such automated procedures?? thanks in advance...
On 24/08/07, Alex Schuster <[EMAIL PROTECTED]> wrote: > > Hi there! > > The last expat update was an example of something that annoys me about > gentoo. I usually do world updates every few days, mostly without > trouble. I only tend to forget to restart services, but even for this > there is an automatic solution now (see the recent "Rolling upgrades" > thread). I have even compiled X.org or a new KDE while having KDE > running. > > But then, there are things like the expat update. This happens seldomly, > but if it does, it's rather annoying. Maybe I have become too comfortable > with updating along the way, while working with the system, but usually > it works fine. But in the case of expat, I got a message _after_ it was > updated that I have to revdep-rebuild some stuff (and I know I should > read these messages, but at first I just did not notice until the first > problems hapened). > > In the meantime, much of the system just does not work any more. It took > me two days on a not-so-fast PC until revdep-rebuild was done (skipping > koffice) and I had kmail running again. It was no big problem, I had the > time, and had downgraded expat before when I needed my whole system, but > still. > > So, what I would like is some way of being informed that the next update > of some software would cause major trouble and break many things, leaving > the system possibly unusable for a while, and the choice of not doing so > until I have the time to deal with it. Something like a --force option to > emerge, without which things like expat would not be updated. > > I know, it's not that simple to decide which updates are that critical, > but I think at least in the case of expat we agree that this was a > problem, as e.g. whole KDE was affected. > > A soution might be to slot expat, and issue a > revdep-rebuild --library=/usr/lib/libexpat.so.0.5.0 afterwards. This > makes all the not-yet-broken apps use the new version, which could be > unmerged afterwards. In the meantime, all would be working fine. > > What do you think? > > Alex > -- > [EMAIL PROTECTED] mailing list > >
