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 1OhA6w-0000QE-W4 for garchives@archives.gentoo.org; Thu, 05 Aug 2010 23:44:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B3296E09A5; Thu, 5 Aug 2010 23:44:22 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id A54D8E08C1 for ; Thu, 5 Aug 2010 23:43:57 +0000 (UTC) Received: from [192.168.1.110] (c-24-245-20-2.hsd1.mn.comcast.net [24.245.20.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPSA id 294841B404D for ; Thu, 5 Aug 2010 23:43:57 +0000 (UTC) Message-ID: <4C5B4CBB.8010301@gentoo.org> Date: Thu, 05 Aug 2010 18:43:55 -0500 From: Jeremy Olexa User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100701 Thunderbird/3.0.5 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] RFC: Reviving GLEP33 References: <4C569638.9000407@gentoo.org> <20100802211517.1f207d31@snowcone> <4C573EBB.3080005@gentoo.org> <20100805032702.GG12708@hrair.al.intel.com> <4C5AF34C.2010608@gentoo.org> In-Reply-To: <4C5AF34C.2010608@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: d77f4178-641b-4ce6-b1c2-dbb2b7a3fdc5 X-Archives-Hash: 80255d7e9bc8351d215b2fcc4fdf906b On 08/05/2010 12:22 PM, Matti Bickel wrote: > I guess the point here is that we need a stable version of PMs for a > reasonable time before we switch tree ebuilds to it. > People will hate me if I use EAPI4 functionality in php ebuilds as soon > as councils approves EAPI4. Security might want a word with me if it's a > fast-stable security release. People will not "hate you" - if the portage with EAPI4 is in ~arch, you can have PHP w/EAPI4 in ~arch, even on zero-day of release. Likewise with stable tree. It does not matter when council "approves" EAPI4, it matters when portage has the implementation and is released.. The caveat is with @system packages, especially bash/python/portage itself. -Jeremy