| 1 |
On 12 March 2012 21:14, Ulrich Mueller <ulm@g.o> wrote: |
| 2 |
>>>>>> On Mon, 12 Mar 2012, James Broadhead wrote: |
| 3 |
> |
| 4 |
>> I'm sure that it's been considered already, but what are the arguments |
| 5 |
>> against embedding the EAPI on a per-package (default) or per-version |
| 6 |
>> basis in metadata.xml. It IS metadata after all. |
| 7 |
> |
| 8 |
> You can find a recent discussion in bug 402167, comment #4 and |
| 9 |
> following. <https://bugs.gentoo.org/show_bug.cgi?id=402167#c4> |
| 10 |
> |
| 11 |
> Ulrich |
| 12 |
> |
| 13 |
|
| 14 |
That makes sense (actually, it calls for metadata.xml to be converted |
| 15 |
to json even without bundling EAPI in there). |
| 16 |
|
| 17 |
If repoman validated metadata.json based on a clear definition in PMS, |
| 18 |
that would be a valid solution to the problem (that wouldn't require |
| 19 |
external libraries beyond python) |
Archives