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