Thanks for the help Salih.
> I am not sure if this the optimal way to do it but usually I do the
> following.
>
> 1. I usually run scandeps.pl (used internally by pp) on the
> "to-be-packaged" scripts and figure out if there is something missing.
I tried this first and got a rather unoptimized response:
$ scandeps.pl script.cgi
No modules found!
In fact there, there is a "use Module::Name" declaration right at the
top of the script in in plain site. A more helpful diagnostic message in
this case would have been:
I saw the following modules were attempted to be loaded, but couldn't
be:
use My:Module
...
Perhaps you need to set PERL5LIB?
...because that's what I need to do:
$ PERL5LIB=../../../config:../../../perllib scandeps.pl script.cgi
> 2. It needs sometimes some cycles before finding all dependencies,
> especially if some modules do runtime requires.
> 3. I unzip the resulting par file (it is a zip archive) and point the
> script to the lib/ directory (either by a use lib... or
> -I/myapplication/lib)
I hate to be dense, but, what resulting par file? (what syntax did you
use) The documentation for "par.pl" only seems to refer to making a Par
file for a CPAN distribution.
Do I need to create a MANIFEST and Build.PL or Makefile.PL first? I was
Mark
