On Wed, 4 Dec 2019 13:44:22 +0100 Miroslav Šulc <fordf...@gentoo.org> wrote:
> it's proly little bit off this topic, but why do we have to copy
> homepage and description from ebuild to ebuild? wouldn't it be better to
> move this information to metadata.xml and keep it just there? or does in
> reality one package really have various homepages and various
> descriptions for different versions? metadata.xml could also contain
> more structured data like you outlined, i.e. link to homepage,
> sources/repository, bug tracker and possibly other.
Also, widespread in usage in dev-perl/, the homepage can be reasonably
defaulted, and so, 99% of ebuilds there have a HOMEPAGE value
conjugated from ${PN}
Can't reasonably do that in metadata.xml
So any proposal that involves metadata.xml must allow for it being an
auxiliary to the value in the ebuild
( ie: if there is a HOMEPAGE in the ebuild, it should take precedence
over reading metadata.xml )
pgpToaepYq4jW.pgp
Description: OpenPGP digital signature
