Re: cvs commit: modperl-2.0/t/response/TestDirective perlrequire.pm

stas@xxxxxxxxxx wrote:
> stas        2003/04/15 20:33:42
>
>   Modified:    t/response/TestDirective perlrequire.pm
>   Log:
>   don't load the whole startup file in the perlrequire's vhost, just adjust
>   @INC so it can find all the needed things
>   
>   Revision  Changes    Path
>   1.11      +2 -1      modperl-2.0/t/response/TestDirective/perlrequire.pm
>   
>   Index: perlrequire.pm
>   ===================================================================
>   RCS file: /home/cvs/modperl-2.0/t/response/TestDirective/perlrequire.pm,v
>   retrieving revision 1.10
>   retrieving revision 1.11
>   diff -u -r1.10 -r1.11
>   --- perlrequire.pm    13 Dec 2002 10:08:09 -0000      1.10
>   +++ perlrequire.pm    16 Apr 2003 03:33:42 -0000      1.11
>   @@ -70,7 +70,8 @@
>    
>        # use test system's @INC
>        PerlSwitches -I@serverroot@
>   -    PerlRequire "conf/modperl_startup.pl"
>   +    PerlRequire "conf/modperl_inc.pl"
>   +    PerlModule Apache2

Most likely the cause of the problem you have reported, Randy, was the 
add_config, but the one running from within a vhost. We had modperl_extra.pl 
executed second time from the vhost running perlrequire tests. I've changed it 
not to load the whole file, but just the needed bits.

Certainly it doesn't solve the problem, but I'm devising a separate test to 
test just add_config in the vhost. I just want to have the test suite work 
100% and have the 1.99_09 release out of the door asap.

Please let me know what is the status on win32 with the current mod_perl cvs.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@xxxxxxxxxx http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com