Gentoo Archives: gentoo-dev

From: "Tiziano Müller" <dev-zero@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: Re: [2 GLEPs] metadata improvements
Date: Sat, 05 Jul 2008 09:27:17
Message-Id: g4neou$imm$1@ger.gmane.org
In Reply to: Re: [gentoo-dev] Re: [2 GLEPs] metadata improvements by "Robin H. Johnson"
1 Robin H. Johnson wrote:
2
3 > On Fri, Jul 04, 2008 at 09:58:21PM +0200, Tiziano M?ller wrote:
4 >> > On Fri, Jul 04, 2008 at 04:22:02PM +0200, Tiziano M?ller wrote:
5 >> >> One GLEP introduces new elements 'team', 'dev' and 'proxy':
6 >> >>
7 http://dev.gentoo.org/~dev-zero/glep/glep-new_metadata_elements.html
8 >> > 1. With the addition of <maintainer><team>cpp</team></maintainer>, why
9 >> > do we still need <herd> elements?
10 >> I'd see the herd element as kind of tag which could be used to search for
11 >> packages (given the corresponding tools).
12 > Clarify the GLEP to mention this please?
13 Sure, will do.
14
15 >
16 >> > 2. "<gentoo:dev>dev-zero</gentoo:dev>". That's not possible to validate
17 >> > sanely. The following would be better:
18 >> > <maintainer><dev project="foobar">moodev</dev></maintainer>
19 >> >
20 >> > With the default value of the 'project' attribute being 'gentoo'.
21 >> That's another good solution. The possibility I mentioned is rather
22 >> suitable for others wanting to extend our metadata.xml format (and still
23 >> be able to validate the content of gentoo:dev against our list of devs).
24 > 'gentoo:dev' isn't directly validable. It states element 'dev' in the
25 > XML namespace of 'gentoo'. That's why I think that the the project
26 > attribute variation would be more suitable, and also really easy for
27 > other projects to handle.
28 >
29 > When they are adding their own metadata.xml files, they can use an XSL
30 > transform to add the explicit "project='gentoo'" for their own
31 > metadata.xml files.
32 >
33
34
35 --
36 gentoo-dev@l.g.o mailing list