From: Dan Meltzer <parallelgrapefruit@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] EAPI
Date: Fri, 26 Aug 2005 17:31:41 -0400 [thread overview]
Message-ID: <46059ce10508261431673110fc@mail.gmail.com> (raw)
In-Reply-To: <1125085775.16733.55.camel@localhost>
Maybe I'm incorrect, but I believe Kristian was not saying use XML,
but using xml as a comparasison (I know there is a better word.. but
its escaping me... that comparassion thing on the SAT's). He's not
saying to use xml, but in order to extend portage, extend it much like
xml extends html, with a pluggable script referenced as the dtd
equivvelent.
On 8/26/05, Kristian Benoit <kbenoit@opersys.com> wrote:
> 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
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-26 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 19:49 [gentoo-dev] [RFC] EAPI Kristian Benoit
2005-08-26 20:32 ` 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 [this message]
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=46059ce10508261431673110fc@mail.gmail.com \
--to=parallelgrapefruit@gmail.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