1 |
Hi there |
2 |
|
3 |
Sorry for the delay but I was busy organizing our booth at the OpenExpo in |
4 |
Bern. |
5 |
You can find the updated GLEP46 here: |
6 |
http://dev.gentoo.org/~dev-zero/glep-0046.txt |
7 |
|
8 |
Difference in words |
9 |
------------------- |
10 |
Restriction to http/https has been dropped as pointed out by council members |
11 |
(amne and Flameeyes if I'm right). |
12 |
The point for restricting the URLs to the mentioned protocols was that they |
13 |
shouldn't link to automatically updated ressources. |
14 |
This has been replaced by an explicit specification and a recommandation |
15 |
that http/http should be favoured over ftp/svn/gopher/etc to make the |
16 |
implementation for automated update discovery tools easier (they should of |
17 |
course ignore URLs they can't handle). |
18 |
|
19 |
`cvs diff` |
20 |
---------- |
21 |
Index: glep-0046.txt |
22 |
=================================================================== |
23 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/glep-0046.txt,v |
24 |
retrieving revision 1.4 |
25 |
diff -r1.4 glep-0046.txt |
26 |
80,81c80,90 |
27 |
< ``changelog`` should contain a URL prefixed with ``http://`` or |
28 |
< ``https://`` where the location of the upstream changelog can be found. |
29 |
--- |
30 |
> ``changelog`` should contain a URL where the location of the upstream |
31 |
> changelog can be found. The URL must be version independent and must point |
32 |
to |
33 |
> a changelog which is only updated on new releases of the corresponding |
34 |
> package. (This also implies that one can link to an automatically updated |
35 |
> changelog in case of vcs snapshots only.) |
36 |
> |
37 |
> ``doc`` should contain a URL where the location of the upstream |
38 |
> documentation can be found. The link must not point to any third party |
39 |
> documentation and must be version independent. If the documentation is |
40 |
> available in more than one language, a ``lang`` attribute can be used |
41 |
> which follows the same rules as the one for ``longdescription``. |
42 |
83,92c92,93 |
43 |
< ``doc`` should contain a URL prefixed with with ``http://`` or |
44 |
< ``https://`` where the location of the upstream documentation can be |
45 |
found. |
46 |
< The link must not point to any third party documentation and must be |
47 |
version |
48 |
< independent. If the documentation is available in more than one language, |
49 |
a |
50 |
< ``lang`` attribute can be used which follows the same rules as the one |
51 |
< for ``longdescription``. |
52 |
< |
53 |
< ``bugs-to`` should contain a place where bugs can be filed, a URL |
54 |
< prefixed with ``http://`` or ``https://`` or an e-mail address prefixed |
55 |
< with ``mailto:``. |
56 |
--- |
57 |
> ``bugs-to`` should contain a place where bugs can be filed, a URL or an |
58 |
> e-mail address prefixed with ``mailto:``. |
59 |
106c107 |
60 |
< in ``metadata/dtd/remote-id-tags.dtd``. |
61 |
--- |
62 |
> in ``metadata/dtd/remote-id-tags.dtd`` or ``metadata/dtd/metadata.dtd``. |
63 |
121c122 |
64 |
< <doc lang="de">http://foo.bar./doc/index.de.html</doc> |
65 |
--- |
66 |
> <doc lang="de">http://foo.bar/doc/index.de.html</doc> |
67 |
135a137,145 |
68 |
> Notes |
69 |
> ===== |
70 |
> |
71 |
> The specified URLs must include a protocol as described in RFC 3986. |
72 |
> Furthermore the most common protocol should be used in case of several |
73 |
> possibilities (http should be favoured over https or ftp over gopher or |
74 |
svn, |
75 |
> etc). |
76 |
> |
77 |
> |
78 |
|
79 |
Cheers, |
80 |
Tiziano |
81 |
|
82 |
|
83 |
-- |
84 |
gentoo-dev@l.g.o mailing list |