"Fernando J. Pereda" <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted below, on  Wed, 19 Dec 2007
17:50:19 +0100:

> On Wed, Dec 19, 2007 at 11:03:54AM -0500, Jim Ramsay wrote:
>> 
>> The sense I've gotten from this discussion so far is that if you want
>> features from two EAPIs you know *can* be combined without collisions,
>> you should define a third EAPI that is a superset of the other 2.
> 
> *nod* But that is different from arbitrary mixing them, which is what
> originated this subthread.

Quoting CiaranM from a different subthread, defining EAPI:

> A cat/pkg-ver has exactly one EAPI. That EAPI belongs to the
> cat/pkg-ver as a whole, and is static across that cat/pkg-ver.

Now, we already had someone mention using two together, prefix (which 
seems to have been defined as an EAPI for the purposes of this 
discussion, I don't deal with it so haven't the foggiest about it, 
personally) and EAPI-1.  If that portion of Ciaran's definition quoted 
above stands, that usage would be defined as illegal, thus anything using 
it "broken".

The work-around as Jim mentions above would be defining a third EAPI 
combining as a superset the other two.  One could then create ebuilds 
using that third EAPI.  Of course, until at least one of the available 
package managers supports that third EAPI, ebuilds created to use it 
wouldn't be of much use, and until portage, being the official Gentoo PM, 
supported it, said ebuilds could not be placed in the Gentoo-x86 tree.

The question, then, is whether anyone, particularly those working with 
PMs other than paludis (Ciaran being the lead on it so presumably his 
EAPI definition works for it), disagrees with that portion of Ciaran's 
EAPI definition.  I've seen no such direct disagreement so far, with the 
presumed exception of the person mentioning already combining two 
(without creating a third out of them) in prefix, of course.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
[EMAIL PROTECTED] mailing list

Reply via email to