From: Fabio Erculiani <lxnay@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Application name in metadata.xml
Date: Sat, 11 Feb 2012 15:03:59 +0100 [thread overview]
Message-ID: <CAN3AtvpgBZvEzQN7fUpHR=2cA6i-7FZJPoeVhZaxoGK_XGKcww@mail.gmail.com> (raw)
In-Reply-To: <20120211142720.6d75db72@pomiocik.lan>
On Sat, Feb 11, 2012 at 2:27 PM, Michał Górny <mgorny@gentoo.org> wrote:
> On Sat, 11 Feb 2012 14:00:38 +0100
> Fabio Erculiani <lxnay@gentoo.org> wrote:
>
>> I think this is not the first time it's been discussed here, but maybe
>> I'm wrong.
>> Other distros associate a more user-friendly package name (application
>> name) to packages.
>> Say, they bind libreoffice-writer to "LibreOffice Writer" in package
>> metadata.
>>
>> How about expanding metadata.xml (adding to its .dtd) to also support
>> this? It would be nice to show this info in GUI package managers
>> instead of the actual, and ugly (for the newbies), CP or CPV.
>> It would be just a small addition that would make a big diff.
>
> I think we already expand the name in DESCRIPTION whenever it is
> ambiguous.
DESCRIPTION != Application Name
Description is way too long, and sometimes, it even overflows 80 chars
limit (I recall there was a suggested limit for it, and it is 80 chars
-- that's why we have long-description in metadata.xml).
>
> Could you please mention some Gentoo examples which would benefit from
> the proposed change?
As I wrote, GUI Package Managers or Web frontends to Portage (package browsers).
Example image, taken from Ubuntu SC, showing application names:
http://cdn.omgubuntu.co.uk/wp-content/uploads/2011/08/Selection_008.jpeg
>
> --
> Best regards,
> Michał Górny
Cheers,
--
Fabio Erculiani
next prev parent reply other threads:[~2012-02-11 14:04 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 [this message]
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
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='CAN3AtvpgBZvEzQN7fUpHR=2cA6i-7FZJPoeVhZaxoGK_XGKcww@mail.gmail.com' \
--to=lxnay@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