public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP 34 (category metadata) implemented
Date: Thu, 24 Mar 2005 08:34:52 -0500	[thread overview]
Message-ID: <1111671292.24040.54.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <200503240926.50056.pauldv@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

On Thu, 2005-03-24 at 09:26 +0100, Paul de Vrieze wrote:
> > Hrm, according to the DTD, no. You'll need to persuade pauldv on that
> > one if you want to use them...
> 
> If you give me a good reason I'll be persuaded. If however you look back at 
> the herds proposal there is no linkage between categories and herds. To add 
> this would possibly introduce that. I also want to have some kind of meaning 
> added on putting herd and maintainer in category metadata. Especially for 
> maintainer it would seem strange that someone could maintain all packages in 
> a category.

Well, games-* could be herd: games... and games-fps could be herd: games
maintainer: vapier, wolf31o2...  I'm also sure that app-vim could be
herd: vim...  Just like app-emacs could be herd: emacs...

There are herds that are specifically designed to maintain a category.
Take net-mail or net-print (printing) as examples.  At the very minimum,
I can see value in being able to assign a herd to a category, if not a
maintainer.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-24 13:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23  2:46 [gentoo-dev] GLEP 34 (category metadata) implemented Ciaran McCreesh
2005-03-23  5:49 ` Joshua Brindle
2005-03-23  6:07   ` Ciaran McCreesh
2005-03-23 14:51 ` Chris Gianelloni
2005-03-23 14:56   ` Ciaran McCreesh
2005-03-24  8:26     ` Paul de Vrieze
2005-03-24 13:34       ` Chris Gianelloni [this message]
2005-03-23 14:59   ` Aaron Walker
2005-03-24 11:52 ` Michael Kohl
2005-03-24 12:46   ` Juergen Hoetzel
2005-03-24 16:22   ` Ciaran McCreesh
2005-03-24 16:56     ` Michael Kohl
2005-03-25  2:27 ` Fernando J. Pereda
2005-03-26 20:57 ` Ciaran McCreesh
2005-03-28  6:12   ` Donnie Berkholz
2005-03-28 14:45   ` Mike Frysinger

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=1111671292.24040.54.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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