From: Kristian Benoit <kbenoit@opersys.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] EAPI
Date: Fri, 26 Aug 2005 15:49:35 -0400 [thread overview]
Message-ID: <1125085775.16733.55.camel@localhost> (raw)
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@gentoo.org mailing list
next reply other threads:[~2005-08-26 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 19:49 Kristian Benoit [this message]
2005-08-26 20:32 ` [gentoo-dev] [RFC] EAPI Brian Harring
2005-08-26 20:41 ` Ciaran McCreesh
2005-08-26 22:02 ` Drake Wyrm
2005-08-26 22:26 ` Brian Harring
2005-08-26 21:31 ` Dan Meltzer
2005-09-02 6:09 ` Marius Mauch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1125085775.16733.55.camel@localhost \
--to=kbenoit@opersys.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox