| 1 |
On Mon, 12 Mar 2012 08:30:19 +0000 |
| 2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Mon, 12 Mar 2012 09:27:11 +0100 |
| 5 |
> Michał Górny <mgorny@g.o> wrote: |
| 6 |
> > <eapi>15-xml</eapi> |
| 7 |
> > |
| 8 |
> > and |
| 9 |
> > |
| 10 |
> > - eapi: 15-yaml |
| 11 |
> |
| 12 |
> You're carefully concocting your examples to make it look like it |
| 13 |
> should work. |
| 14 |
|
| 15 |
Or I am just printing the first thing that comes into my head. |
| 16 |
|
| 17 |
> If you go the XML route, though, the EAPI would either be in a DTD |
| 18 |
|
| 19 |
Like .../gentoo/eapi/15-xml.dtd ? That would match my regex as well, |
| 20 |
unless we allow dots in EAPI. |
| 21 |
|
| 22 |
> or as <eapi value="15" />. |
| 23 |
|
| 24 |
No, definitely not. That's not the XML style. |
| 25 |
|
| 26 |
> Part of the point of all of this is that we shouldn't have to guess |
| 27 |
> what future EAPIs will look like. |
| 28 |
|
| 29 |
I'm just suggesting a way which will support a little more than |
| 30 |
bash-based solutions. We could also assume that if a file doesn't match |
| 31 |
the regexp at all, it's a unsupported EAPI. |
| 32 |
|
| 33 |
-- |
| 34 |
Best regards, |
| 35 |
Michał Górny |
Archives