kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

- Add p5-Role-Tiny 1.000000

Browse source 
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 first wins. In a more complete system (see Moose)
roles are checked to see if they clash. The goal of this is to be much simpler,
hence disallowing composition of multiple roles at once.

WWW: http://search.cpan.org/dist/Role-Tiny/

Feature safe:	yes
This commit is contained in:
Sunpoet Po-Chuan Hsieh 2012-03-31 01:15:00 +00:00
parent 375c1889b2
commit 591eabe82e
Notes: svn2git 2021-03-31 03:12:20 +00:00 
svn path=/head/; revision=294023
5 changed files with 62 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
devel/Makefile
View file

@ -2351,6 +2351,7 @@
SUBDIR += p5-Return-Value
SUBDIR += p5-Role-HasMessage
SUBDIR += p5-Role-Identifiable
SUBDIR += p5-Role-Tiny
SUBDIR += p5-Rose-DateTime
SUBDIR += p5-Rose-Object
SUBDIR += p5-RunApp

40
devel/p5-Role-Tiny/Makefile Normal file
View file

@ -0,0 +1,40 @@
# New ports collection makefile for: p5-Role-Tiny
# Date created: 2012-03-31
# Whom: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>
#
# $FreeBSD$
#
PORTNAME= Role-Tiny
PORTVERSION= 1.000.000
CATEGORIES= devel perl5
MASTER_SITES= CPAN
MASTER_SITE_SUBDIR= CPAN:MSTROUT
PKGNAMEPREFIX= p5-
DISTNAME= ${PORTNAME}-${PORTVERSION:R}${PORTVERSION:E}
MAINTAINER= sunpoet@FreeBSD.org
COMMENT= Roles, like a nouvelle cusine portion size slice of Moose
BUILD_DEPENDS= p5-Class-Method-Modifiers>=0:${PORTSDIR}/devel/p5-Class-Method-Modifiers
RUN_DEPENDS= p5-Class-Method-Modifiers>=0:${PORTSDIR}/devel/p5-Class-Method-Modifiers
TEST_DEPENDS= p5-Test-Fatal>=0.003:${PORTSDIR}/devel/p5-Test-Fatal
PERL_CONFIGURE= yes
MAN3= Role::Tiny.3 \
Role::Tiny::With.3
.include <bsd.port.pre.mk>
.if ${PERL_LEVEL} < 501000
BUILD_DEPENDS+= p5-MRO-Compat>=0:${PORTSDIR}/devel/p5-MRO-Compat
RUN_DEPENDS+= p5-MRO-Compat>=0:${PORTSDIR}/devel/p5-MRO-Compat
.endif
.if ${PERL_LEVEL} < 501400
TEST_DEPENDS+= p5-Test-Simple>=0.96:${PORTSDIR}/devel/p5-Test-Simple
.endif
.include <bsd.port.post.mk>

2
devel/p5-Role-Tiny/distinfo Normal file
View file

@ -0,0 +1,2 @@
SHA256 (Role-Tiny-1.000000.tar.gz) = 68864357cdec72a4094b38986d642f28eccaafafc1b8184bf82c282ff5d1e2f8
SIZE (Role-Tiny-1.000000.tar.gz) = 8622

13
devel/p5-Role-Tiny/pkg-descr Normal file
View file

@ -0,0 +1,13 @@
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 first wins. In a more complete system (see Moose)
roles are checked to see if they clash. The goal of this is to be much simpler,
hence disallowing composition of multiple roles at once.
WWW: http://search.cpan.org/dist/Role-Tiny/

6
devel/p5-Role-Tiny/pkg-plist Normal file
View file

@ -0,0 +1,6 @@
%%SITE_PERL%%/Role/Tiny.pm
%%SITE_PERL%%/Role/Tiny/With.pm
%%SITE_PERL%%/%%PERL_ARCH%%/auto/Role-Tiny/.packlist
@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Role-Tiny
@dirrmtry %%SITE_PERL%%/Role/Tiny
@dirrmtry %%SITE_PERL%%/Role