Ralf Stephan writes:
> I might be a bit too naive or hands-on -- I think portage
> or paludis should be able to tell you which upgrades that
> expat one will draw behind it. I don't know what would be
> required for implementation, though.
>
> In other words, even the existence of a separate revdep-rebuild
> tool is a design error, IMHO.
I agree, revdep-rebuild is a kludge. However, I do not think portage knows
which libraries a specific package needs, so it is necessary at the
moment.
It might not be impossible to implement, though. After the install step,
emerge could run ldd for each binary to check for its libraries, run
equery belongs to it and save the list of so found dependent packages
somewhere. When such a library is later about to be removed during the
cleaning phase, the dependent applications could be re-merged before
(assuming the configure step will use the newest library available - not
sure if this is entirely true).
I guess the equery step would slow things down a lot, but once done,
revdep-rebuild would not need to run ldd for every binary in the system
over and over again, which does not seem to be that elegant indeed.
Alex
--
[EMAIL PROTECTED] mailing list
