On 02/11/2011 05:13 PM, Diego Elio Pettenò wrote: > Il giorno ven, 11/02/2011 alle 15.37 +0100, Sebastian Pipping ha > scritto: >> Portage will propose a downgrade of glibc on emerge-update-world, okay. >> How bad would that be? Does it cause any other trouble? > > And glibc will refuse to downgrade unless you hack the ebuild. Now let's > say that the user rebuilt gcc after the glibc upgrade, and now forces > downgrade; after forcing downgrade, gcc will fail to find the symbols > with higher versioning (GNU versioning), which means it won't run. > >> In your eyes, is there anything we can do to improve the current situation? > > Every time a base package changes that could cause huge breakage, mask, > send a message to q...@gentoo.org to start up testing ebuild $foo with an > unmask list, and wait till we give the go before unmasking. >
That will be definately done for libpng-1.5.1 that just hit tree with KEYWORDS="". It turns most, if not all deprecation warnings from libpng-1.4.x series to fatal errors. ABI break, .la files drop and the fun of 90% of packages not building against it \o/ - Samuli
