| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
Brian Dolbec: |
| 5 |
> On Thu, 28 Apr 2016 15:39:05 -0400 Göktürk Yüksek |
| 6 |
> <gokturk@××××××××××.edu> wrote: |
| 7 |
> |
| 8 |
>> --- metadata.dtd | 5 +---- 1 file changed, 1 insertion(+), 4 |
| 9 |
>> deletions(-) |
| 10 |
>> |
| 11 |
>> diff --git a/metadata.dtd b/metadata.dtd index 7626a57..b608852 |
| 12 |
>> 100644 --- a/metadata.dtd +++ b/metadata.dtd @@ -3,7 +3,7 @@ |
| 13 |
>> <!ATTLIST catmetadata pkgname CDATA ""> |
| 14 |
>> |
| 15 |
>> <!-- Metadata for a package --> -<!ELEMENT pkgmetadata ( |
| 16 |
>> (maintainer|natural-name|longdescription|slots|use|upstream)* )> |
| 17 |
>> +<!ELEMENT pkgmetadata ( |
| 18 |
>> (maintainer|longdescription|slots|use|upstream)* )> <!ATTLIST |
| 19 |
>> pkgmetadata pkgname CDATA ""> <!-- One tag for each maintainer of |
| 20 |
>> a package, multiple allowed--> @@ -13,9 +13,6 @@ explicit type) |
| 21 |
>> for Gentoo maintainers is prohibited. --> <!ATTLIST maintainer |
| 22 |
>> type (person|project|unknown) "unknown"> |
| 23 |
>> |
| 24 |
>> - <!-- Natural name for package, example: LibreOffice (for |
| 25 |
>> app-office/libreoffice) --> - <!ELEMENT natural-name (#PCDATA) |
| 26 |
>> > - <!-- A long description of the package in freetext--> |
| 27 |
>> <!ELEMENT longdescription (#PCDATA|pkg|cat)* > |
| 28 |
>> |
| 29 |
> |
| 30 |
> |
| 31 |
> Isn't this almost obsolete? it's now xmlschema... And I hope to |
| 32 |
> have the new repoman with it out this weekend :) |
| 33 |
> |
| 34 |
|
| 35 |
Does GLEP 68 explicitly declare metadata.dtd obsolete? I see that the |
| 36 |
example metadata.xml on the GLEP is missing DOCTYPE, are we getting |
| 37 |
rid of those too? |
| 38 |
|
| 39 |
I understand that the DTD is more like a super-set, so anything that |
| 40 |
complies with GLEP 68 will comply with the DTD as well. However, there |
| 41 |
is a caveat here: for example the GLEP dismisses the list of possible |
| 42 |
values for <remote-id/> by saying "The list of available trackers and |
| 43 |
their specific identifiers are outside scope of this specification." |
| 44 |
but does not mention where these values shall be kept either. The |
| 45 |
moment we add a new remote-id, the xmlschema diverges from the DTD and |
| 46 |
stops being a subset. |
| 47 |
|
| 48 |
Besides, the PMS says the format of metadata.xml is described in DTD. |
| 49 |
Even if we move to something else, doesn't metadata.dtd need to be |
| 50 |
kept around until the PMS is amended? |
| 51 |
|
| 52 |
- -- |
| 53 |
gokturk |
| 54 |
|
| 55 |
-----BEGIN PGP SIGNATURE----- |
| 56 |
|
| 57 |
iQEcBAEBCgAGBQJXIp+LAAoJEIT4AuXAiM4zszAIAI8GPcE8Ap3b652DYWRX/THb |
| 58 |
IeRBMGyTsgu8s0GB5i7Qfy94uKMxc1+9SCipEK0GoBq7Vkeils8SHdSNCt2TPE6t |
| 59 |
Hzh4UG6lI7qebMVrsRi85GDZr1l4HA5/Co54lizMlFW7uO8vgRRU2Cj7AfPt/BFQ |
| 60 |
zan7+yQv+zLv0OVxb2XPAnbCMn0cL5PIzSBXN4aN+p58FVOwJlUs/tEQbNOKjRWK |
| 61 |
v6J4ejz4QA8Sy6Gx7aAupBzT+8YhtU9BLMWzbSf4VEMBELD8ZrzYfZtxZQNcpkFV |
| 62 |
INef3hFcpM+5whHTDQ0QfAbVXEyRRVoMo1W87yZLUT7qUrlRcMhbjopT6+e+ZCs= |
| 63 |
=HDEG |
| 64 |
-----END PGP SIGNATURE----- |
Archives