prompt? I hope that was just a slip :) I much prefer the current method (die with an error message) over the libapreq test method (wait indefinitely for an entry or ! to skip).
Nope, not a slip. If you install manually I agree that die is better than prompt. If you install with CPAN, which it seems the majority do, it's better to prompt, since it's not trivial to tell CPAN which options need to be supplied during 'perl Makefile.PL'.
ah. I never use CPAN.pm, so I'm always forgetting about it.
You know what? I think we should educate the users to use env vars.
doesn't that sorta happen now - throw an error message if it can't find a suitable Apache? granted, it could be more explicit, maybe even including your CPAN shell one-liner below.
The problem is that we have two mod_perl versions, so setting the APACHE env var is not a solution, since how do we set it for 2 versions. What I mean is, I'd like to have a set of env vars in my .profile/.cshrc/.whatever and never think twice, just selecting the version I want to build with. So I'd have:
env MOD_PERL=1 perl -MCPAN -eshell and env MOD_PERL=2 perl -MCPAN -eshell
if we could achieve that, it'd be fantastic. So may be we need to support APACHE and APACHE2, APXS and APXS2, so if we see MOD_PERL=2, we look for APACHE2 and APXS2 env vars.
well, I can see how that would benefit developers, but I'm not so sure that we have to go through all that trouble for end-users. typically, they would be using/developing either one version or the other and not messing around with both (at least not in the volume that you do :) so, I'd expect that educating them as to
$ APXS=/usr/local/apache2/bin/apxs perl -MCPAN -eshell
is quite sufficient. personally, I have apache1 and apache2 aliases set up to do my exporting for me :)
I'm also still bothered with this MOD_PERL vs. MODPERL thing, we really need to stick to a single way to write it. (same for macros.)
yeah.
at any rate, I guess there's lots to do. I'll get to my part and try to fill in the gaps as I can. especially as my OSCon talk (and upcoming perl.com article) is on Apache::Test :)
Oh, wow, that's cool! Hopefully I'll get the rest of the fixes in the next few days.
excellent :)
> > Also I'm planning to release Apache::Test on CPAN soon. What do you think?
that's great. actually, its a long time in coming.
if you're thinking about doing this, a mod_perl 2.0 CPAN release might also be nice - that way you can have a PREREQ_PM mod_perl version that corresponds to an Apache::Test CPAN release, thus making third party modules (or said article :) that support mod_perl 1.99_09 capable of being used as examples of how Apache::Test works for both 2.0 and (if you want to get it from CPAN) 1.0. I don't mean to say that this will be required for each release, but we've come pretty far on third party module support recently so it would be nice to have them in sync once we settle down.
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
