Devel::TraceUse, simple way to know whether your perl script pulls

the kitchen sink in.

landry@ approved.
This commit is contained in:
espie 2012-09-01 17:11:02 +00:00
parent 8438ca85a5
commit fac0a2dcf4
4 changed files with 32 additions and 0 deletions

View File

@ -0,0 +1,17 @@
# $OpenBSD: Makefile,v 1.1.1.1 2012/09/01 17:11:02 espie Exp $
COMMENT = show modules your program loads
DISTNAME = Devel-TraceUse-2.06
CATEGORIES = devel
# perl
PERMIT_PACKAGE_CDROM = Yes
PERMIT_PACKAGE_FTP = Yes
PERMIT_DISTFILES_CDROM =Yes
PERMIT_DISTFILES_FTP = Yes
MODULES = cpan
CONFIGURE_STYLE = modbuild
.include <bsd.port.mk>

View File

@ -0,0 +1,2 @@
SHA256 (Devel-TraceUse-2.06.tar.gz) = P9GqE2fptAwHYVO+jfeFHru4ce0LfkLxF9K/7pujtEk=
SIZE (Devel-TraceUse-2.06.tar.gz) = 12650

View File

@ -0,0 +1,9 @@
Devel::TraceUse can analyze a program to see which part used which module.
Command-line usage:
$ perl -d:TraceUse myprog.pl
will display a tree of the modules ultimately used to run your
program. (It also runs your program all the way through to the end with
a small startup cost.)

View File

@ -0,0 +1,4 @@
@comment $OpenBSD: PLIST,v 1.1.1.1 2012/09/01 17:11:02 espie Exp $
${P5SITE}/Devel/
${P5SITE}/Devel/TraceUse.pm
@man man/man3p/Devel::TraceUse.3p