> > So should I just give up the idea of APACHE_TEST_CONFIGURE and move on
> > with Apache::TestUtil like vhost_alias does?
>
> i think so.
>
> > Let's just think for a sec, whether we may have some other reason for
> > having something like APACHE_TEST_CONFIGURE? Was the creation of the files
> > on the fly the only reason for wanting this?
>
> we can always revisit later if needed.
> would be nice if the .t files do something like this in any case to make
> things clear:
>
> configure();
>
> sub configure {
> t_mkdir ...;
> }
It doesn't work ;(
I need to autogenerate files which are needed during server startup. The
test's configure won't be run before the server gets started. It's an egg
and chicken problem.
So should I try to make all tests require'able outside httpd and get the
APACHE_TEST_CONFIGURE working or do you have any other ideas?
Of course I can just cvs commit the files, but it makes the test spread
out across too many files, and I don't like it.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
