Ok. I think I undestood. But, why do I need to use "revdep-rebuild" after "emerge --depclean"? I mean, "emerge --depclean" should unmerge just that dependences not necessary anymore by other packages. So, I suppose I don't need to rebuild nothing because I just unmerge dependences unused.
i.e. if I don't have any packages dependents of that dependences unmerged with "emerge --depclean", there's no dynamic link to update. Am I right? Do you undestand what I say?
Thanks!
Rafael Menezes Barreto
=====================
Brazil/PE - UFPE-CIn (rmb3)
2005/10/13, Bruno Lustosa <[EMAIL PROTECTED]>:
On 10/13/05, Rafael Barreto < [EMAIL PROTECTED]> wrote:The use of --depclean would not have erase only the dependences that are not more used for any applicatory one? If yes, why do I need to reconstruct the dependent applications of those dependences that I erased with "emerge -- depclean"? If no, please, clarify me about the functioning of "revdep-rebuild" that I did not understand its funcionality.
revdep-rebuild should be used when upgraded dependencies break a package.
for example, you have package A that has a dependency on library B.
you go and upgrade B, which happened to change its major version number.
now, package A doesn't work anymore, because the dynamic linker can't find the old lib anywhere.
revdep-rebuild should locate and rebuild package A to link it against the new library.
--
Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED]
Network Administrator/Web Programmer | ICQ: 1406477
Rio de Janeiro - Brazil |
