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!
Pkgsrc changes:
- set PERL5_MODULE_TYPE to Module::Install::Bundled
Upstream changes:
0.11 THu May 13 14:31:00 CEST 2010
- Fix doc typo. jawnsy++
0.10 Wed May 12 17:53:56 CEST 2010
- Stop pretending the created classes are anonymous.
They used to close over their own metaclass, so they were never
cleaned up anyway and only made debugging unnecessarily hard as
all instances referenced the metaclass as well.
- Require newer version of MX::Role::Parameterized in the parameterized
role test. (RT#49873).
0.09 Tue Apr 6 22:51:40 CDT 2010
- Class->with_traits(...)->new is now preferred over
Class->new_with_traits(...).
Upstream changes:
0.08 Sat Feb 13 17:05:23 GMT 2010
- Allow you to pass traits => 'OneTrait' rather than having to say
traits => ['OneTrait'] to help when getting traits from things that
want to send a scalar (e.g. Config::General)
Pkgsrc changes:
- Adjust dependencies
Upstream changes:
0.07 Sun Aug 16 10:38:47 CDT 2009
- deprecate apply_traits ("no warnings" to disable warning)
- add MooseX::Traits::Util so that other modules can resolve trait names
- add new_class_with_traits util function to create classes with traits
of scheduled import of MooseX::Traits::Pluggable (dependency for
CatalystX::Component::Traits etc.)
Often a developer want to create components that can be added to a class
arbitrarily. This module makes it easy for the end user to use these
components. Instead of requiring the user to create a named class with the
desired roles applied, or applying roles to the instance one-by-one, he can
just pass a traits parameter to the class's new_with_traits constructor.
This role will then apply the roles in one go, cache the resulting class
(for efficiency), and return a new instance. Arguments meant to initialize
the applied roles' attributes can also be passed to the constructor.
