1 |
On Fri, Aug 26, 2005 at 03:49:35PM -0400, Kristian Benoit wrote: |
2 |
> On the EAPI subject Brian just brought back, I had this idea that we |
3 |
> could use the same approch XML took with HTML. |
4 |
> |
5 |
> The ebuild could define which EAPI to use, but instead beiing a version, |
6 |
> the EAPI would be an ebuild API definition. The equivalent to the XML's |
7 |
> dtd. The ebuild could point to a directory named |
8 |
> $PORTDIR/eapi/<eapi-name>/ which would contain a python script named |
9 |
> <eapi-name>.py. If not already loaded, that plugable eapi would be |
10 |
> loaded before processing the ebuild. |
11 |
> |
12 |
> That way, there is no outdated ebuild format. There is just a default |
13 |
> format which is the actual format. |
14 |
> |
15 |
> It could also be an XML defining the ebuild's build sequence and other |
16 |
> particularities a group of ebuild could have. |
17 |
Few questions; |
18 |
A) what does xml bring to the table explicitly that is needed? |
19 |
remember portage doesn't have a hard dep on xml parsing libs yet, |
20 |
this would add it (livecd/stage* potentially needing adjustment as |
21 |
a result). |
22 |
B) EAPI is pretty much bash env template switching; xml/python plugins |
23 |
don't help in that respect, although a python plugin for that eapi |
24 |
level may be added at some point (right now it's not required for |
25 |
the eapi v0/v1 python side components). |
26 |
|
27 |
I am worried, long term mind you, in tracking the differences between |
28 |
eapi levels and keeping the code clean. My thought for way down the |
29 |
line when an eapi level has long since gone unused is to break it out |
30 |
of portage and into it's own package as a plugin. |
31 |
Specifics of it haven't yet gotten to, mainly because it's not worth |
32 |
sweating over till rewrite is usable (priorities), but that's the long |
33 |
term intention for EAPI. |
34 |
|
35 |
Beyond that, the question of what needs to be tracked outside of |
36 |
python/bash code (what would be stuck in the suggested xml) should |
37 |
also be clarified, since I'm not seeing what all would be jammed in |
38 |
there. |
39 |
~harring |