Commit graph

6 commits

Author SHA1 Message Date
wen
b7b4393682 Update to 1.002004
Remove period in the end of COMMENT to make pkglint happy

Upstream changes:
1.002004 - 2012-11-02
  - remove accidentally-introduced strictures.pm usage

1.002003 - 2012-10-29
  - fix method modifier breakage on 5.10.0

1.002002 - 2012-10-28
  - skip t/around-does.t when Class::Method::Modifiers is not installed
    (RT#80310)

1.002001 - 2012-10-26
  - t/does-Moo.t moved to 'xt' (RT#80290)
  - don't die when looking for 'DOES' on perl < 5.10 (RT#80402)

1.002000 - 2012-10-19
  - load class in addition to roles when using create_class_from_roles
  - fix module name in Makefile.PL (RT#78591)
  - when classes consume roles, override their DOES method (RT#79747)
  - method modifiers can be used for 'does' and 'DOES'
2012-11-29 02:35:09 +00:00
asau
e1ab7079b6 Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. 2012-10-31 11:16:30 +00:00
wiz
8b5d49eb78 Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.
2012-10-03 21:53:53 +00:00
sno
4a99481e98 Updating package for CPAN module Role::Tiny in devel/p5-Role-Tiny from
1.001004 to 1.001005.

upstream changes:
1.001005 - 2012-07-18
  - localize UNIVERSAL::can change to avoid confusing TB2
  - properly report roles consumed by superclasses
2012-09-10 13:02:16 +00:00
sno
f82d9234b2 Add conflict for devel/p5-Moo before Role::Tiny was split out from it 2012-07-18 08:06:03 +00:00
sno
4b90070f45 Adding new package for CPAN module Role::Tiny version 1.001004 into
devel/p5-Role-Tiny as requirement for upcoming update for devel/p5-Moo.

Role::Tiny is a minimalist role composition tool.

ROLE COMPOSITION

Role composition can be thought of as much more clever and meaningful
multiple inheritance. The basics of this implementation of roles is:

    * If a method is already defined on a class, that method will not be
      composed in from the role.
    * If a method that the role "requires" to be implemented is not
      implemented, role application will fail loudly.

Unlike Class::C3, where the last class inherited from "wins," role
composition is the other way around, where the class wins. If multiple
roles are applied in a single call (single with statement), then if any
of their provided methods clash, an exception is raised unless the class
provides a method since this conflict indicates a potential problem.
2012-07-18 07:54:13 +00:00