>>>>> On Sat, 12 Apr 2008 08:27:30 -0400, "David Golden" <[EMAIL PROTECTED]> >>>>> said:
>> Maybe a perliminary solution would be some sort of heuristics for >> CPAN::Reporter or CPAN.pm: if the result is "PL FAIL" and no YAML >> module is installed (i.e. $CPAN::META->has_inst($yaml_module) returns >> false) and there's a META.yml available in the distribution and it >> contains the string "configure_requires" (not parsing it, just doing a >> grep), then DISCARD the report. > I cringe in horror at the thought -- but concede that you're probably > right. Putting it in the "bug" section of the Todo list now. I do not think it's a bug in CPAN::Reporter, it is in CPAN.pm. I think CPAN.pm *must* (sort of) refuse to build a module when it - has a META.yml containing the string configure_requires and the perl - has no YAML processing module Just like it makes no sense to test a module with a broken Test::Harness, it makes no sense to build a module that depends on something we cannot parse. CPAN.pm must present immediate feedback to the user when something is going severly wrong. Details of the implementation are not yet clear to me but they will likely affect how CPAN::Reporter can then deal with the case when we arrive at the test phase. -- andreas
