public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Walker <ka0ttic@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP 34 (category metadata) implemented
Date: Wed, 23 Mar 2005 09:59:08 -0500	[thread overview]
Message-ID: <4241843C.3050806@gentoo.org> (raw)
In-Reply-To: <1111589519.24040.21.camel@cgianelloni.nuvox.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Gianelloni wrote:
> On Wed, 2005-03-23 at 02:46 +0000, Ciaran McCreesh wrote:
> 
>>Package maintainers, feel free to update the descriptions if you can
>>come up with something better. It's fairly likely you'll be able to add
>>in a couple more helpful sentences, since I never go anywhere near some
>>categories. If you're fluent in non-English, by all means add in other
>>languages, but only do this if you're actually sure you're going to
>>spell things properly -- this is why I stuck to English only...
> 
> 
> Do these metadata files support <herd> and <maintainer>?
> 

- From a post from ciaranm in the original thread:

| > The ``<herd>`` and ``<maintainer>`` elements are not generally
| > relevant at the category level.
|
| If they are, can they be used?

The DTD says they can be. Or, at least, I see no reason to impose
additional restrictions saying that they can't. I wouldn't consider them
an appropriate substitute for per-package metadata, however.

- --
merreeege-a, n.:
	Cunferteeble-a bunds.
Bork Bork Bork!

Aaron Walker <ka0ttic@gentoo.org>
[ BSD | cron | forensics | shell-tools | commonbox | netmon | vim | web-apps ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCQYQ8C3poscuANHARAlaPAJ4m4M6wvi513tH4npZqLmUNTwgAvQCgxGfl
BEMopMfGnz10UgF4VoWcGHU=
=HGq3
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-03-23 14:59 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
2005-03-23 14:59   ` Aaron Walker [this message]
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=4241843C.3050806@gentoo.org \
    --to=ka0ttic@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