James E Keenan wrote:
Michael G Schwern wrote:
Oh yeah, forgot about that. Its not in your path so you have to give
it the full path to the program.
The directories in blib have no relation to where the file came from.
Non-binary executables always go into blib/script. Binary
On Fri, Jul 08, 2005 at 11:17:44PM -0400, James E Keenan wrote:
One other curiosum: As a result of my Phalanx work, I've gotten in the
habit of using File::Temp to create 'anonymous' directories and files in
which to conduct testing. I tried that here:
my $tdir = tempdir( CLEANUP =
I am having trouble figuring out how to test a Perl script which
functions as a command-line utility and which is included with a
CPAN-style distribution.
For purpose of discussion, let's call the distribution XYZ and the
script xyz.pl. My distribution has the following standard structure:
On Fri, Jul 08, 2005 at 07:47:42PM -0400, James E Keenan wrote:
scripts/
xyz.pl
Make sure MakeMaker is told about that script via EXE_FILES or it won't know
to do anything with it (like install it).
I would like to be able to write tests which call xyz.pl with different
Michael G Schwern wrote:
Make sure MakeMaker is told about that script via EXE_FILES or it won't know
to do anything with it (like install it).
Check. In Makefile.PL, I already had:
EXE_FILES= [
'scripts/modulemaker',
],
[snip]
Michael G Schwern wrote:
Oh yeah, forgot about that. Its not in your path so you have to give it
the full path to the program.
The directories in blib have no relation to where the file came from.
Non-binary executables always go into blib/script. Binary executables
go into blib/bin.
