On Sat, 22 Sep 2001, Stas Bekman wrote:
> I've fixed this problem and committed the new functionality.
cool.
> Now, I think we should enforce a leading - and not allow plain words.
> Consider a situation where there is a test dir called apxs, because we
> decided to test apxs. In the current setup this would be impossible.
> (just like in the previous, if this dir was autogenerated)
not too worried about that, but forcing - or -- is fine.
> There are more problems that I've notices. e.g.:
> If I build perl Makefile.PL with prefork mod_perl, but then run the test
> with the threaded one
> ./t/TEST -apxs /home/stas/httpd/threaded/bin/apxs
>
> the configuration changes partially, e.g. Apache::BuildConfig doesn't
> change. So if you run 'perl build/config.pl' you get the prefork options
> and not the new ones passed via apxs. This is how it was before I've
> committed my latest change.
Apache::BuildConfig shouldn't change in this case. prefork is still the
apxs you used to _compile_ modperl. you only change apxs for the tests to
find a different httpd.
> I'm kinda unsure what the ./t/TEST configuration option are supposed to
> do. What's the scope of the change and etc. It doesn't seem clean to me.
Apache::BuildConfig and t/TEST are two different things. t/TEST only uses
Apache::BuildConfig as a hint to find apxs if not specified elsewhere.
> Another problem: If I try to override configuration options in
> httpd-test/perl-framework they are ignored. Again, tested with the new
> TestRun.pm and the old one -- I see the same behavior. Try:
>
> % /home/stas/perl/ithread/bin/perl5.7.2 Makefile.PL apxs
> /home/stas/httpd/prefork/bin/apxs
> % ./t/TEST
> % ./t/TEST apxs /home/stas/httpd/threaded/bin/apxs
>
> it still invokes the prefork server, I cannot figure out why...
works fine for me, as it always has.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]