Brian C. Thomas wrote:
Hi
I have read through the lists looking for issues related to mp2 and
@INC, and have read the part about "+Parent" and virtual hosts. What
about the following scenario?
One apache2 server w/ mp2 (no virtual hosts) and several perl coders
using the server as a development site.
Is there a "best" way to configure the apache/mp2 setup so that there
doesn't have to be constant additions to "startup.pl" to adjust the
INC path? What about name space conflicts?
For example, I want developer1 to use /dev1, and developer2 /dev2. I
want each developer to be able to build functions below there
directories in as many subdirectories as projects they have going on.
I don't want developer1's "functions.pm" code to interfere with
developer2's "functions.pm".
Is such an arrangement even possible under mp2? I've been using
Apache1/mp1 and this works fine, but all my tests with mp2 end up
giving me
I suppose you are looking for this:
http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_
ModPerl::Registry: Can't locate FUNC.pm in @INC (@INC contains:
/usr...) types of errors. And for identically named files (e.g.
functions.pm above), I get the subroutines from the first listed
functions.pm in the @INC path, which are the wrong ones being called
for.
Sure, you hit the old 1.0 problem described here:
http://perl.apache.org/docs/1.0/guide/porting.html#Name_collisions_with_Modules_and_libs
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
