From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RJkkg-0007Gv-Nb for garchives@archives.gentoo.org; Fri, 28 Oct 2011 11:37:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 23C9621C05B; Fri, 28 Oct 2011 11:37:19 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 5D3E821C01F for ; Fri, 28 Oct 2011 11:36:39 +0000 (UTC) Received: from [192.168.3.7] (cpe-74-77-238-39.buffalo.res.rr.com [74.77.238.39]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: blueness) by smtp.gentoo.org (Postfix) with ESMTPSA id 8B31A1B400D for ; Fri, 28 Oct 2011 11:36:38 +0000 (UTC) Message-ID: <4EAA93C4.6030101@gentoo.org> Date: Fri, 28 Oct 2011 07:36:36 -0400 From: "Anthony G. Basile" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.20) Gecko/20110919 Lightning/1.0b3pre Lanikai/3.1.12 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: hardened glibc and gcc dependencies References: <4EA91E7E.4000902@gentoo.org> <4EA98204.4030601@gentoo.org> <20111027174707.21c6cdbe@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: 788e38891bdce131b4c627a6da9daae0 On 10/27/2011 07:50 PM, Mike Frysinger wrote: > On Fri, Oct 28, 2011 at 01:47, Ryan Hill wrote: >> On Thu, 27 Oct 2011 23:03:12 +0530 Nirbheek Chauhan wrote: >>> So, I honestly see no reason why toolchain should not start using EAPI 2. >> I await your patch to toolchain.eclass. :P > i wouldn't bother as it's most likely not going to be accepted at this time > > (i haven't kept up-to-date with the hardened threads as i'm traveling atm) > -mike > I wouldn't even worry about the hardened stuff right now, just getting toolchain.eclass EAPI>=2 would be a step forward. Approaching this naively, can't we just set EAPI="2" in the eclass, see what breaks and fix? Or is it more involved because some EAPI="0" ebuilds would be inheriting it and we'd need a lot of if "${EAPI}" == 0 checks interspersed through the eclass? -- Anthony G. Basile, Ph.D. Gentoo Linux Developer [Hardened] E-Mail : blueness@gentoo.org GnuPG FP : 8040 5A4D 8709 21B1 1A88 33CE 979C AF40 D045 5535 GnuPG ID : D0455535