| 1 |
On Mon, 06 Aug 2007 12:40:38 +0200, Remy Blank wrote: |
| 2 |
|
| 3 |
> Even worse, if you don't know that the LIB update will break APP, you |
| 4 |
> might not notice immediately that APP is broken, or you might only get |
| 5 |
> some strange results from APP. That's where revdep-rebuild steps in: it |
| 6 |
> can tell you that APP is broken, and what's needed to fix it. So you're |
| 7 |
> better off running it consistently after your regular updates. |
| 8 |
|
| 9 |
If the update is likely to cause such breakage, the ebuild should warn of |
| 10 |
this, as many do, giving the exact command to run to fix such breakage |
| 11 |
before it becomes a problem. |
| 12 |
|
| 13 |
Such breakages are inevitable on a source based system using dynamic |
| 14 |
libraries. Fortunately, being a source based system makes the fix simple. |
| 15 |
Try dealing with the same problems on a binary distro. |
| 16 |
|
| 17 |
|
| 18 |
-- |
| 19 |
Neil Bothwick |
| 20 |
|
| 21 |
If at first you don't succeed, call it Windows NT. |
Archives