On Dec 29, 2004, at 10:20 PM, David Wheeler wrote:
I think, looking at the code, that all you need to do is override the
find_pm_files method like this:
sub find_pm_files {
my $files = shift->SUPER::find_pm_files;
for my $file (keys %$files) {
$files{$file} = File::Spec->c
David Wheeler wrote:
On Dec 29, 2004, at 6:49 PM, Geoffrey Young wrote:
for a bit of history here, what happens with mp2 is that if it sees a mp1
installation it installs everything under site_lib/Apache2/ (like
Apache::Filter becomes Apache2/Apache/Filter.pm) as to not collide with
existing module
On Dec 29, 2004, at 6:49 PM, Geoffrey Young wrote:
for a bit of history here, what happens with mp2 is that if it sees a
mp1
installation it installs everything under site_lib/Apache2/ (like
Apache::Filter becomes Apache2/Apache/Filter.pm) as to not collide with
existing modules in the mp1 namespa
Ken Williams wrote:
On Dec 29, 2004, at 8:35 PM, Stas Bekman wrote:
Ken Williams wrote:
On Dec 29, 2004, at 8:22 PM, Stas Bekman wrote:
with MM we override MY::constants so things end up in Apache2/
subdirs in blib/. That's about it. so if normally a file would be
installed under /foo/bar it'll b
On Dec 29, 2004, at 8:35 PM, Stas Bekman wrote:
Ken Williams wrote:
On Dec 29, 2004, at 8:22 PM, Stas Bekman wrote:
with MM we override MY::constants so things end up in Apache2/
subdirs in blib/. That's about it. so if normally a file would be
installed under /foo/bar it'll be now installed unde
hi ken :) many belated congrats on your new addition :)
Ken Williams wrote:
>
> On Dec 29, 2004, at 8:22 PM, Stas Bekman wrote:
>
>> with MM we override MY::constants so things end up in Apache2/ subdirs
>> in blib/. That's about it. so if normally a file would be installed
>> under /foo/bar i
Stas Bekman wrote:
Ken Williams wrote:
Um, doesn't that really break things (like, say, perl) that are
looking for modules in @INC and not map( "$_/Apache2", @INC)?
Break what things? Any perl program that wants to find mp2 modules
starts with 'use Apache2' or -MApache2.
What Stas means is that t
Ken Williams wrote:
On Dec 29, 2004, at 8:22 PM, Stas Bekman wrote:
with MM we override MY::constants so things end up in Apache2/ subdirs
in blib/. That's about it. so if normally a file would be installed
under /foo/bar it'll be now installed under /foo/bar/Apache2.
Um, doesn't that really bre
On Dec 29, 2004, at 8:22 PM, Stas Bekman wrote:
with MM we override MY::constants so things end up in Apache2/ subdirs
in blib/. That's about it. so if normally a file would be installed
under /foo/bar it'll be now installed under /foo/bar/Apache2.
Um, doesn't that really break things (like, say,
Ken Williams wrote:
On Dec 29, 2004, at 2:12 PM, Stas Bekman wrote:
But M::B doesn't support XS yet, so that's moot.
M::B has supported XS since it was in diapers.
Well, I've never used M::B, someone (?) said that it doesn't. If it does
then great.
so David and I were only t
On Dec 29, 2004, at 2:12 PM, Stas Bekman wrote:
But M::B doesn't support XS yet, so that's moot.
M::B has supported XS since it was in diapers.
so David and I were only talking about ModPerl::MB subclass of M::B
which will do the usual thing as any another non-mp2 module does, but
wil
> In which case I've lost you, since ModPerl::MM doesn't call
> Apache::src->new->inc. I guess, you've meant:
>
> http://perl.apache.org/docs/2.0/api/ModPerl/MM.html#C_INC_
>
> is that right?
yes.
/me sighs
all I was doing was showing how things worked in mp1 and, thus, what mp2
does _equival
Geoffrey Young wrote:
note that even without the win32 foo mp1 still needs the call to
Apache::src->new->inc to find the proper header files.
wo, wo, wo, nobody was even suggesting to do that for mp1. mp2 was the
only one.
eesh... I wasn't suggesting that. I was just showing what ModPerl::MM doe
>> note that even without the win32 foo mp1 still needs the call to
>> Apache::src->new->inc to find the proper header files.
>
>
> wo, wo, wo, nobody was even suggesting to do that for mp1. mp2 was the
> only one.
eesh... I wasn't suggesting that. I was just showing what ModPerl::MM does
behi
7;ve seen in just
the last week, I'm not the only one that is writing XS extensions for mp2 :)
But M::B doesn't support XS yet, so that's moot.
so David and I were only talking about ModPerl::MB subclass of M::B which
will do the usual thing as any another non-mp2 module does, but
> From what I understand, the whole
> point of that module is to detect when both mod_perl1 and mod_perl2 are
> installed, and, when they are, to add "Apache" to the install path
> before installing mod_perl2-specific modules.
well, that's not the _whole_ point :) a mp1 Makefile.PL that needs to
and Geoff about providing the same
functionality for modules that want to use Module::Build, the question
came up as to how they should go about it. I think what makes the most
sense is for a ModPerl::MB module to subclass Module::Build and
override the appropriate method to append "Apache&
17 matches
Mail list logo
