Re: [gentoo-dev] [RFC] EAPI

[Drake Wyrm <wyrm@haell.com>]

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

Brian Harring <ferringb@gentoo.org> wrote:
> On Fri, Aug 26, 2005 at 03:49:35PM -0400, Kristian Benoit wrote:
[snip]
> > the EAPI would be an ebuild API definition. The equivalent to the XML's
> > dtd. The ebuild could point to a directory named
> > $PORTDIR/eapi/<eapi-name>/ which would contain a python script named
[snip]
> Few questions; 
> A) what does xml bring to the table explicitly that is needed?
>    remember portage doesn't have a hard dep on xml parsing libs yet, 
>    this would add it (livecd/stage* potentially needing adjustment as 
>    a result).

If I read the idea correctly, it's not suggesting that Portage implement
XML as a config engine; it's just using XML as an example. The analogy
works just as well for SGML DTDs or C libraries.

> B) EAPI is pretty much bash env template switching
[snip]

Perhaps the EAPI handling could be implemented using eclasses, rather
than something in the deep, dark, python-based internals.

-- 
That is not dead which can eternal lie,
And with strange eons even death may die.
	-- The Call of Cthulu, II. The Tale of Inspector Legrasse

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]