On Tue, 2005-11-29 at 09:51 +0100, Gregorio Guidi wrote: > On Tuesday 29 November 2005 03:40, Mark Loeser wrote: > > Mike Frysinger <[EMAIL PROTECTED]> said: > > > that means when people upgrade to gcc-3.4, gcc-3.3 will remain on their > > > system until they remove it > > > > > > so if user fails to rebuild all their packages before unmerging gcc-3.3 > > > they will be screwed, but OH WELL > > > > Yea. Even after they remove it though, libstdc++-v3 should be pulled in > > after that. Only issue I really see is people that have libraries compiled > > with 3.3 and 3.4 and don't know why stuff is broken. I don't know how > > large of a problem that will be though. > > It will be huge, see > https://bugs.gentoo.org/show_bug.cgi?id=64615 > https://bugs.gentoo.org/show_bug.cgi?id=61146 > > Every user _must_ be instructed to run > 'revdep-rebuild --soname libstdc++.so.5', > if a system contains things linking to libstdc++.so.5 and things linking to > libstdc++.so.6 I consider it horribly broken.
*sigh* ...and when it tries to "recompile" openoffice-bin? doom3? A system linked against both libraries is definitely *not* broken, as there are plenty of cases where this is necessary. > Thus having libstdc++-v3 installed apparently solves a problem but in fact > does not solve anything, the only solution is to recompile everything c++ > related on the system. Except the binary apps that you don't have the source to be able to recompile. So now we're right back where we were, aren't we? -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
