Hi
Thanks for all the replies and various solutions proposed to my
question. A brief roundup, for the benefit of anyone who passes this
way in future:
1. Re the 'use lib' stuff, the 'FindBin::Real' does indeed look like
it would get around the problem of the ambiguous 'use lib '../..'
thing. (Acc
-- Ron Savage <[EMAIL PROTECTED]>
Hi Folks
You can use FindBin and set it relative to your script's directory.
Is FindBin::Real a better choice?
FindBin::libs will locate the lib dir's based on your
path (using FindBin).
--
Steven Lembark 85-09 90th
Hi Folks
>You can use FindBin and set it relative to your script's directory.
Is FindBin::Real a better choice?
--
Cheers
Ron Savage, [EMAIL PROTECTED] on 13/01/2006
http://savage.net.au/index.html
Let the record show: Microsoft is not an Australian company
Daniel McBrearty wrote:
Til now I've been using
use lib "../..";
use MyLib::X;
use lib is fine, but do it from your startup.pl and use the full path.
You can use FindBin and set it relative to your script's directory.
I don't know what the working dir of one of teh mod_perl processes
would
You could check %INC to see exactly which file it's including:
--
use MyLib::X;
warn "Using MyLib::X from $INC{'MyLib/X.pm'}\n";
--
John
Daniel McBrearty wrote:
Hi,
If I am developing an app that has a bunch of perl modules as part of
the repository (the modules are dedicated for this
What version of mp are you using:
mp1:
http://perl.apache.org/docs/1.0/guide/modules.html#Apache__PerlVINC___Allows_Module_Versioning_in_Location_blocks_and_Virtual_Hosts
mp2:
Any mp2 you can give every v-host it's own perl interpreter with a
different lib-path:
http://perl.apache.org/d
