Thread: search.cpan.org is EOL, update links

search.cpan.org has now been EOL’d and turned off, with all URLs redirecting to
metacpan.org [1].  While the redirects are likely to the maintained for a long
time, we might as well update to avoid the risk of stale redirects.  Attached
patch changes the few links we have to instead use metacpan.

cheers ./daniel

[1] https://www.perl.com/article/saying-goodbye-to-search-cpan-org/

On Thu, Jun 28, 2018 at 01:00:47PM +0200, Daniel Gustafsson wrote:
> search.cpan.org has now been EOL’d and turned off, with all URLs redirecting to
> metacpan.org [1].  While the redirects are likely to the maintained for a long
> time, we might as well update to avoid the risk of stale redirects.  Attached
> patch changes the few links we have to instead use metacpan.

Okay, let's fix that.

While working on the links for CPAN, perhaps these should be switched to
https as well?
src/sgml/acronyms.sgml:
<ulink url="http://www.cpan.org/">Comprehensive Perl Archive Network</ulink>
contrib/fuzzystrmatch/dmetaphone.c:
version 0.05 available from http://www.cpan.org.
--
Michael

> On 29 Jun 2018, at 03:23, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Thu, Jun 28, 2018 at 01:00:47PM +0200, Daniel Gustafsson wrote:
>> search.cpan.org has now been EOL’d and turned off, with all URLs redirecting to
>> metacpan.org [1].  While the redirects are likely to the maintained for a long
>> time, we might as well update to avoid the risk of stale redirects.  Attached
>> patch changes the few links we have to instead use metacpan.
>
> Okay, let's fix that.
>
> While working on the links for CPAN, perhaps these should be switched to
> https as well?

Good point, we might as well do that too.  Fixed those two and an additional
one in the attached updated version.

cheers ./daniel

On Fri, Jun 29, 2018 at 08:29:16AM +0200, Daniel Gustafsson wrote:
> Good point, we might as well do that too.  Fixed those two and an additional
> one in the attached updated version.

Did you notice the paragraph at the top of ppport.h?  This is a file
automatically generated so it does not sound like a good idea to apply
the change there.  Refreshing this file would make the most sense if
needed, but I have not looked at that in details.

Pushed the rest with a proper back-patch for the docs.
--
Michael

> On 29 Jun 2018, at 15:24, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Fri, Jun 29, 2018 at 08:29:16AM +0200, Daniel Gustafsson wrote:
>> Good point, we might as well do that too.  Fixed those two and an additional
>> one in the attached updated version.
>
> Did you notice the paragraph at the top of ppport.h?  This is a file
> automatically generated so it does not sound like a good idea to apply
> the change there.  Refreshing this file would make the most sense if
> needed, but I have not looked at that in details.

Good spot, I missed that and 100% agree with you.

> Pushed the rest with a proper back-patch for the docs.

Thanks!