Re: [Module-build-general] [BUG] ./Build dist problem with scanning for packages

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

On Monday, July 7, 2003, at 02:30  PM, Dave Rolsky wrote:

> Ok, I just found a somwhat serious bug in the 0.18_04 release, and I 
> think
> it's still present in the CVS version.
>
> If I run "./Build dist" on a new distro, it tries to load all the .pm
> files in the MANIFEST file and scan them for packages via Module::Info.
>
> But if you've never installed the distro at hand, then loading the 
> various
> module may fail unless the ./lib (or equivalent) directory is included 
> in
> your lib path.
>
> I'm not sure if this is a new bug or if I've just not used 
> Module::Build
> for an entirely new module, which is what provoked the problem.

Argh, you're right.  I wish Module::Info could override CORE::use() or 
something so it wouldn't have to run any other modules to get the info.

In fact, looking through Module::Info now, I'm not sure it's really the 
right tool to be using here.  It's really not very accurate in a lot of 
its information, and there's a case to be made that we should just be 
using the PAUSE/CPAN heuristics anyway.

  -Ken