From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] metdata.dtd should require <herd/>
Date: Tue, 15 Dec 2009 18:19:00 +0300 [thread overview]
Message-ID: <1260890340.29419.142.camel@tablet> (raw)
In-Reply-To: <200912072120.44046.bangert@gentoo.org>
В Пнд, 07/12/2009 в 21:20 +0100, Thilo Bangert пишет:
> Hans de Graaff <graaff@gentoo.org> said:
> > On Mon, 2009-12-07 at 12:56 +0100, Thilo Bangert wrote:
> > > dev-util/cucumber <herd> missing
> >
> > Fixed, but this is really a bug in metadata.dtd, which specifies
> > <!ELEMENT pkgmetadata ( (herd|maintainer|longdescription|use|
> > upstream)* )>
> indeed: http://bugs.gentoo.org/show_bug.cgi?id=279206
So what we will do with this? It'll be great to fix dtd to follow our
requirements, but there is a problem:
if we change dtd like this:
<!ELEMENT pkgmetadata ( herd+, (maintainer|longdescription|use|upstream)* )>
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 .
Hans's suggestion http://bugs.gentoo.org/show_bug.cgi?id=279206#c7 works
but it is not nice and prohibits another order: herd, other tags, herd.
Personally I'd kept dtd simple and forced ordering.
So actually two questions here:
1. How should we fix dtd?
2. Are there any problems if we fix dtd first and let maintainers fix
metadata.xml on bumps (iow, what will became broken if metadata.xml
became not valid)?
--
Peter.
next prev parent reply other threads:[~2009-12-15 16:32 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 ` Peter Volkov [this message]
2009-12-15 17:16 ` [gentoo-dev] metdata.dtd should require <herd/> 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
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=1260890340.29419.142.camel@tablet \
--to=pva@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