This tells me that if I want to write a script that builds a number of modules plus apache, I will have to answer a prompt when the script gets to the mod_perl portion of my script (unless I want to make mod_perl the last module built and use "DO_HTTPD=1" instead of doing a make inside the apache directory).
Nope. Just say 'NO_HTTPD=1' and drop 'PREP_HTTPD=1'. It looks like the 3 (DO, NO, PREP) are self exclusive.
So 'PREP_HTTPD=1' is not needed? All it does is force the prompt? And here I thought it was setting a flag to prepare the httpd code.
I'm pretty sure 'PREP_HTTPD=1' is needed. I went through the process of trying to figure this out about a month ago, and found the documentation pretty confusing (confusing enough that it gave me the 'opportunity' to look into the Makefile internals, which was a first for me, which probably wasn't such a bad thing...). To me, it seems that all the flags are useful, but (a) the docs could probably be cleaned up, and (b) there should probably be a way to avoid the prompt. But it's all pretty minor stuff...
I guess Bryn has given the perfect reason of why nobody has complained in 7 years. People try things as documented, they don't do what is expected and they figure out on their own what should be done, but then they just move on instead of trying to contribute a patch that fixes incorrect/confusing/missing docs.
I wish more people who get helped here were giving something back to the project and help others who will come after... It's not like you need C skills to make the docs betters. Oh well...
__________________________________________________________________ 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
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
