Hi folks,

this commit changes the set of USE flags on the just stabled gcc-4.6,
running a huge number into an rebuild of an freshly updated package.
(emerge --newuse recaclulates from "go disabled" to "go missing")

Wouldn't it be possible to
a) refrain from this change (really, who has USE=go turned on?)
b) handle this with package.use.mask,
c) figure it out before stabilization

I see the point in nobody beeing perfect, but these recurring
effect-less rebuilds of widespread base packages set me up.

Imho, editing /var/db/pkg/sys-devel/gcc-4.6.3/USE is not a recipe to be
carried out to the user. But can we do stuff like this in profile
updates? Without hurting system with USE=go activated, which need
actually need the recompile.

my 2 cents

   Michael


-------- Original Message --------
Subject: [gentoo-commits] gentoo-x86 commit in eclass: ChangeLog
toolchain.eclass
Date: Tue, 15 Jan 2013 02:30:53 +0000 (UTC)
From: Ryan Hill (dirtyepic) <[email protected]>
Reply-To: [email protected], [email protected]
To: [email protected]

dirtyepic    13/01/15 02:30:53

  Modified:             ChangeLog toolchain.eclass
  Log:
  Drop go support for 4.6 - broken by newer glibc versions and upstream
recommends it not be used.

Revision  Changes    Path
1.615                eclass/ChangeLog

file :
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/ChangeLog?rev=1.615&view=markup
plain:
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/ChangeLog?rev=1.615&content-type=text/plain
diff :
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/ChangeLog?r1=1.614&r2=1.615

Index: ChangeLog
===================================================================
RCS file: /var/cvsroot/gentoo-x86/eclass/ChangeLog,v
retrieving revision 1.614
retrieving revision 1.615
diff -u -r1.614 -r1.615
--- ChangeLog   13 Jan 2013 22:35:28 -0000      1.614
+++ ChangeLog   15 Jan 2013 02:30:53 -0000      1.615
@@ -1,6 +1,10 @@
 # ChangeLog for eclass directory
 # Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/eclass/ChangeLog,v 1.614 2013/01/13
22:35:28 eva Exp $
+# $Header: /var/cvsroot/gentoo-x86/eclass/ChangeLog,v 1.615 2013/01/15
02:30:53 dirtyepic Exp $
+
+  15 Jan 2013; Ryan Hill <[email protected]> toolchain.eclass:
+  Drop go support for 4.6 - broken by newer glibc versions and upstream
+  recommends it not be used.

   13 Jan 2013; Gilles Dartiguelongue <[email protected]> gnome2.eclass:
   Allow ebuild override of eclass generated econf.



1.567                eclass/toolchain.eclass

file :
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/toolchain.eclass?rev=1.567&view=markup
plain:
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/toolchain.eclass?rev=1.567&content-type=text/plain
diff :
http://sources.gentoo.org/viewvc.cgi/gentoo-x86/eclass/toolchain.eclass?r1=1.566&r2=1.567

Index: toolchain.eclass
===================================================================
RCS file: /var/cvsroot/gentoo-x86/eclass/toolchain.eclass,v
retrieving revision 1.566
retrieving revision 1.567
diff -u -r1.566 -r1.567
--- toolchain.eclass    29 Dec 2012 06:45:06 -0000      1.566
+++ toolchain.eclass    15 Jan 2013 02:30:53 -0000      1.567
@@ -1,6 +1,6 @@
-# Copyright 1999-2012 Gentoo Foundation
+# Copyright 1999-2013 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
-# $Header: /var/cvsroot/gentoo-x86/eclass/toolchain.eclass,v 1.566
2012/12/29 06:45:06 vapier Exp $
+# $Header: /var/cvsroot/gentoo-x86/eclass/toolchain.eclass,v 1.567
2013/01/15 02:30:53 dirtyepic Exp $
 #
 # Maintainer: Toolchain Ninjas <[email protected]>

@@ -115,7 +115,7 @@
                tc_version_is_at_least "4.3" && IUSE+=" fixed-point"
                tc_version_is_at_least "4.4" && IUSE+=" graphite"
                [[ ${GCC_BRANCH_VER} == 4.5 ]] && IUSE+=" lto"
-               tc_version_is_at_least "4.6" && IUSE+=" go"
+               tc_version_is_at_least "4.7" && IUSE+=" go"
        fi
 fi






-- 
Michael Weber
Gentoo Developer
web: https://xmw.de/
mailto: Michael Weber <[email protected]>



Reply via email to