Gentoo Archives: gentoo-dev

From: Kristian Benoit <kbenoit@×××××××.com>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] [RFC] EAPI
Date: Fri, 26 Aug 2005 19:59:27
Message-Id: 1125085775.16733.55.camel@localhost
On the EAPI subject Brian just brought back, I had this idea that we
could use the same approch XML took with HTML.

The ebuild could define which EAPI to use, but instead beiing a version,
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
<eapi-name>.py. If not already loaded, that plugable eapi would be
loaded before processing the ebuild.

That way, there is no outdated ebuild format. There is just a default
format which is the actual format.

It could also be an XML defining the ebuild's build sequence and other
particularities a group of ebuild could have.

Kristian

-- 
gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] [RFC] EAPI Brian Harring <ferringb@g.o>
Re: [gentoo-dev] [RFC] EAPI Dan Meltzer <parallelgrapefruit@×××××.com>
Re: [gentoo-dev] [RFC] EAPI Marius Mauch <genone@g.o>