From: Alexandre Rostovtsev <tetromino@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Application name in metadata.xml
Date: Sun, 12 Feb 2012 16:14:42 -0500 [thread overview]
Message-ID: <1329081282.446.9.camel@rook> (raw)
In-Reply-To: <20280.5374.577507.960890@a1i15.kph.uni-mainz.de>
On Sun, 2012-02-12 at 20:37 +0100, Ulrich Mueller wrote:
> >>>>> On Sun, 12 Feb 2012, Paweł Hajdan, wrote:
>
> > On 2/11/12 2:00 PM, Fabio Erculiani wrote:
> >> Other distros associate a more user-friendly package name
> >> (application name) to packages.
> >> Say, they bind libreoffice-writer to "LibreOffice Writer" in
> >> package metadata.
>
> [Replying to a random message in this thread.]
>
> Why do you think that writing the package name in mixed case and with
> embedded white space would be more "user friendly"?
because-removing-all-upper-case-spaces-and-punctuation-from-a-string
makes it less readable to a non-programmer.
> >> How about expanding metadata.xml (adding to its .dtd) to also
> >> support this?
>
> I still don't see what this would buy us. So far we have a unique
> identifier (namely ${CATEGORY}/${PN}) for our packages. Introducing
> another name will water this down and cause confusion for users, in
> the first place.
>
> So, can you point out what are the advantages of your proposal?
> Are they large enough to outweigh the confusion arising?
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
next prev parent reply other threads:[~2012-02-12 21:15 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 [this message]
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
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=1329081282.446.9.camel@rook \
--to=tetromino@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