| 1 |
Abraham Marín Pérez wrote: |
| 2 |
> Now think there's a new version available of LIB, let's say version 2.1, |
| 3 |
> but the latest version of APP is still 1.0. If portage performed a deep |
| 4 |
> update by default LIB would be rebuilt, but no APP, what would cause |
| 5 |
> broken dependencies on APP (remember LIB is a dynamic library). However, |
| 6 |
> is you don't update LIB unless you update also APP you will prevent this |
| 7 |
> problem*. |
| 8 |
|
| 9 |
That's what revdep-rebuild is for. Update your LIB, run revdep-rebuild, |
| 10 |
and if APP is really broken by the LIB update (it doesn't have to be), |
| 11 |
it will be rebuilt. |
| 12 |
|
| 13 |
-- Remy |
Archives