Re: [Module::Build] You underestimate the problem

[David G. <da...@hy...>]

Chris Dolan wrote:
> The problem with Yves' suggestion to generate META.yml on the 
> installation host, as I've said before, is that it renders META.yml 
> pointless.  The goal of META.yml is to create a non-executable source of 
> accurate metadata about a package.  If you have to download the package 
> and run Build.PL to generate META.yml, then why bother using META.yml?  
> In that case just use Build.PL itself.

This was the point I was getting at.  Otherwise, every indexer will need 
to run in a chroot jail and will only have valid information for the 
configuration of the indexer.

That said, Adam's list of special cases is formidable, though I'm not 
sure that every eventuality needs to be supported.  I'd be happy if it 
covered 80% of cases.

Is there a reference to the existing mini-language proposal?

As an intermediate measure, what do people think about adding a 
"may_require" field to the META.yml spec as something in between 
"requires" and "recommends".  This would be for things that might get 
required depending on local configuration.

For a mix of human and indexer useful info, it could function like 
recommends, with a text description and a list (apologies if my YAML is 
poor):

may_require:
   - gpg not available:
     - Module::A
     - Module::B
     - etc
   - older Win32 (e.g. Win95, Win98):
     - Win32::C
     - Win32::D

Regards,
David Golden