From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Application name in metadata.xml
Date: Mon, 13 Feb 2012 01:42:57 +0100 [thread overview]
Message-ID: <4F385C91.2000608@gentoo.org> (raw)
In-Reply-To: <1329081282.446.9.camel@rook>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
Alexandre Rostovtsev schrieb:
> Users know a package's "natural name", not the occasionally cryptic
> ebuild name, and certainly not the category. If I want to install a game
> called "Neverwinter Nights", it may not be immediately apparent to me
> that I should emerge something called "games-rpg/nwn".
>
> Adding the natural name to metadata would allow users to more easily
> find the packages they need via packages.gentoo.org and tools like eix.
>
> -Alexandre
>
>
>
If people have to look into a file to find a name for a package
different from the package name, they can also directly look into the
ebuild or, even more simple, just use the search ability of portage or
other tools, which are able to search the DESCRIPTION.
So if package name really differs from the ebuild name, put it into the
description and you can find the package with portage or tools like.....
eix ;-)
If you really, for whatever reasons, dont want to place it into
DESCRIPTION, metadata.xml already has longdescription. If you place the
full natural name of the package into that field together with an
extended description, i am pretty sure, that noone will complain.
So from my point of view, i currently dont see any need for a special
field in metadata.xml to specify the natural name of a package.
--
Thomas Sachau
Gentoo Linux Developer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 380 bytes --]
next prev parent reply other threads:[~2012-02-13 0:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 13:00 [gentoo-dev] RFC: Application name in metadata.xml Fabio Erculiani
2012-02-11 13:27 ` Michał Górny
2012-02-11 14:03 ` Fabio Erculiani
2012-02-12 0:02 ` Ian Stakenvicius
2012-02-12 8:01 ` Fabian Groffen
2012-02-12 15:43 ` "Paweł Hajdan, Jr."
2012-02-12 19:37 ` Ulrich Mueller
2012-02-12 21:14 ` Alexandre Rostovtsev
2012-02-12 21:22 ` Michał Górny
2012-02-12 21:34 ` Alexandre Rostovtsev
2012-02-12 21:43 ` James Broadhead
2012-02-13 0:42 ` Thomas Sachau [this message]
2012-02-13 8:35 ` Markos Chandras
2012-02-13 13:12 ` Fabio Erculiani
2012-02-13 17:24 ` Kent Fredric
2012-02-13 9:41 ` Luca Barbato
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=4F385C91.2000608@gentoo.org \
--to=tommy@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