* Alan McKinnon <[EMAIL PROTECTED]> wrote: > 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.
If an upgrade breaks primary things, it's simply broken. You can now choose, whether the bug is expat or the ebuild/portage. > 2. Something like revdep-rebuild that scans the system looking for > errors and is triggered manually by the user. This is also ugly and error-prone. After every slightest upgrade you have to fear nothing's running anymore and everything has to be rebuilt first. If downtimes don't matter, fine. But for critical systems, this is very dangerous. Why not modeling/storing the *runtime* dependencies and doing an *clean* MVCC ? Isn't this what slotting was meant for ? ;-P > 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... Then the package manager's obviously broken ... cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ --------------------------------------------------------------------- -- gentoo-user@lists.gentoo.org mailing list
