Doug MacEachern wrote: > +1 > > On Thu, 27 Jun 2002, Stas Bekman wrote: > > >>Currently we have the following order in the autogenerated httpd.conf: >> >>Include "t/conf/extra.conf" >>[ response config sections come here] >>PerlSwitches -Mlib=t >>PerlRequire t/conf/modperl_startup.pl >> >>so if extra.conf is trying to preloading some Perl module, it won't do >>the right thing because @INC is not adjusted at this point yet to point >>to the dev libs. which in the best case fail, and the worse case it'll >>use the wrong previously installed system-wide module. >> >>I suggest the following order: >> >>PerlSwitches -Mlib=t >>PerlRequire t/conf/modperl_startup.pl >>Include "t/conf/extra.conf" >>[ response config sections come here]
This is not possible with the current way Apache::Test configures things. Since mod_perl's config hooks are run after the rest of the configuration is done, Include "t/conf/extra.conf" will always come up before mod_perl startup and other perl files. Perhaps we need to find a way for mod_perl or any other subproject to be able to supply a set of perl and conf files in a way that they will be grouped together? For example, during the SUPER::configure, don't configure files which start with a magic prefix or any prefix such that there is an '_' in it. And then mod_perl's configure will pickup the '_' files or files starting with the magic prefix. e.g. modperl_extra.conf.in -- __________________________________________________________________ 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
