From: Jeff M. <jef...@vi...> - 2003-02-08 21:29:26
|
Hi, I tend to put any perl modules a program requires into that program's own perl library. I then add the library path to my perl program. When I install the program I do this: perl -I /path/program/perllib Makefile.PL PREFIX=3D/path/program/perllib LI= B=3D/path/program/perllib The program then has this: #!/bin/perl use FindBin qw($Bin); use lib "$Bin/perllib"; <rest of program> Why do I do this? This helps prevents an accidental update of perl modules affecting the program. I also put the source of the modules (the tar files) into CVS, as you can not depend on CPAN to have that version of the module handy. Ashley's recent problems with Image-Info-1.12 reminded me of this method. Perhaps we should also include the modules IDS requires as part if the total package. This should lessen support headaches. I'll send my makefile that compiles/installs the modules at a later date (having trouble with ImageMagick at the moment). What are everyone else's thoughts? --=20 Jeff Macdonald <jef...@vi...> Into birding? Check out http://www.migratus.com |