| 1 |
On 7 March 2016 at 07:12, Justin <jlec> <jlec@g.o> wrote: |
| 2 |
>> Slots are not accepted in <pkg> elements? Is that intentional? If so, |
| 3 |
>> is there something else we can use? |
| 4 |
>> |
| 5 |
> |
| 6 |
> We should definitely include SLOTs in the allowed syntax. |
| 7 |
|
| 8 |
|
| 9 |
<flag name="gstreamer">Enable HTML5 audio/video support via |
| 10 |
<pkg>media-libs/gstreamer:1.0</pkg></flag> |
| 11 |
<flag name="gstreamer010">Enable HTML5 audio/video support via |
| 12 |
<pkg>media-libs/gstreamer:0.10</pkg></flag> |
| 13 |
|
| 14 |
|
| 15 |
Surely you can trivially transpose: |
| 16 |
|
| 17 |
<pkg>cat/pn:slot</pkg> |
| 18 |
|
| 19 |
To |
| 20 |
|
| 21 |
<pkg>cat/pn</pkg>:slot |
| 22 |
|
| 23 |
Its not like you need slot/version metadata to be machine trackable |
| 24 |
here, you're probably wanting to communicate the cat/pn for hyper-ref |
| 25 |
purposes, and the slot/version to be separate for humans. |
| 26 |
|
| 27 |
Its "<pkg>" not "<depspec>" after all. |
| 28 |
|
| 29 |
-- |
| 30 |
Kent |
| 31 |
|
| 32 |
KENTNL - https://metacpan.org/author/KENTNL |
Archives