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 <[EMAIL PROTECTED]> 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
