On Thu, 3 Apr 2008 10:19:31 +0200
Torsten Foertsch <[EMAIL PROTECTED]> wrote:
> I am asking because I have had FAIL reports from CPAN testers that don't
> install ModPerl::MM. The way around these reports is using
> BEGIN {
> eval {
> require ModPerl::MM;
&g
have used in all my modules ModPerl::MM. Is that right?
Or should I rather port them to use the former?
ModPerl::MM is the way to go. I suspect you can get away with
ExtUtils::MakeMaker as log as you're not using XS, but I honestly can't
recall what additional magic ModPerl::MM add
dules ModPerl::MM. Is that right?
Or should I rather port them to use the former?
ModPerl::MM is the way to go. I suspect you can get away with
ExtUtils::MakeMaker as log as you're not using XS, but I honestly can't
recall what additional magic ModPerl::MM adds. it could be substant
Hi,
I am a bit confused about what MakeMaker is best to use with mp2 modules.
There is the good old ExtUtils::MakeMaker that is mentioned in
http://perl.apache.org/docs/general/testing/testing.html. How I got there I
don't remember but I have used in all my modules ModPerl::MM. Is that
; resides in /usr/include/apr-0 on my system.
That might be a problem with ModPerl::MM, which I know little about at this
point.
On Dec 28, 2004, at 2:36 PM, Stas Bekman wrote:
Probably vice versa. It looks that Apache::TestMM does more than it
should be doing. It should be handling only test/clean parts.
Ah, and I just copied what was there to create Apache::TestMB.
so you will be asking, right?
Oh, okay, but not today. To
Perrin Harkins wrote:
I'd like to put in a request at this point that no one use Module::Build
for any mod_perl-related stuff until it comes with perl. I like Ken's
work on it, and I appreciate how Module::Build makes interactive installs
easier to write, but I don't want to ask people to install
I'd like to put in a request at this point that no one use Module::Build
for any mod_perl-related stuff until it comes with perl. I like Ken's
work on it, and I appreciate how Module::Build makes interactive installs
easier to write, but I don't want to ask people to install another module
in orde
David Wheeler wrote:
On Dec 28, 2004, at 2:17 PM, Stas Bekman wrote:
David Wheeler wrote:
why Apache::TestMB? It should be ModPerl::MB when it'll appear, right?
Up to you. I used it as an example because I don't really understand
how Apache::TestMM and ModPerl::MM interact.
Apache:
On Dec 28, 2004, at 2:17 PM, Stas Bekman wrote:
David Wheeler wrote:
why Apache::TestMB? It should be ModPerl::MB when it'll appear,
right?
Up to you. I used it as an example because I don't really understand
how Apache::TestMM and ModPerl::MM interact.
Apache::TestMM is only needed o
David Wheeler wrote:
why Apache::TestMB? It should be ModPerl::MB when it'll appear, right?
Up to you. I used it as an example because I don't really understand
how Apache::TestMM and ModPerl::MM interact.
Apache::TestMM is only needed only to add 'make test' and adjust &
On Dec 28, 2004, at 1:53 PM, Stas Bekman wrote:
'perl' => 6.006,
perl 6? :)
Oops. :-)
why Apache::TestMB? It should be ModPerl::MB when it'll appear, right?
Up to you. I used it as an example because I don't really understand
how Apache::TestMM and ModPerl
what if none exists, should Module::Install be used to require
Module::Build?
that's a tricky one. If ModPerl::MB is added, I suppose a Build.PL writer
should still manually require Module::Build (version) and probably ensure
that it's installed via Module::Install, correct? Then ModPerl::MB co
David Wheeler wrote:
On Dec 28, 2004, at 1:26 PM, Stas Bekman wrote:
it can't be any simpler:
That wasn't the whole script, but I found it on search.cpan.org. Here's
how to get it working with Module::Build right now:
use strict;
use warnings FATAL => 'all';
use Apache2;
>
use Apache::TestMB;
#
On Dec 28, 2004, at 1:26 PM, Stas Bekman wrote:
it can't be any simpler:
That wasn't the whole script, but I found it on search.cpan.org. Here's
how to get it working with Module::Build right now:
use strict;
use warnings FATAL => 'all';
use Apache2;
use Apache::TestMB;
# prerequisites
my %requir
way?
Yes, that should be pretty straight-forward, provided you're not
practicing any voodoo in the Makefile.PL script that needs replicating. ;-)
it can't be any simpler:
ModPerl::MM::WriteMakefile(
NAME => 'Apache::Filter::HTTPHeadersFixup',
VERSION_FRO
On Dec 28, 2004, at 12:58 PM, Stas Bekman wrote:
And if we do it the other way around, so you could take
Apache-Filter-HTTPHeadersFixup (the latest is on cpan) add a plain
Build.PL (as if there was no mp2) and then we can add the needed
strings and design ModPerl::MB on the way?
Yes, that should
[disconnect this thread from the unrelated noise]
David Wheeler wrote:
> On Dec 28, 2004, at 8:17 AM, Stas Bekman wrote:
>
>> Why not? I'm not familiar with Module::Build, but doesn't it make
>> possible to subclass itself? Of course ModPerl::MB is only needed if
>> there are 3rd party mp2 modules
On Dec 28, 2004, at 8:17 AM, Stas Bekman wrote:
Why not? I'm not familiar with Module::Build, but doesn't it make
possible to subclass itself? Of course ModPerl::MB is only needed if
there are 3rd party mp2 modules that use M::B. Are there any? May be
David could write a skeleton for a dummy mod
Geoffrey Young wrote:
at any rate, it's a
big win for people writing mp2 stuff for CPAN, and I can see how M::B folks
could take advantage of a similar tool. however, stas is right, that tool
should be distributed with mp2 core so that developers have access to it.
of course, once that's done we
David Wheeler wrote:
> On Dec 27, 2004, at 9:58 PM, Stas Bekman wrote:
>
>> I think all you need to do is to write an equivalent of WriteMakefile
>> (and some other bits). The rest of the stuff in it, is a painful
>> exercise of overriding ExtUtils::MakeMaker MY:: methods.
>
>
> You make it so
21 matches
Mail list logo
