Re: [Module-build-general] bug in Module-Build-0.18

[Ken W. <ke...@ma...>]

On Saturday, May 10, 2003, at 05:56  PM, jk wrote:

> Ken Williams wrote:
>
>>
>> On Friday, May 9, 2003, at 05:05  PM, jk wrote:
>>
>>> 1)  When I ran "./Build test" I got a couple of tests fail, 
>>> indicating they could not find Module::Info.pm.  I do have it 
>>> installed locally (in the  /home/me/data/perl58/  tree), and I do 
>>> have the PERL5LIB environmental variable set to indicate it... is it 
>>> possible that Module::Build doesn't know about PERL5LIB and doesn't 
>>> add it to the @INC array?
>>
>>
>> Nope, not possible - but I did figure out what the problem is here.  
>> I'd seen this problem show up in a couple different ways, and the 
>> reason is that we chdir() a few times in the testing code, and any 
>> relative paths in @INC will be messed up if we load modules after 
>> that.
>>
>> The fix for this, which I've applied in CVS, is to convert all the 
>> @INC paths to absolute paths.
>
> I may be misunderstanding you--if I am, just ignore this--but the 
> paths specified in my PERL5LIB aren't relative. And as you can see, 
> they didn't appear to be getting added to @INC, at least that isn't 
> indicated in the output below.

Hmm, that's strange.  Perhaps you set PERL5LIB after you ran 'perl 
Build.PL'?  'perl Build.PL' freezes @INC so that it'll be the same for 
all subsequent runnings of the 'Build' script.

Oh - note that it can't find B::Module::Info, not Module::Info.  They 
should have both been installed as part of the Module::Info package.  
What happens if you run this one-liner to check whether Module::Info is 
working?

   perl -MModule::Info -le 'print 
Module::Info->new_from_module("File::Spec")->packages_inside'


> Actually, the CPAN problems could just be due to it not using the 
> "config=" string prior to the "sitelib=" string on the command line 
> and problem 1 above.

Yeah, that could do it.  CPAN doesn't know to invoke the 'Build.PL' 
script with this argument.


> I tried it again using CPAN and here are the results below.  Note that 
> I am using CPAN version 1.61,  I don't know if the Module::Build 
> problems still exist in the most recent version of CPAN.

Probably nothing has changed recently.


> The problems appear to be:  1) a couple of the tests fail, and it 
> looks like the @INC doesn't include the paths from my PERL5LIB 
> variable (same as above); and

I don't think that should make any tests fail, it just complains that 
it can't load Module::Info - but notice it also says "All tests 
successful", which is true.

  -Ken