> what i'm proposing now is that we add a local USE flag (Nick proposed
> "autopoint") to sys-devel/gettext. something like:
> RDEPEND="autopoint? (
> git? ( dev-vcs/git )
> !git? ( cvs? ( dev-vcs/cvs ) )
> !cvs? ( dev-vcs/git )
> )"
> idea is that
> "JC" == Jonathan Callen writes:
JC> You can create a POSIX.UTF-8 locale right now, using the same
JC> /etc/locale.gen mechanism that is used for generating other locales
JC> (localedef will output a few warnings, but the generated locale
JC> works just fine from what I can see).
JC> If the
On Thursday, August 05, 2010 03:17:18 Vaeth wrote:
> > what i'm proposing now is that we add a local USE flag (Nick proposed
> > "autopoint") to sys-devel/gettext. something like:
> > RDEPEND="autopoint? (
> >
> > git? ( dev-vcs/git )
> > !git? ( cvs? ( dev-vcs/cvs ) )
> >
On 08/05/2010 05:27 AM, Brian Harring wrote:
> If a PM encounters an EAPI it doesn't understand/support, by
> definition the metadata it tried generating is not usable- the PM
> doesn't support that new EAPI thus it has zero clue how to
> generate/store metadata appropriately for that EAPI.
I g
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 wit
On Thu, Aug 05, 2010 at 07:22:20PM +0200, Matti Bickel wrote:
> On 08/05/2010 05:27 AM, Brian Harring wrote:
> > If a PM encounters an EAPI it doesn't understand/support, by
> > definition the metadata it tried generating is not usable- the PM
> > doesn't support that new EAPI thus it has zero cl
