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-pms
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-pms@g.o
From: "Andreas K. Huettel" <dilfridge@g.o>
Subject: Re: Re: EAPI 5
Date: Tue, 1 May 2012 01:02:48 +0200
Am Dienstag 01 Mai 2012, 00:44:20 schrieb Ciaran McCreesh:
> "Andreas K. Huettel" <dilfridge@g.o> wrote:
> > > I'm against this one in a "quick" EAPI, unless you can get a
> > > reference implementation and extensive testing on possible use
> > > scenarios done in time. I strongly suspect this will end up having
> > > the problems that REQUIRED_USE had when it was shoved in at the
> > > last minute without anyone having properly tried it out...
> > 
> > I cannot say much myself about the complexity of the reference
> > implementation, however the concept itself is imho pretty
> > straightforward and (in particular) not intrusive.
> Can you enumerate every possible way the files will be used, both in
> terms of syntax and intended effect? 

In the same way as package.use.mask and package.use.force.

> Can you provide assurances that it
> can't also be (ab)used to do other things not on your list?

Which list?

Of course someone will come up with other creative ideas how to (ab)use it, 
that's the nature of things. (I mean, people even write other package manglers 
replacing portage... :)

> Can you demonstrate that introducing this in an EAPI won't require
> upping profile EAPIs, 

No. Teach me, please.

An indication might however be that it acts on a package level.

> and that users whose package mangler doesn't do
> EAPI 5 won't run into problems with it?

Well. PMS describes the files in a profile directory. If 
* we introduce a new file via PMS that was not in there before, 
* and another package manager accesses that file but expects different 
information there not corresponding to our new definition, 
that package manager should be considered broken because it is not adhering to 
previous PMS revisions. So?

> The interaction of the various use related profile things is already
> very complicated and messy. We still haven't decided what happens when
> use dependencies become allowed in profiles, and we're keeping profile
> EAPIs locked below 2 so we don't have to figure it out.


Andreas K. Huettel
Gentoo Linux developer 

Re: Re: EAPI 5
-- Ciaran McCreesh
Re: Re: EAPI 5
-- Andreas K. Huettel
Re: Re: EAPI 5
-- Ciaran McCreesh
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: EAPI 5
Next by thread:
Re: Re: EAPI 5
Previous by date:
Re: Re: EAPI 5
Next by date:
Re: Re: EAPI 5

Updated Jul 18, 2012

Summary: Archive of the gentoo-pms mailing list.

Donate to support our development efforts.

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