On Mon, Mar 12, 2012 at 1:53 AM, Helmut Jarausch <jarau...@igpm.rwth-aachen.de> wrote: > Hi, > > even the most recent portage 2.2.0_alpha90 has difficulties handling > @preserved-rebuild especially after many binary emerge operations. > It tries to re-emerge the same packages again and again. > As a last resort I have to remove /var/lib/portage/preserved_libs_registry. > But after that the old libraries are still hanging around and revdep-rebuild > won't since there aren't any broken libs or binaries just some which are > linked against old versions. > Is there an elegant way to find these old libraries? (Removing them would > alert revdep-rebuild afterwards). > > Thanks for a hint, > Helmut. >
Hi, I haven't tried Neil's method so I cannot comment on that. Personally I actually start with revdep-rebuild -ip to see if anything is flagged. If there is then I run equery depends whatever-was-found and equery belongs whatever-was-found to see what uses (if anything) and what owns (if anything) whatever-was-found. If nothing uses or owns then I delete it by hand. It's labor intensive. Possibly Neil's metthod gets around some of that. However I've used this for years and seldom had too many things to clean up, and what I have had wasn't too difficult to work though. There were some issue with Flash on one of my machine last week that took awhile to dig through. I try to do my machine once every couple of months. HTH, Mark
