Philippe M. Chiasson wrote:
It really doesn't matter how to differ, we could definitely do what you suggest.On Fri, 2003-01-31 at 07:01, Stas Bekman wrote:Doug, have you intended ModPerl::MM to be used only internally to the mod_perl build or by other 3rd party modules as well?
I like it much more than Apache::src. I'm currently porting Apache::Peek and the Makefile.PL is:
use Apache2;
use mod_perl 1.99;
use ModPerl::MM ();
ModPerl::MM::WriteMakefile(
NAME => "Apache::Peek",
VERSION_FROM => "Peek.pm",
);
And it works ;)
Looks very nice to me ;-)The only issue is that ModPerl::MM uses the source build include dirs when compiling things, which should not be used for building 3rd party modules. So should it have a special mode for mod_perl build time, e.g, saying:
ModPerl::MM::BuildWriteMakefile(...)
which will add all the build-time includes, and 3rd party modules will use:
ModPerl::MM::WriteMakefile(...) and it'll know to include only system-wide paths?
How about : ModPerl::MM::WriteMakefile( NAME => "Apache::Peek", VERSION_FROM => "Peek.pm", MODPERL_BUILD => 1, ); For the mod_perl core build ?
I'd even have ModPerl::BuildMM which subclasses ModPerl::MM and overrides things as needed.
__________________________________________________________________
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]
