Mark Stosberg wrote:
>>$ 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
>>
>>
>>
>
>
Does it report something when you use Modules in @INC? and what version
of Module::ScanDeps are using ? Previous versions did not work properly
without CPANPLUS installed. The last version work without, make sure
that scandeps.pl works correctly first!
>>>>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
>>
>>
>>
>
>
Oops, or maybe I was too concise ;-)
What I was meaning:
pp -o out.par cgifile
or when necessary
pp -M This::Module --addfile=thisdir/ -addfile=thisfile -o out.par cgifile
then unzip out.par
out.par is now a self contained perl application in a zipped archive,
after unzipping it you will see lib/ script/ etc... try to see if it works
if everything is ok, you may then try the self contained cgi script
-salih
