| 1 |
>>>>> On Wed, 16 Sep 2020, Michał Górny wrote: |
| 2 |
|
| 3 |
> +- one or more ``<version/>`` elements, each containing a version |
| 4 |
> + constraint in the format matching EAPI 0 dependency specification |
| 5 |
> + with the package category and name parts omitted, e.g. ``<1.7``. |
| 6 |
|
| 7 |
That's not a very powerful syntax, so unless I miss something, |
| 8 |
metadata.xml would have to be updated for almost every stable candidate. |
| 9 |
|
| 10 |
To give an example, released versions of app-editors/emacs have exactly |
| 11 |
two numerical components, while prereleases and release candidates have |
| 12 |
three components or are marked _rc. Both would be impossible to match |
| 13 |
with the proposed syntax. |
| 14 |
|
| 15 |
So IMHO this has no advantage over keeping the information in the ebuild |
| 16 |
(e.g. as a PROPERTIES token). |
| 17 |
|
| 18 |
Ulrich |
Archives