Re: Metacpan trailing slash
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On 24/02/14 20:37, Axel Beckert wrote:
> Hi,
>
> Daniel Lintott wrote:
>> Just a quick question... I have seen several commits where the
>> trailing slash has been dropped from the metacpan url's.
>
> That was probably me.
>
>> Is this the format to use from now on, as looking at the
>> pkg-perl policy it is stated including the trailing slash?
>
> I didn't know it was explicitly with slash in the policy. I just
> noticed that MetaCPAN always redirects to the URL without slash so
> I consider that to be the correct one and fixed it when I noticed
> it.
>
> If it's in the policy with slash, I think we should fix that at
> least in the policy.
>
My wording was probably a little bad on that one, it's not so much as
in policy as the example given includes it ;-)
> I don't think it's worth a mass-commit, though, unless maybe it's
> done together with some more important stuff which validates
> mass-commits.
>
I would agree on that one, it's not something that is a big issue, so
can be updated as and when releases are made.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJTC69tAAoJEMw/9yOWzAkJKd8IAL2UF1Uv0fVT7xfJ+w9nl76f
UwXEYemNxbzomC8lq/hjIEs24BNEaln9nwVaQ6PcdyvawRzDwtlwEVyAKRlPPOp/
izPaJm/u4/wWFMltm1VTHjcKZ6Ws3XZcXmFn34oxG0C5Q1IY8FLBY5ioqw1uZLb8
+o/2+1nlunPH8AXL2Q23jfBAC+OhSoczsz+kJP/UKKVA8FeEGjFZYl5t4tY2S/Su
4lbBLYHrgY0Pc1HgnGbyc4BSyFhTD7+1dZI9TWqMKG+WKg87V4AbgP5zRPcme8YK
ebgpWTCWuyhlejs+LczGWkReCSgksSUjpERym1NyNI/jPSX6o/uY6K8e4q9clug=
=qysU
-----END PGP SIGNATURE-----
Reply to: