On Tue, 26 Apr 2011, Greg KH wrote:
On Tue, Apr 26, 2011 at 06:43:43PM +0200, Marco Poletti wrote:
2011/4/26 Jeff Mahoney
: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/26/2011 12:38 PM, Marco Poletti wrote:
Are there any plans to push gcc 4.6.0 in Tumbleweed (now or later)?
I haven't tried it yet, so I can't guarantee it is stable enough.
As gcc or as gcc46? It's not even the default in Factory yet.
I'm interested in both plans (if any).
Note that I'm not saying it should be pushed right now, I just ask when (approx.) it will be included.
Note, if a package isn't even in Factory, it will not go to Tumbleweed, that wouldn't make much sense, right?
Is there a specific reason why you want gcc 4.6.0 in Tumbleweed? I have thought about it but was not going to even consider it until after it had survived a lot of testing in Factory.
GCC 4.6.0 as it is in Factory now is simply a new package (it won't
replace the system compiler unless you also pull the 'gcc' package
from Factory after the default compiler transition happened there).
That said, pulling GCC 4.6.0 into Tumbleweed will cause system
libraries like libgcc and libstdc++ to be updated once there is
a package that requires the new symbol versions or once the user
installs GCC 4.6 packages. This already happened in Factory about
one and a half month ago. Unfortunately people are slow fixing
fallout of a switch (see openSUSE:Factory:Staging:Gcc46) and I
don't have too much time for pushing myself.
Richard.
--
Richard Guenther