From: Michael Palimaka <kensington@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Expanding categories' descriptions
Date: Mon, 01 Apr 2013 18:52:02 +1100 [thread overview]
Message-ID: <kjbeat$n59$1@ger.gmane.org> (raw)
In-Reply-To: <51587263.6080505@politeia.in>
On 1/04/2013 04:29, Denis M. wrote:
> Hello,
>
> (I was redirected from gentoo-doc@ to ask this here.)
>
> I think it's a good idea to expand the categories' descriptions (found
> in the corresponding metadata.xml files) with more accurate descriptions
> of which packages are welcome to fit in which categories.
>
> The current descriptions are very vague and aren't probably in the best
> shape to bring users' a good idea what certain category is about and
> what packages are to be found there.
>
> This can also be an issue for (new) ebuild-writers (either
> user-contributed ebuilds or just gentoo developers that are not sure0-000-p
> about it either).
> hat t
> This is of course checked by a gentoo developer if new ebuilds are to be
> submitted via the bugzilla, but I still think we should provide a better
> understanding of the categories.
>
> If expanding the metadata.xml files does not seem a good idea, we should
> at least make a little bit more comprehensive description somewhere in
> the gentoo.org/doc/ or wiki.gentoo.org pages.
>
> What do you think about it?
>
>
> Regards,
> Denis M. (Phr33d0m)
>
Sounds good to me. From time to time I see even experienced developers
not sure as to which category a package belongs.
There is also inconsistency with packages of a certain type being spread
over multiple categories. For example, packages containing "password
manager" in the description currently exist in three different categories.
next prev parent reply other threads:[~2013-04-01 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 17:29 [gentoo-dev] Expanding categories' descriptions Denis M.
2013-04-01 7:52 ` Michael Palimaka [this message]
2013-04-02 11:01 ` [gentoo-dev] " Sergey Popov
2013-04-05 5:33 ` Ben de Groot
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='kjbeat$n59$1@ger.gmane.org' \
--to=kensington@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