>>While debugging the problem, I've noticed that if the Makefile.PL in
>>sub-dirs fails, it's silently swallowed. I think it should croak. Is it
>>a problem with MakeMaker in general or something specific to
>>modperl-2.0/Makefile.PL? Most likely the former.
>
>
> this would be a MakeMaker i
On Mon, 8 Apr 2002, Stas Bekman wrote:
> ok, the patch at the end solves the problem. Now any sub-dir can enjoy
> from imported My::test, etc.
looks right to me, +1
> While debugging the problem, I've noticed that if the Makefile.PL in
> sub-dirs fails, it's silently swallowed. I think it sh
Doug MacEachern wrote:
> On Sun, 7 Apr 2002, Stas Bekman wrote:
>
>
>>Yes, but how does it help with Apache::TestMM?
>
>
> well, there's a comment explains what's going on.
> and code to work around the problem.
>
>
>>Its import() already does a similar thing.
>
>
> no, that is not the sa
>>>you could just do:
>>> $self->{conf_opts}->{src_dir} = "$cwd/../..";
>>
> ^^
>
>> $self->{conf_opts}->{src_dir} = "$cwd/../../src";
>>
>>doesn't seem to do the trick, still finds the one installed on the system.
>
>
> try without
On Sun, 7 Apr 2002, Stas Bekman wrote:
> Yes, but how does it help with Apache::TestMM?
well, there's a comment explains what's going on.
and code to work around the problem.
> Its import() already does a similar thing.
no, that is not the same.
> Should it unconditionaly force the aliasing?
Doug MacEachern wrote:
> On Sat, 6 Apr 2002, Stas Bekman wrote:
>
>
>>but that's not what we want. I'm not sure why MY package can be seen
>>only in the first caller of Apache::TestMM::import.
>
>
> see ModPerl::MM::my_import
Yes, but how does it help with Apache::TestMM? Its import() alread
On Sat, 6 Apr 2002, Stas Bekman wrote:
> but that's not what we want. I'm not sure why MY package can be seen
> only in the first caller of Apache::TestMM::import.
see ModPerl::MM::my_import
> $self->{conf_opts}->{maxclients} = 2;
> +$self->{conf_opts}->{libmodperl} = "$cwd/../../src
