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