kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/p5-Module-Pluggable/Makefile

21 lines
566 B
Makefile
Raw Normal View History

Update Module::Pluggable to 3.9. Changes since 3.8: 2009-03-02 - 3.9 Allow inner packages when in a one file situation (suggestion from Christopher Brown) Fix bug with requiring skipped packages (from Jos Boumans) Oked by he@
2009-03-22 00:18:22 +01:00
# $NetBSD: Makefile,v 1.10 2009/03/21 23:18:22 sno Exp $
Initial import of p5-Module-Pluggable-2.8: p5-Module-Pluggable provides a simple but, hopefully, extensible way of having 'plugins' for your module. Obviously this isn't going to be the be all and end all of solutions but it works for me. Essentially all it does is export a method into your namespace that looks through a search path for .pm files and turn those into class names. Optionally it instantiates those classes for you.
2005-04-18 18:36:15 +02:00
#
Update Module::Pluggable to 3.9. Changes since 3.8: 2009-03-02 - 3.9 Allow inner packages when in a one file situation (suggestion from Christopher Brown) Fix bug with requiring skipped packages (from Jos Boumans) Oked by he@
2009-03-22 00:18:22 +01:00
DISTNAME= Module-Pluggable-3.9
Initial import of p5-Module-Pluggable-2.8: p5-Module-Pluggable provides a simple but, hopefully, extensible way of having 'plugins' for your module. Obviously this isn't going to be the be all and end all of solutions but it works for me. Essentially all it does is export a method into your namespace that looks through a search path for .pm files and turn those into class names. Optionally it instantiates those classes for you.
2005-04-18 18:36:15 +02:00
PKGNAME= p5-${DISTNAME}
SVR4_PKGNAME= p5mpl
CATEGORIES= devel perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=Module/}
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Initial import of p5-Module-Pluggable-2.8: p5-Module-Pluggable provides a simple but, hopefully, extensible way of having 'plugins' for your module. Obviously this isn't going to be the be all and end all of solutions but it works for me. Essentially all it does is export a method into your namespace that looks through a search path for .pm files and turn those into class names. Optionally it instantiates those classes for you.
2005-04-18 18:36:15 +02:00
HOMEPAGE= http://search.cpan.org/dist/Module-Pluggable/
COMMENT= Perl 5 module for automatically adding the ability to have plugins to modules
Updated to version 3.6. Pkgsrc changes: - The package supports installation to DESTDIR. Changes since version 3.4: ========================== 2007-04-07 - 3.6 Include blead perl patch from Craig Berry that gives better Module::Pluggable::Object::search_paths portability as prompted by VMS test failures. 2007-01-29 - 3.5 Patch from Audrey Tang to prevent clobbering of $@
2007-05-27 11:16:28 +02:00
PKG_DESTDIR_SUPPORT= user-destdir
USE_LANGUAGES= # empty
PERL5_PACKLIST= auto/Module/Pluggable/.packlist
Initial import of p5-Module-Pluggable-2.8: p5-Module-Pluggable provides a simple but, hopefully, extensible way of having 'plugins' for your module. Obviously this isn't going to be the be all and end all of solutions but it works for me. Essentially all it does is export a method into your namespace that looks through a search path for .pm files and turn those into class names. Optionally it instantiates those classes for you.
2005-04-18 18:36:15 +02:00
.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink