Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Jeremy Olexa <darkside@g.o>
Subject: Re: RFC: Reviving GLEP33
Date: Thu, 05 Aug 2010 18:43:55 -0500
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


Replies:
Re: RFC: Reviving GLEP33
-- Duncan
References:
RFC: Reviving GLEP33
-- Matti Bickel
Re: RFC: Reviving GLEP33
-- Ciaran McCreesh
Re: RFC: Reviving GLEP33
-- Matti Bickel
Re: RFC: Reviving GLEP33
-- Brian Harring
Re: RFC: Reviving GLEP33
-- Matti Bickel
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: RFC: Reviving GLEP33
Next by thread:
Re: RFC: Reviving GLEP33
Previous by date:
Re: RFC: Reviving GLEP33
Next by date:
Re: RFC: Reviving GLEP33


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.