David Wheeler wrote:
On Saturday, July 19, 2003, at 10:21 AM, Matt Sergeant wrote:

I would go with the latter. The situation of working with >1 httpd on the same system is reserved for guys like you and I, not the majority of people installing Apache::Test because it was a pre-requisite for things like Apache::Request. So just allow it to be overridden with a Makefile.PL argument.


matt++ This makes al lot of sense to me.

it's not necessarily right that most people will have one httpd server. I think quite many people will have httpd 1.3 and httpd 2.0 installed on the same machine.


Otherwise I'm +1 on your idea, Matt. Though we will need to add some trickery so that Apache::Test will store this info when installed separately and when installed as part of mod_perl 2.0.

Another idea that I had is that Apache::Test will store the default on the first time it's used, rather than during the build time.

As for your earlier question, the docs for Apache::Test should be in the Apache::Test distribution, in the .pm file preferably. I would never think to look anywhere else, especially not the mod_perl guide for module docs.


I'm in complete agreement on this, which is why I took it upon myself to document Apache::TestRequest. You'll see the docs for that module in CVS. Stas has also added some docs for Apache::TestMM, which will be crucial for those of us upgrading from Apache::test. I think the documentation of Apache::Test will happen slowly as motivated (or annoyed) folks send in patches after struggling through it on their own.

Meanwhile we can add a pointer to the Apache::Test tutorial from Apache/Test.pm.


__________________________________________________________________
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]



Reply via email to