On Sun, 11 Nov 2012 09:48:16 -0600 Dale <rdalek1...@gmail.com> wrote:
> Alan McKinnon wrote: > > On Sat, 10 Nov 2012 17:29:11 -0600 > > Dale <rdalek1...@gmail.com> wrote: > > > >> I have noticed that when I do a KDE upgrade and something acts a > >> little funny, a emerge -e world generally fixes it. I do wish there > >> was a way to know what needed to be emerged again without doing > >> everything. OP, you could try doing a emerge -e ksplash with the -t > >> option and sort of see what it depends on that way. Then try to > >> emerge those packages first to see if it helps. For what it is > >> worth, I did the upgrade and the only problem I ran into was my > >> saved session got messed up. I had to set things up and save it > >> again, I haven't logged out and back in yet so I hope that fixes > >> that problem. Any Linux geeks know how to fix this sort of thing > >> without a emerge -e world? > > short answer: usually, you can't > > > > longer answer: you can't, because software usually can't detect the > > answer. > > > > revdep-rebuild does a fine job of finding what it was designed to > > do - reverse dependencies that are now broken. > > > > So if app A uses lib B directly which uses lib C directly, and lib C > > got updated, revdep-rebuild will discover if the new C is > > incompatible with the current B. Re-emerge B and it usually just > > manages to do the right thing. > > > > Weird issues often crop up when you have plug-in modules that are > > loaded dynamically at runtime. Revdep-rebuild can't find these as > > they don't show up in ldd, the app itself figures out what modules > > it wants to load then tries, so if something is broken there, well > > you find that out when you run the app. > > > > emerge -e world is the only way I know to to fix these things with > > any certainty. Binary distro by the way usually don't have this > > problem happen to them, because with those lib C doesn't suddenly > > get ripped out underneath B and replaced ;-) > > > > > > > > That figures. So, emerge -e world it is from time to time then. > > Binaries may not have this problem but they sure do have their share > of other problems. lol haha, you mean like when you have lib v1 and you want to run an app (from the distro repo!) and it requires lib v2? We all know what that's like, and basically then you are SOL... :-) -- Alan McKinnon alan.mckin...@gmail.com
