If a package no longer in the portage tree is broken, revdep-rebuild will fail and the user will have to manually fix the problem, either by removing the package from .revdep-rebuild-4 or emerging an updated version of the package. Suggested attitude: a)if a different version of such package exists in portage, revdep-rebuild should emerge that one instead (remember to issue a 5 seconds warning and allow the user to disable this behaviour) b)if such package doesn't exist at all, it should be skipped and a warning should be issued.
revdep-rebuild already supports this behavior. If you run 'revdep-rebuild -X' it will use the name of the package and will emerge the latest version available according to your ACCEPT_KEYWORDS variable.
sry, I saw the "bug depends on 62644" just right after I clicked on the commit button Yours Matt
*** This bug has been marked as a duplicate of 22161 ***
