On 2/1/07, Bo Ørsted Andresen <[EMAIL PROTECTED]> wrote:
On Thursday 01 February 2007 00:20:12 Daiajo Tibdixious wrote: > I NEVER allow revdep-rebuild to rebuild ANYTHING. If I think the > "broken ..." actually match the list of packages, I'll emerge them > manually with --update. You haven't noticed the --package-names switch for revdep-rebuild, have you?
Not until after I got in the habit of doing it manually in another window. Besides I don't want the "broken ..." lines to scroll off the scroll back buffer, I like to keep them handy in case something goes wrong with the merge.
The main problem is that revdep-rebuild only fixes the case where the "(requires blah)" blah has a newer version lying around, so the broken .so can just be rebuilt to pick up the newer version. It doesn't handle the case where the broken .so is an orphan, or belongs to a package and is supposed to be manually deleted, or where blah simply does not exist anymore, and its that package that needs to be emerged. It also may be that package with the broken .so needs to be unmerged, rather than rebuilt, in the case where its something installed but not used any more. -- [email protected] mailing list
