Upstream changes:
2.128 2014-09-06 00:04:22-04:00 America/New_York
[FIXED]
- Throws an error at compile time if neither version nor
the ExtUtils::MakeMaker bootstrap are available
2.127 2014-09-04 22:17:44-04:00 America/New_York
[FIXED]
- Works around limitations in version::vpp detecting v-string magic
[PREREQS]
- Requires version.pm 0.88 in metadata, but code should work with any
version of version.pm
- Adds support for forthcoming ExtUtils::MakeMaker bootstrap version.pm
for Perls older than 5.10.0
2.126 2014-07-30 16:26:29-04:00 America/New_York
[FIXED]
- Fixed compatibility with version.pm 0.77
[DOCUMENTED]
- Minor documentation fixes
[CHANGED]
- Modernized distribution meta files
- updated Makefile.PL logic to support PERL_NO_HIGHLANDER
- Better fix than 2.123. On old perls, rather than install into
'core', we continue to install into the proper 'site' library,
but force UNINST=1 when necessary to remove stale copies
from ExtUtils::MakeMaker
- On Perls prior to v5.12, CPAN::Meta::Requirements will be installed
into the 'core' library path to avoid an older version bundled with
ExtUtils::MakeMaker and installed there taking precedence.
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.
devel/p5-CPAN-Meta-Requirements to satisfy upcoming import of Dist::Zilla
module.
A CPAN::Meta::Requirements object models a set of version constraints like
those specified in the META.yml or META.json files in CPAN distributions.
It can be built up by adding more and more constraints, and it will reduce
them to the simplest representation.
Logically impossible constraints will be identified immediately by thrown
exceptions.
