Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
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.
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.
Changes from previous:
----------------------
0.012 2014-02-24 13:07:18-05:00 America/New_York
- Generated from ETHER/YAML-Tiny-1.61.tar.gz
0.011 2014-02-13 20:30:30-05:00 America/New_York
- Generated from ETHER/YAML-Tiny-1.60.tar.gz
0.010 2013-09-23 13:11:20 America/New_York
- Generated from ETHER/YAML-Tiny-1.55.tar.gz
- Fix broken test when copying from YAML-Tiny
- updated Makefile.PL logic to support PERL_NO_HIGHLANDER
0.009 2013-09-23 10:16:19 America/New_York
- Generated from ETHER/YAML-Tiny-1.55.tar.gz
- Makefile.PL will use UNINST=1 on old perls that might have
an old version incorrectly installed into the core library path
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
devel/p5-CPAN-Meta-YAML from 0.007 to 0.008.
Upstream changes:
0.008 2012-03-14 17:13:24 EST5EDT
- Generated from ADAMK/YAML-Tiny-1.51.tar.gz
- Updated from YAML-Tiny to fix compatibility with older Scalar::Utils
devel/p5-CPAN-Meta-YAML as dependency of scheduled update of package
for CPAN module CPAN::Meta in devel/p5-CPAN-Meta.
This module implements a subset of the YAML specification for use in
reading and writing CPAN metadata files like META.yml and MYMETA.yml.
It should not be used for any other general YAML parsing or generation
task.
NOTE: META.yml (and MYMETA.yml) files should be UTF-8 encoded. Users
are responsible for proper encoding and decoding. In particular, the
read and write methods do not support UTF-8 and should not be used.