From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: HOMEPAGE and DESCRIPTION in ebuilds? (was: Usefulness of HOMEPAGE=https://www.gentoo.org)
Date: Wed, 04 Dec 2019 14:11:47 +0100 [thread overview]
Message-ID: <ed4a37336f6c47b43b1dcd103cd3099eb45637a7.camel@gentoo.org> (raw)
In-Reply-To: <4d591628-9956-a952-29bd-af6accc136c6@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
On Wed, 2019-12-04 at 13:44 +0100, Miroslav Šulc wrote:
> hi,
>
> 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.
>
Inertia. It's been proposed years ago, never moved forward.
The relevant bug is here:
https://bugs.gentoo.org/186454
If you want to discuss it further, please do it on the bug (even though
it's closed).
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-12-04 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 12:36 [gentoo-dev] Usefulness of HOMEPAGE=https://www.gentoo.org Michał Górny
2019-12-04 12:44 ` [gentoo-dev] Re: HOMEPAGE and DESCRIPTION in ebuilds? (was: Usefulness of HOMEPAGE=https://www.gentoo.org) Miroslav Šulc
2019-12-04 13:11 ` Michał Górny [this message]
2019-12-04 15:18 ` Kent Fredric
2019-12-04 13:25 ` [gentoo-dev] Usefulness of HOMEPAGE=https://www.gentoo.org Michał Górny
2019-12-04 15:21 ` Kent Fredric
2019-12-04 15:24 ` Joonas Niilola
2019-12-04 15:47 ` Kent Fredric
2019-12-04 17:26 ` Michał Górny
2019-12-04 19:58 ` Joonas Niilola
2019-12-04 21:32 ` Alec Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed4a37336f6c47b43b1dcd103cd3099eb45637a7.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox