Log message:
Update packages using a search.cpan.org HOMEPAGE to metacpan.org.

The former now redirects to the latter.

This covers the most simple cases where http://search.cpan.org/dist/name
can be changed to https://metacpan.org/release/name.

Reviewed by hand to hopefully make sure no unwanted changes sneak in.

Log message:
Recursive bump for perl5-5.28.0

Log message:
Recursive revbump from lang/perl5 5.26.0

Log message:
Bump PKGREVISION for perl-5.24.

Log message:
Add SHA512 digests for distfiles for math category

Problems found locating distfiles:
	Package dfftpack: missing distfile dfftpack-20001209.tar.gz
	Package eispack: missing distfile eispack-20001130.tar.gz
	Package fftpack: missing distfile fftpack-20001130.tar.gz
	Package linpack: missing distfile linpack-20010510.tar.gz
	Package minpack: missing distfile minpack-20001130.tar.gz
	Package odepack: missing distfile odepack-20001130.tar.gz
	Package py-networkx: missing distfile networkx-1.10.tar.gz
	Package py-sympy: missing distfile sympy-0.7.6.1.tar.gz
	Package quadpack: missing distfile quadpack-20001130.tar.gz

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.

Log message:
Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.

Log message:
Bump for perl-5.20.0.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.

Log message:
Adding package forPAN package Math-Random-ISAAC-XS version 1.004 into
math/Math-Random-ISAAC-XS.

This module implements the same interface as Math::Random::ISAAC and can
be used as a drop-in replacement. This is the recommended implementation
of the module, based on Bob Jenkins' reference implementation in C.

Selecting the backend to use manually really only has two uses:

    * If you are trying to avoid the small overhead incurred with
      dispatching method calls to the appropriate backend modules.
    * If you are testing the module for performance and wish to
      explicitly decide which module you would like to use.