| 1 |
Ok. I think I undestood. But, why do I need to use "revdep-rebuild" after |
| 2 |
"emerge --depclean"? I mean, "emerge --depclean" should unmerge just that |
| 3 |
dependences not necessary anymore by other packages. So, I suppose I don't |
| 4 |
need to rebuild nothing because I just unmerge dependences unused. i.e. if I |
| 5 |
don't have any packages dependents of that dependences unmerged with "emerge |
| 6 |
--depclean", there's no dynamic link to update. Am I right? Do you undestand |
| 7 |
what I say? |
| 8 |
Thanks! |
| 9 |
Rafael Menezes Barreto |
| 10 |
===================== |
| 11 |
Brazil/PE - UFPE-CIn (rmb3) |
| 12 |
2005/10/13, Bruno Lustosa <bruno.lists@×××××.com>: |
| 13 |
|
| 14 |
> On 10/13/05, Rafael Barreto <rafaelmbarreto@×××××.com> wrote: |
| 15 |
> > |
| 16 |
> > The use of --depclean would not have erase only the dependences that are |
| 17 |
> > not more used for any applicatory one? If yes, why do I need to reconstruct |
| 18 |
> > the dependent applications of those dependences that I erased with "emerge |
| 19 |
> > -- depclean"? If no, please, clarify me about the functioning of |
| 20 |
> > "revdep-rebuild" that I did not understand its funcionality. |
| 21 |
> > |
| 22 |
> |
| 23 |
> revdep-rebuild should be used when upgraded dependencies break a package. |
| 24 |
> for example, you have package A that has a dependency on library B. |
| 25 |
> you go and upgrade B, which happened to change its major version number. |
| 26 |
> now, package A doesn't work anymore, because the dynamic linker can't find |
| 27 |
> the old lib anywhere. |
| 28 |
> revdep-rebuild should locate and rebuild package A to link it against the |
| 29 |
> new library. |
| 30 |
> |
| 31 |
> -- |
| 32 |
> Bruno Lustosa, aka Lofofora | Email: bruno@×××××××.net |
| 33 |
> Network Administrator/Web Programmer | ICQ: 1406477 |
| 34 |
> Rio de Janeiro - Brazil | |
Archives