to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
- Updating package for p5 module MRO::Compat from 0.10 to 0.11
- Correcting license to ${PERL5_LICENSE}
- Adjusting dependencies according to META.yaml
Upstream changes:
0.11 - Wed May 27, 2009
- Fix misspelled docs for get_isarev. Closes RT#46401.
- Bump optional prereq on Class::C3 to 0.20.
- Updating package for p5 module MRO::Compat to 0.10
- set license to artistic-2.0
Upstream changes:
0.10 - Wed Mar 25, 2009
- Remove the fake Build.PL. Module::Install doesn't support that anymore.
(Florian Ragwitz)
- Remove auto_install from Makefile.PL. Its use is strongly discouraged.
(Closes RT#44542) (Simon Betrang)
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
The "mro" namespace provides several utilities for dealing with
method resolution order and method caching in general in Perl 5.9.5
and higher.
This module provides those interfaces for earlier versions of Perl
(back to 5.6.0 anyways).
It is a harmless no-op to use this module on 5.9.5+. That is to
say, code which properly uses MRO::Compat will work unmodified on
both older Perls and 5.9.5+.
If you're writing a piece of software that would like to use the
parts of 5.9.5+'s mro:: interfaces that are supported here, and
you want compatibility with older Perls, this is the module for
you.
Some parts of this code will work better and/or faster with
Class::C3::XS installed (which is an optional prereq of Class::C3,
which is in turn a prereq of this package), but it's not a requirement.
This module never exports any functions. All calls must be fully
qualified with the mro:: prefix.
