From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] metdata.dtd should require <herd/>
Date: Wed, 23 Dec 2009 19:36:27 +0100 [thread overview]
Message-ID: <55e0be1b0912231036q533f43ccx2425383804da561@mail.gmail.com> (raw)
In-Reply-To: <4B288301.5030808@gentoo.org>
On Wed, Dec 16, 2009 at 7:49 AM, Rémi Cardona <remi@gentoo.org> wrote:
> Le 15/12/2009 16:19, Peter Volkov a écrit :
>>
>> we will force all metadata.xml files have strict order of tags: first
>> <herd/> then other tags. Currently there are about 200 ebuilds with
>> different order http://bugs.gentoo.org/show_bug.cgi?id=279206#c4 .
>
> Others and I actually make use of the order in metadata.xml. The first entry
> is the one that will get bugs assignment in bugzilla, and the others will
> get CCed.
>
> So if we're really going with herds first in metadata.xml, could we have an
> optional attribute - or whatever else you see fit - to convey that _this_
> herd/maintainer is the "main" herd/maintainer?
>
> Thanks
>
Perhaps we should create a schema to validate the file. XMLSchema (or
any of the other standards) allows for much more flexibility in
specifying these things. Btw. I did not design the metadata DTD for
order to be significant. The only priority is that maintainer goes
before herd, that's all.
Paul
--
Paul de Vrieze
next prev parent reply other threads:[~2009-12-23 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 11:56 [gentoo-dev] irregular metdata.xml check Thilo Bangert
2009-12-07 12:13 ` Ulrich Mueller
2009-12-07 13:20 ` Thilo Bangert
2009-12-07 17:04 ` Hans de Graaff
2009-12-07 20:20 ` Thilo Bangert
2009-12-15 15:19 ` [gentoo-dev] metdata.dtd should require <herd/> Peter Volkov
2009-12-15 17:16 ` Alex Alexander
2009-12-15 17:27 ` Mike Frysinger
2009-12-15 17:48 ` [gentoo-dev] " Jonathan Callen
2009-12-16 6:49 ` [gentoo-dev] " Rémi Cardona
2009-12-23 18:36 ` Paul de Vrieze [this message]
2009-12-24 12:37 ` Richard Freeman
2009-12-24 16:12 ` Jeroen Roovers
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=55e0be1b0912231036q533f43ccx2425383804da561@mail.gmail.com \
--to=pauldv@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