| 1 |
On Wed, 4 Dec 2019 13:44:22 +0100 |
| 2 |
Miroslav Šulc <fordfrog@g.o> wrote: |
| 3 |
|
| 4 |
> it's proly little bit off this topic, but why do we have to copy |
| 5 |
> homepage and description from ebuild to ebuild? wouldn't it be better to |
| 6 |
> move this information to metadata.xml and keep it just there? or does in |
| 7 |
> reality one package really have various homepages and various |
| 8 |
> descriptions for different versions? metadata.xml could also contain |
| 9 |
> more structured data like you outlined, i.e. link to homepage, |
| 10 |
> sources/repository, bug tracker and possibly other. |
| 11 |
|
| 12 |
Also, widespread in usage in dev-perl/, the homepage can be reasonably |
| 13 |
defaulted, and so, 99% of ebuilds there have a HOMEPAGE value |
| 14 |
conjugated from ${PN} |
| 15 |
|
| 16 |
Can't reasonably do that in metadata.xml |
| 17 |
|
| 18 |
So any proposal that involves metadata.xml must allow for it being an |
| 19 |
auxiliary to the value in the ebuild |
| 20 |
|
| 21 |
( ie: if there is a HOMEPAGE in the ebuild, it should take precedence |
| 22 |
over reading metadata.xml ) |
Archives