On Sun, 16 Sep 2001, Stas wrote:
> The actual test is the smallest example I can come up with. What I want
> is to create two identical .pm files, with different contents and make
> sure that vh interpreter loads a file different from the main
> interpreter. The test passes if each one fetches its own file.
that should be possible.
> So what I want is for the main interpreter to have only the path:
> t/htdocs/testdirectives/main
> in @INC and the vh interpreter to have only the path:
> t/htdocs/testdirectives/vh
of course more than one path in @INC is require to find the Apache::*
modules and such. you should be able to configure such that the main
server has t/htdocs/testdirectives/main in its path and
t/htdocs/testdirectives/vh in the vhost path, i don't understand why this
currently wouldn't work.
> Yes, I know. I was just suggesting to have a different functionality a
> special case for test. So Apache::Test will automatically require
> modperl_startup, or whatever is required for running tests if it creates
> the <Location> with vh in it? thus removing this burden from the test
> writers.
most test writing won't be writing tests for +Parent.
i don't see adding this as much of burden:
PerlRequire @t_dir@/conf/modperl_startup.pl
> How about having this as an option? So by default PerlSwitches would be
> inherited at all:
you can turn off inherting already with something like:
PerlSwitches /dev/null
> I think that if we inherit PerlSwitches by default it can bring
> surprising results, when the order of path in @INC, can break things.
ok, i will restore the old behavior so PerlSwitches is not inherited.
we can add support for something like:
PerlSwitches +inhert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
