Re: [Module-build-general] Module::Info

[Dominic M. <do...@se...>]

Ken Williams wrote:
> Hmm, this is a tough problem that seems to be inherent in the way 
> Module::Info scans for packages.  The problem is actually that it 
> compiles the module, then walks the parse tree - but during compilation, 
> any dependencies need to be available.
> 
> If we could tell Module::Info to somehow ignore any missing modules from 
> 'use' statements, that might be helpful.  Otherwise I'm not sure 
> Module::Info is a completely viable approach, even though it's probably 
> "the right way" to do things.

Perhaps the best solution for the moment is a documentation patch?  It's 
not a major problem, as it's only going to affect packagers, not users. 
  And even for them, it's only going to affect one small piece of their 
package, META.yml.

Something for the TODO section, perhaps?

    When generating META.yml, you may see errors from Module::Info.  This
    is because to build the I<provides> section, Module::Info compiles
    each source file to determine what packages it contains.  If that
    module requires dependencies, they will not be loaded if they are
    part of the same distribution, because they might not have been built
    yet.  Patches to fix this welcome.

-Dom