Doug MacEachern wrote:
But ewww, this is one of those 'we MUST be on the same system as the server' things.. :-(
yeah. we have support for the modperl test.pm's to have a CONFIGURE routine that is run when .conf.in -> .conf generation happens. we should probably do similar for .t files.
that means scanning .t files for CONFIGURE and requiring them, when you require them they will be run. Which will be very slow.
_____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
