--- Stas Bekman <[EMAIL PROTECTED]> wrote: > Sreeji K Das wrote:
mod_perl build currently requires that makepl_args.mod_perl is present in one of
current, '..' or $ENV{HOME}.
...<snip>
Why not do the simple:
perl Makefile.PL `cat /whereever/your/file/is/makepl_args.mod_perl`
Then I lose the flexibility of having comments & neat formatting in the config. file. I'll have to escape all the newlines. Also, this works only on Unices.
This is not a problem with Perl :)
% perl Makefile.PL `perl -l0ne '/^([^#\n\r]+)/ && print "$1 "' /whereever/your/file/is/makepl_args.mod_perl`
So if your input file is:
# comment FOO=bar # comment FOO2=bar2 # wow # comment FOO3=bar3
you get:
FOO=bar FOO2=bar2 FOO3=bar3
This is certainly not something that you'd want to remember and type from scratch ;) I just tested it with the above input, so that pattern may have problems.
Comparitively, perl Makefile.PL MAKEPL_ARGS_FILE=/whereever/your/file/is/makepl_args.mod_perl
looks better (IMHO).
You have to type that every time aren't you? And I suppose that you don't type but write a script that will do the work for you. Am I right? In which case why not having those options in that script? I have to maintain a few dozens of mp2 builds and I use a script for each separate one. The benefit is that I can control, tune and adjust each of these scripts when I need to without affecting the others. If I were to use makepl_args.mod_perl I'd be doomed to inadvertendly affect other builds when I modify it.
So instead of doing:
% perl Makefile.PL \ MAKEPL_ARGS_FILE=/whereever/your/file/is/makepl_args.mod_perl
You end up doing an even simpler:
% build-mp2-foo-bar
e.g. I have in my ~/bin:
run.prefork run.prefork.2.0.36 run.prefork.2.0.40 run.prefork.2.0.43 run.prefork.2.0.46 run.prefork.5.6.0 run.prefork.5.6.0-ithreads run.prefork.5.6.1 run.prefork.5.6.1-ithreads run.prefork.5.6.2 run.prefork.5.6.2-ithreads run.prefork.5.6.2-perlio run.prefork.5.8.0 run.prefork.5.8.0-ithreads run.prefork.5.8.0-ithreads-nodebug run.prefork.5.8.1 run.prefork.5.8.1-ithreads run.prefork.5.8.1-ithreads-noshrplib run.prefork.5.8.1-noperlio run.prefork.5.8.2 run.prefork.5.8.2-ithreads run.prefork.5.8.2-ithreads-noshrplib run.prefork.5.8.2-noperlio run.prefork-all-shared.5.8.1-ithreads run.prefork.blead run.prefork.blead-ithreads run.prefork.blead-multi run.prefork.install run.prefork.MP_AP_PREFIX run.prefork.MP_AP_PREFIX_SRC run.worker run.worker.2.0.36 run.worker.2.0.40 run.worker.2.0.43 run.worker.2.0.46 run.worker.2.0.46-5.8.0 run.worker.5.6.1 run.worker.5.6.2 run.worker.5.8.0 run.worker.5.8.1 run.worker.5.8.1-hash-seed run.worker.5.8.1-noshrplib run.worker.5.8.2 run.worker.5.8.2-noshrplib run.worker.install
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.
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
__________________________________________________________________ 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
