| 1 |
On Tuesday 18 March 2008, Enrico Weigelt wrote: |
| 2 |
> BTW: if libexpat.so.0 was there before the update and now isn't, |
| 3 |
> there's an major bug in expat (either the ebuild or the source). |
| 4 |
|
| 5 |
There's no bug in expat, the OP is doing an *expat*upgrade*, which means |
| 6 |
that libexpat.so.0 was there before and libexpat.so.1 is there now. |
| 7 |
Thus any app that links explicitly to libexpat.so.0 is now broken. |
| 8 |
|
| 9 |
A source based distro like Gentoo runs this risk with every library |
| 10 |
upgrade and sometimes it hits a low level lib with deep dependencies |
| 11 |
like expat. There are only two possible solutions to this: |
| 12 |
|
| 13 |
1. Track the links between every app and every lib, and as soon as one |
| 14 |
is detected with a lib upgrade then fire an event to trigger a |
| 15 |
recompile of the linking app. This solution is so ugly, so error-prone |
| 16 |
that I cannot suffer it to live. |
| 17 |
|
| 18 |
2. Something like revdep-rebuild that scans the system looking for |
| 19 |
errors and is triggered manually by the user. |
| 20 |
|
| 21 |
Getting through these upgrades is a serious PITA. But at least on Gentoo |
| 22 |
we can fix it. Imagine using a binary distro where the packager didn't |
| 23 |
pick this up and you are left stranded with no easy way to fix it... |
| 24 |
|
| 25 |
-- |
| 26 |
Alan McKinnon |
| 27 |
alan dot mckinnon at gmail dot com |
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-user@l.g.o mailing list |
Archives