| 1 |
On Fri, Jul 04, 2008 at 09:58:21PM +0200, Tiziano M?ller wrote: |
| 2 |
> > On Fri, Jul 04, 2008 at 04:22:02PM +0200, Tiziano M?ller wrote: |
| 3 |
> >> One GLEP introduces new elements 'team', 'dev' and 'proxy': |
| 4 |
> >> http://dev.gentoo.org/~dev-zero/glep/glep-new_metadata_elements.html |
| 5 |
> > 1. With the addition of <maintainer><team>cpp</team></maintainer>, why |
| 6 |
> > do we still need <herd> elements? |
| 7 |
> I'd see the herd element as kind of tag which could be used to search for |
| 8 |
> packages (given the corresponding tools). |
| 9 |
Clarify the GLEP to mention this please? |
| 10 |
|
| 11 |
> > 2. "<gentoo:dev>dev-zero</gentoo:dev>". That's not possible to validate |
| 12 |
> > sanely. The following would be better: |
| 13 |
> > <maintainer><dev project="foobar">moodev</dev></maintainer> |
| 14 |
> > |
| 15 |
> > With the default value of the 'project' attribute being 'gentoo'. |
| 16 |
> That's another good solution. The possibility I mentioned is rather suitable |
| 17 |
> for others wanting to extend our metadata.xml format (and still be able to |
| 18 |
> validate the content of gentoo:dev against our list of devs). |
| 19 |
'gentoo:dev' isn't directly validable. It states element 'dev' in the |
| 20 |
XML namespace of 'gentoo'. That's why I think that the the project |
| 21 |
attribute variation would be more suitable, and also really easy for |
| 22 |
other projects to handle. |
| 23 |
|
| 24 |
When they are adding their own metadata.xml files, they can use an XSL |
| 25 |
transform to add the explicit "project='gentoo'" for their own |
| 26 |
metadata.xml files. |
| 27 |
|
| 28 |
-- |
| 29 |
Robin Hugh Johnson |
| 30 |
Gentoo Linux Developer & Infra Guy |
| 31 |
E-Mail : robbat2@g.o |
| 32 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives