| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Ciaran McCreesh wrote: |
| 5 |
> Subject pretty much sums it up. I mentioned this in the sys-apps thread |
| 6 |
> and no-one said it was a horrid idea... Since I'm asking for DTD |
| 7 |
> additions it probably warrants a GLEP. Also, it'll be nice to get a |
| 8 |
> quick easy 'Accepted, Implemented' up on the site :) This time, my |
| 9 |
> efforts will not be thwarted by Donnie and his lame editor! |
| 10 |
|
| 11 |
I don't see any need to thwart this one, since it depends on GLEP 31 |
| 12 |
already. =P |
| 13 |
|
| 14 |
> * It would help developers better select a relevant category for their |
| 15 |
> package, rather than dumping everything into ``sys-apps`` and |
| 16 |
> ``app-misc`` as is done currently. |
| 17 |
|
| 18 |
If it's difficult to search/browse, it may not help much. |
| 19 |
|
| 20 |
> A new top level ``<catmetadata>`` element shall be added to the DTD to |
| 21 |
> distinguish category metadata elements from the existing ``<pkgmetadata>`` |
| 22 |
> elements. |
| 23 |
|
| 24 |
Why does it needs to be distinguished? |
| 25 |
|
| 26 |
> The ``<herd>`` and ``<maintainer>`` elements are not generally relevant at |
| 27 |
> the category level. |
| 28 |
|
| 29 |
If they are, can they be used? |
| 30 |
-----BEGIN PGP SIGNATURE----- |
| 31 |
Version: GnuPG v1.4.0 (GNU/Linux) |
| 32 |
|
| 33 |
iD8DBQFCMfqeXVaO67S1rtsRAtaZAKDtIr+cSQzbpwbNvTTv61KsJzOQQgCaApIp |
| 34 |
L0zHo+bThPqTfmxIyRsqn44= |
| 35 |
=bRlL |
| 36 |
-----END PGP SIGNATURE----- |
| 37 |
-- |
| 38 |
gentoo-dev@g.o mailing list |
Archives