From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Move HOMEPAGE, DESCRIPTION, etc. to metadata.xml?
Date: Thu, 5 Jan 2023 12:37:12 -0500 [thread overview]
Message-ID: <Y7cKyNCyIj+eVsQG@eversor> (raw)
In-Reply-To: <1672832467.569183747@f478.i.mail.ru>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On Wed, Jan 04, 2023 at 02:41:07PM +0300, Alexander Kurakin wrote:
>
> Good day!
>
> Was there an idea to move HOMEPAGE, DESCRIPTION, etc. to metadata.xml?
There is[1] (since 2007), but it never went anywhere.
> Are the properties common for package, aren’t they?
Usually anyway. For what it's worth, among what I maintain, there is
one package (nvidia-drivers) where the 0/vulkan slot (525.47.x) has
a different HOMEPAGE pointing to the vulkan page. Not that "most" tools
really consider differences for these when displaying so it's mostly
useful for someone opening the ebuild and wanting something to click.
Having these readily viewable in the ebuild rather than buried in
the metadata is often an argument to keep these, i.e. without
description can't even see what the package is about if only looking
at the ebuild. Not that I need that myself given I use repo-cd[2]
that displays metadata when I work on ebuilds.
[1] https://bugs.gentoo.org/186454
[2] https://github.com/ionenwks/iwdevtools#repo-cd
--
ionen
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-01-05 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 11:41 [gentoo-user] Move HOMEPAGE, DESCRIPTION, etc. to metadata.xml? Alexander Kurakin
2023-01-05 17:37 ` Ionen Wolkens [this message]
2023-01-07 21:47 ` [gentoo-user] " Alexander Kurakin
2023-01-21 22:30 ` Alexander Kurakin
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=Y7cKyNCyIj+eVsQG@eversor \
--to=ionen@gentoo.org \
--cc=gentoo-user@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