Geoffrey Young wrote: > >> >> 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 > > > > I ran (and still run) into this problem some time ago > > http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=99010804314607&w=2 > > I've since been able to work around my particular problem by using > > <Perl> > # stuff to get Apache::Test to recognize shared object files > use blib; > </Perl> > > in my extra.conf.in, though I think this runs in to trouble as well with > XS-based modules, which throw subroutine redefined warnings.
and 2.0 doesn't have perl sections yet :( > any thoughts on using the blib pragma over the various use lib stuff in > modperl_inc.pl? I think we need to rethink the whole concept of how Apache::Test and its elements manipulate @INC. What are the demands from you Geoff, as its user? Now that you mention this my recent patch suggestion seems to be bogus since blindly adding Apache2/ to @INC will break testing of modules with mod_perl 1.0 if both 1.0 and 2.0 are installed. __________________________________________________________________ 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]
