From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] metdata.dtd should require <herd/>
Date: Tue, 15 Dec 2009 12:27:25 -0500 [thread overview]
Message-ID: <200912151227.25617.vapier@gentoo.org> (raw)
In-Reply-To: <1260890340.29419.142.camel@tablet>
[-- Attachment #1: Type: Text/Plain, Size: 849 bytes --]
On Tuesday 15 December 2009 10:19:00 Peter Volkov wrote:
> 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.
+1 ... i dont see any need/reason to have fields scattered
> 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)?
write a script to fix the tree and then update the dtd
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-12-15 18:37 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 [this message]
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=200912151227.25617.vapier@gentoo.org \
--to=vapier@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