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.
Upstream changes:
version 0.014; 2014-02-06
* bugfix: suppress any CORE::GLOBAL::require override, where possible,
to avoid use_package_optimistically() being misled into treating
missing modules as broken
* bugfix: in use_module() and use_package_optimistically(), pass a
supplied VERSION parameter through for the version check even if it
is undef
* tighten use_package_optimistically()'s recognition of can't-locate
errors (the same way that base.pm has recently been tightened),
so that, when a module fails to load because a module that it uses
isn't available, the outer module will be perceived as broken rather
than missing
* update documentation notes about the state of Unicode handling for
module names
* in META.{yml,json}, point to public git repository
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-Module-Runtime from 0.011 to 0.013.
pkgsrc changes:
- remove dependency to devel/p5-Params-Classify
Upstream changes:
version 0.013; 2012-02-16
* fix false failure of the test for lack of unintended dependencies
that occurred on systems using a sitecustomize.pl
version 0.012; 2012-02-12
* work around Perl core bug [perl #68590] regarding leakage of %^H
into modules being loaded
* work around Perl core bug that made a failed module loading appear
successful when re-requiring the same module
* duplicate is_string() from Params::Classify, rather than importing it,
to avoid circular dependency problems (affecting both installation
and runtime)
* duplicate minimal exporting behaviour from Exporter, and avoid using
the "feature", "warnings", "strict", and "parent" pragmata, to allow
for possible future use of this module by any infrastructure module
* document core bug workarounds
* document module name syntax more prominently, and discuss the state
of Unicode handling
* tweak documentation of use_package_optimistically()
* test behaviour with tainted module name
* test lack of unwanted eval frame around require
* give test modules more meaningful names
* convert .cvsignore to .gitignore
in devel/p5-Module-Runtime from 0.010 to 0.011
Upstream changes:
version 0.011; 2011-10-24
* bugfix: in require_module() and use_module(), work around a Perl
core bug affecting Perl 5.8 and 5.10 that could pass the wrong
context to the file scope of a required file, which breaks some
modules; this bug would only rarely afflict the core's require()
in situations where it would afflict require_module()
