From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-science] Scientific Gentoo reorg: on herd naming
Date: Sat, 01 Jul 2006 13:07:24 -0700 [thread overview]
Message-ID: <44A6D5FC.1020608@gentoo.org> (raw)
In-Reply-To: <200607011656.45178.george@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
George Shapovalov wrote:
> The herd naming issue has surfaced in more detail again - there were already
> two comments that it is beneficial to keep -sci in herd names. I originally
> suggested that we drop it (and in general go with a "catchier" names), but
> now it looks like I am slowly turning towards being more conservative
> myself :). That is to keep sci- and possibly resembel category names as much
> as possible. The reasoning: making life easier on bug wranglers and on
> everybody trying to search for the sci-related maintaince info or just to see
> the relationship between different packages.. Any thoughts?
As I said on the bug, I don't really think this makes sense.
metadata.xml will show either 'electronics' or 'sci-electronics',
however you name it. You can use herdstat or many other tools to display
things in many different ways related to package maintainers/herds/etc.
Naming herds after categories doesn't really make sense when there isn't
a 1-to-1 mapping of herds and categories.
Thanks,
Donnie
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
prev parent reply other threads:[~2006-07-01 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 10:29 [gentoo-science] Scientific Gentoo reorg: lets get it moving George Shapovalov
2006-07-01 14:56 ` [gentoo-science] Scientific Gentoo reorg: on herd naming George Shapovalov
2006-07-01 20:07 ` Donnie Berkholz [this message]
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=44A6D5FC.1020608@gentoo.org \
--to=spyderous@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-science@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