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 ;)
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?
__________________________________________________________________
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]
- Re: using ModPerl::MM as a replacement for Apache::sr... Stas Bekman
- Re: using ModPerl::MM as a replacement for Apach... Philippe M. Chiasson
- Re: using ModPerl::MM as a replacement for A... Stas Bekman
- Re: using ModPerl::MM as a replacement for Apach... Geoffrey Young
- Re: using ModPerl::MM as a replacement for A... Stas Bekman
