Sreeji K Das wrote: [...]
Hm... Actually I manage the techstack for our development and production servers. The idea was we'll have a document & blindly following the document, anyone can manage the techstack (even those who don't have much idea about mod_perl/apache & other components). So we planned to 'source control' makepl_args. This can be modified only by few ppl. who know what it contain. Then we'll have a line in the doc. like: 'To build mod_perl cd modperl_dir && perl Makefile.PL MAKEPL_ARGS_FILE=<location_of_makepl_args> && make && ....'
Currently the line is: cp /location/of/makepl_args/ <mod_perl_dir> ..other steps...
Basically we wanted to avoid the 'cp' and cluttering of mod_perl dir. So I thought the simplest option is to have an option to take the filename. Ofcourse, I can write & source control a script or have patterns in the command line, but I'd consider the above process (simple copy) or an option to be the simplest :-) (We do not want anyone to accidentally modify makepl_args, as this can cause good amount of issues and would not be easy to track at times.)
Now that you explained that, it seems that a script that contains 'perl Makefile.PL' and the arguments as if they were in makepl_args.mod_perl, seems to be an obvious solution. You can keep it under the source control and will make the life of those non-techies even easier as now they will just need to run:
% sh install-mp1-whatever
% cat install-mp1-whatever #!/bin/sh cd ~/where/modper/is perl Makefile.PL opts \ more opts \ and more opts
The reason I'm trying to suggest an alternative solution, is that most users will never use the
option you suggest, so if we can avoid providing too
many options it's a goodness.
Now I understand. Thanks. I sent this patch, because I thought there'd be many ppl. facing the same problem & this would be useful. Anyway, I would not insist if that's not the case.
It's been out for about 7 years and it's the first time someone has asked for it. If there will be more people asking for it, then sure we can add it.
Also if you are repeatedly updating your build, did
you know of this new mp2 option:
% perl -MApache::Build -e rebuild
http://perl.apache.org/docs/2.0/user/install/install.html#Re_using_Configure_Options
Yes. But I have never tried ('ts in mp1 ?). We rebuild when we upgrade mod_perl or apache or perl - so it's not that frequent.
Ah, for some reason I thought it was for mp2. There is a similar method for mp1 with Apache::MyConfig (see the guide).
__________________________________________________________________ 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
