On Fri, Nov 13, 2009 at 3:13 PM, Neil Bothwick <n...@digimed.co.uk> wrote: > On Fri, 13 Nov 2009 15:00:33 -0800, Mark Knecht wrote: > >> > >> > Was it an endless loop? AIUI you emerged twice and the >> > @preserved-rebuild count decreased. In my experience, it can >> > occasionally take a few runs to clear the list, sometimes subsequent >> > runs add packages that were not there previously, but it all clears >> > in the end, I have NEVER had to resort to deleting the registry file >> > manually. > >> If I don't run it forever then I don't think I can say it would never >> clear up. Can't prove a negative, etc. > > When you get identical package lists on subsequent runs, I think it's > fair to say it won't fix itself. This has never happened to me. > >> However, it did get to the point where it was complaining about two >> packages and the number of files to be rebuilt went (IIRC) 52, 50, 50, >> so I decide since it was rebuilding 50 packages the 2nd & 3rd times it >> wasn't going to improve. Might not be true though. > > I think it is being over-cautious, which results in packages being > rebuilt multiple time unnecessarily, but I's rather give it the chance to > fix itself. That said, I've never had a list anything like 50 packages > long, but I do update frequently. > It wasn't that I had 50 packages in the emerge -DuN @world. That was something like 10. It was after that finished and I ran @preserved-rebuild that it said 50 packages were effected by something it found, but those 50 were all dependent on just one or two packages that Alan was suggesting to me are held in the preserved database file, or so I think.
Again, you know me...basically a flunky just trying to use my tool box to play music even if I don't know how the tool box works... - Mark
