Wednesday 5th October 2011
Fedora Project
Updated perl-Class-Load to 0.11 in F-16 and Rawhide:
- Don't accept package names that start with a digit
Rewrite some of the guts to use Module::Runtime rather than reimplementing its functionality
As this version now requires Module::Runtime ≥ 0.009, which is only available in F-16 onwards, I dropped support in the spec file for all older releases, which significantly simplifies things
Local Packages
New package perl-Params-Classify (0.013)
New package perl-Module-Runtime (0.009)
Updated perl-AnyEvent to 6.1:
Incompatible change: the default log level is now "4" (error and above), and some messages inside AnyEvent have been elevated to higher log levels to print by default
AnyEvent::log, unlike AnyEvent::Log::log, did not always exit on fatal
Work around yet another signal race bug, newly introduced by POE
Add google public ipv6 dns as fall-back servers, so AE::DNS can finally support ipv6-only operation even with defaults (also use ::1 instead of 127.0.0.1)
- Give better guidelines on how to choose a logging level
AnyEvent::Log can now cap (limit) log message priority by context
AE::log will now save and restore $! and $@, so callers don't have to
AE::Strict now checks that registered fds are still valid at regular intervals
Skip frequently called 'require' calls if the module appears loaded
- Increase signal latency test timer considerably for poor little OSX, which can't be bothered with basic POSIX functionality such as signal delivery
- Mention some debugging aides in the tutorial
New environment variable PERL_ANYEVENT_MAX_SIGNAL_LATENCY
Private (%namespace) log contexts in PERL_ANYEVENT_LOG now have the name of the context as title
AnyEvent::Strict would not restore read-write access to $_ when a callback died - this is a user bug, but since AE::Strict exists to help debugging...
Detect the extremely evil IO::Async::Loop::AnyEvent module and refuse to work with it - the author is well aware of the issues but refuses to fix them; this extreme step has been taken because the module actively attacks the goals of AnyEvent and makes it harder for module authors to use AnyEvent
Updated perl-Class-Load to 0.11:
- Don't accept package names that start with a digit
Rewrite some of the guts to use Module::Runtime rather than reimplementing its functionality
I dropped the patches to support building without Test::Fatal or Pod::Coverage::Moose since these are only needed with perl < 5.8.1 and we need at least 5.8.1 for the required module Package::Stash
Updated perl-ExtUtils-ParseXS to 3.05:
The XSUB.h changes to make XS(name) use XS_INTERNAL(name) by default (which were in the 5.15.2 dev release of perl) have been reverted since too many CPAN modules expect to be able to refer to XSUBs declared with XS(name); instead, ExtUtils::ParseXS will define a copy of the XS_INTERNAL/XS_EXTERNAL macros as necessary going back to perl 5.10.0.
By default, ExtUtils::ParseXS will use XS_INTERNAL(name) instead of XS(name)
Don't put null characters into the generated source file when -except is used; write the '\0' escape sequence properly instead
By #defineing PERL_EUPXS_ALWAYS_EXPORT or PERL_EUPXS_NEVER_EXPORT early in your XS code, you can force ExtUtils::ParseXS to always or never export XSUB symbols; this has no effect on boot_* symbols since those must be exported
Simplify generated XS code by emitting a compatibility version of dVAR
Fixed "INCLUDE: $cmd |" (CPAN RT#70213)
Updated perl-Module-Load to 0.22:
Resolve possible security problem (http://blogs.perl.org/users/michael_g_schwern/2011/10/how-not-to-load-a-module-or-bad-interfaces-make-good-people-do-bad-things.html) where a '::' prefixed module can 'jump' out of @INC