[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev]  Updated GLEP 46: Allow upstream tags in metadata.xml (again)
From:       Tiziano =?ISO-8859-1?Q?M=FCller?= <dev-zero () gentoo ! org>
Date:       2008-03-25 8:22:41
Message-ID: fsacom$n3t$1 () ger ! gmane ! org
[Download RAW message or body]

Hi there

Sorry for the delay but I was busy organizing our booth at the OpenExpo in
Bern.
You can find the updated GLEP46 here:
http://dev.gentoo.org/~dev-zero/glep-0046.txt

Difference in words
-------------------
Restriction to http/https has been dropped as pointed out by council members
(amne and Flameeyes if I'm right).
The point for restricting the URLs to the mentioned protocols was that they
shouldn't link to automatically updated ressources.
This has been replaced by an explicit specification and a recommandation
that http/http should be favoured over ftp/svn/gopher/etc to make the
implementation for automated update discovery tools easier (they should of
course ignore URLs they can't handle).

`cvs diff`
----------
Index: glep-0046.txt
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/glep-0046.txt,v
retrieving revision 1.4
diff -r1.4 glep-0046.txt
80,81c80,90
< ``changelog`` should contain a URL prefixed with ``http://`` or
< ``https://`` where the location of the upstream changelog can be found.
---
> ``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``.
83,92c92,93
< ``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:``.
---
> ``bugs-to`` should contain a place where bugs can be filed, a URL or an
> e-mail address prefixed with ``mailto:``.
106c107
< in ``metadata/dtd/remote-id-tags.dtd``.
---
> in ``metadata/dtd/remote-id-tags.dtd`` or ``metadata/dtd/metadata.dtd``.
121c122
<               <doc lang="de">http://foo.bar./doc/index.de.html</doc>
---
>               <doc lang="de">http://foo.bar/doc/index.de.html</doc>
135a137,145
> Notes
> =====
>
> 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).
>
>

Cheers,
Tiziano


-- 
gentoo-dev@lists.gentoo.org mailing list

[prev in list] [next in list] [prev in thread] [next in thread]