| 1 |
Remy Blank escribió: |
| 2 |
> Abraham Marín Pérez wrote: |
| 3 |
> |
| 4 |
>> Now think there's a new version available of LIB, let's say version 2.1, |
| 5 |
>> but the latest version of APP is still 1.0. If portage performed a deep |
| 6 |
>> update by default LIB would be rebuilt, but no APP, what would cause |
| 7 |
>> broken dependencies on APP (remember LIB is a dynamic library). However, |
| 8 |
>> is you don't update LIB unless you update also APP you will prevent this |
| 9 |
>> problem*. |
| 10 |
>> |
| 11 |
> |
| 12 |
> That's what revdep-rebuild is for. Update your LIB, run revdep-rebuild, |
| 13 |
> and if APP is really broken by the LIB update (it doesn't have to be), |
| 14 |
> it will be rebuilt. |
| 15 |
> |
| 16 |
> -- Remy |
| 17 |
> |
| 18 |
> |
| 19 |
That is indeed true, however, it will always be better keeping things |
| 20 |
right than breaking and fixing as a rule, don't you think? |
| 21 |
|
| 22 |
Abraham |
| 23 |
|
| 24 |
-- |
| 25 |
gentoo-user@g.o mailing list |
Archives