--- xml/htdocs/proj/en/glep/glep-0046.html 2008/01/24 13:02:28 1.8 +++ xml/htdocs/proj/en/glep/glep-0046.html 2008/04/03 13:35:55 1.9 @@ -28,9 +28,9 @@
name should contain a block of text with upstream's name, is mandatory and can only appear once.
email should contain an e-mail address in the format firstname.lastname@example.org.-
changelog should contain a URL prefixed with http:// or -https:// where the location of the upstream changelog can be found.-
doc should contain a URL prefixed with with http:// or -https:// where the location of the upstream documentation can be found. -The link must not point to any third party documentation and must be version -independent. If the documentation is available in more than one language, a -lang attribute can be used which follows the same rules as the one -for longdescription.-
bugs-to should contain a place where bugs can be filed, a URL -prefixed with http:// or https:// or an e-mail address prefixed -with mailto:.+
changelog should contain a URL where the location of the upstream +changelog can be found. The URL must be version independent and must point to +a changelog which is only updated on new releases of the corresponding +package. (This also implies that one can link to an automatically updated +changelog in case of vcs snapshots only.)+
doc should contain a URL where the location of the upstream +documentation can be found. The link must not point to any third party +documentation and must be version independent. If the documentation is +available in more than one language, a lang attribute can be used +which follows the same rules as the one for longdescription.+
bugs-to should contain a place where bugs can be filed, a URL or an +e-mail address prefixed with mailto:.
remote-id should specify a type of package identification tracker and the identification that corresponds to the package in question. remote-id should make it easier to index information such as its @@ -133,7 +135,7 @@ identifier. This GLEP does not specify a complete list of legal values for type -- developers should email the gentoo-dev mailing list before using a new type value. The list of valid tags should be kept -in metadata/dtd/remote-id-tags.dtd.+in metadata/dtd/remote-id-tags.dtd or metadata/dtd/metadata.dtd.
For example, a metadata.xml upstream snippet may look like:
<upstream> @@ -147,7 +149,7 @@ </maintainer> <changelog>http://foo.bar/changelog.txt</changelog> <doc lang="en">http://foo.bar/doc/index.html</doc> - <doc lang="de">http://foo.bar./doc/index.de.html</doc> + <doc lang="de">http://foo.bar/doc/index.de.html</doc> <bugs-to>https://bugs.foo.bar</bugs-to> <remote-id type="freshmeat">foobar</remote-id> <remote-id type="sourceforge">foobar</remote-id> @@ -162,7 +164,14 @@ should just ignore the additional elements.
The specified URLs must include a protocol as described in RFC 3986. +Furthermore the most common protocol should be used in case of several +possibilities (http should be favoured over https or ftp over gopher or svn, +etc).+
This document has been placed in the public domain.