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.
{perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS
since pkgsrc enforces the newest perl version anyway, so they
should always pick perl, but sometimes (pkg_add) don't due to the
design of the {,} syntax.
No effective change for the above reason.
Ok joerg
Update DEPENDS
Upstream changes:
0.011 2015-03-22 10:07:52+01:00 Europe/Amsterdam
Declare the minimum version required for the "merged_requirements" interface
---------------
0.010 2015-01-30 19:10:49+01:00 Europe/Amsterdam
bump Module::Metdata prereq for $VERSION parsing (RT#101095)
Consistently require same version of CPAN::Meta::Requirements
Upstream changes:
0.009 2014-06-20 19:37:43+02:00 Europe/Amsterdam
Various POD fixes
0.008 2013-10-17 16:44:57 Europe/Amsterdam
Switch to using merged_requirements
Test Env instead of Carp for version overshoot [#89591]
Document $incdirs in the right function
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.
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.