To reduce the work on the individual users, cut the hassle of supporting people who don't know what to do about broken libs, and make portage a more complete package management system, we should automatically run revdep-rebuild after every set of merges. This could result in an apparent major slowdown of portage, so I propose that it be hidden behind FEATURES="revdep-rebuild". A package management system shouldn't just leave broken programs out there on the system after it's done upgrading -- it should fix them, too. If _nothing_ else, at least run a scan for broken deps and tell the user to run revdep-rebuild at the end of the merge set.
Would rather specify metadata for each ebuild that can be used to determine if a rebuild is required...
yeah, this is not a good idea as is the NEEDED stuff that eradicator proposed on the mailing list and that scanelf now creates should be utilized instead
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
Consider this closed as WONTFIX, there are better proposals.
