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

20 lines
528 B
Makefile
Raw Normal View History

Updating package for p5 module PadWalker from 1.7nb1 to 1.9 and set license to the value from META.yml. Upstream changes: 1.8 Thu 25 Jun 2009 21:17:17 BST - Apply patches from doy (#41710) and nothingmuch (set_closed_over). 1.9 Fri 26 Jun 2009 10:01:17 BST - Identical to 1.8, but with the bogus metadata ._ files removed from the distributed tar file.
2009-07-07 23:19:09 +02:00
# $NetBSD: Makefile,v 1.3 2009/07/07 21:19:09 sno Exp $
Added devel/p5-PadWalker version 1.7 PadWalker is a module which allows you to inspect (and even change!) lexical variables in any subroutine which called you. It will only show those variables which are in scope at the point of the call. PadWalker is particularly useful for debugging. It's even used by Perl's built-in debugger. (It can also be used for evil, of course.) I wouldn't recommend using PadWalker directly in production code, but it's your call. Some of the modules that use PadWalker internally are certainly safe for and useful in production.
2008-07-14 11:26:02 +02:00
Updating package for p5 module PadWalker from 1.7nb1 to 1.9 and set license to the value from META.yml. Upstream changes: 1.8 Thu 25 Jun 2009 21:17:17 BST - Apply patches from doy (#41710) and nothingmuch (set_closed_over). 1.9 Fri 26 Jun 2009 10:01:17 BST - Identical to 1.8, but with the bogus metadata ._ files removed from the distributed tar file.
2009-07-07 23:19:09 +02:00
DISTNAME= PadWalker-1.9
Added devel/p5-PadWalker version 1.7 PadWalker is a module which allows you to inspect (and even change!) lexical variables in any subroutine which called you. It will only show those variables which are in scope at the point of the call. PadWalker is particularly useful for debugging. It's even used by Perl's built-in debugger. (It can also be used for evil, of course.) I wouldn't recommend using PadWalker directly in production code, but it's your call. Some of the modules that use PadWalker internally are certainly safe for and useful in production.
2008-07-14 11:26:02 +02:00
PKGNAME= p5-${DISTNAME}
CATEGORIES= devel perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=../../authors/id/R/RO/ROBIN/}
MAINTAINER= pkgsrc-users@NetBSD.org
HOMEPAGE= http://search.cpan.org/perldoc?PadWalker
COMMENT= Play with other peoples' lexical variables
Updating package for p5 module PadWalker from 1.7nb1 to 1.9 and set license to the value from META.yml. Upstream changes: 1.8 Thu 25 Jun 2009 21:17:17 BST - Apply patches from doy (#41710) and nothingmuch (set_closed_over). 1.9 Fri 26 Jun 2009 10:01:17 BST - Identical to 1.8, but with the bogus metadata ._ files removed from the distributed tar file.
2009-07-07 23:19:09 +02:00
LICENSE= ${PERL5_LICENSE}
Added devel/p5-PadWalker version 1.7 PadWalker is a module which allows you to inspect (and even change!) lexical variables in any subroutine which called you. It will only show those variables which are in scope at the point of the call. PadWalker is particularly useful for debugging. It's even used by Perl's built-in debugger. (It can also be used for evil, of course.) I wouldn't recommend using PadWalker directly in production code, but it's your call. Some of the modules that use PadWalker internally are certainly safe for and useful in production.
2008-07-14 11:26:02 +02:00
USE_LANGUAGES= c
PERL5_PACKLIST= auto/PadWalker/.packlist
PKG_DESTDIR_SUPPORT= user-destdir
.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink