Adam Kennedy wrote:
missing_no_index:
Only the libraries (and .pod docs) in your dist should be indexed)
things in inc/ and t/ and examples/ etc should NOT be indexed. Thus,
there should be a no_index entry in the meta.yml for all of these directories (if they have .pm files in them).

I like it. (N.B. Since t/ is not indexed already and many people write test support modules, I'd recommend against needing those to be explictly included in a no_index)


has_perl_dependency:

My initial thought was "great"! Then I realized that encouraging people to stick one one in may be worse than having none at all as quick (but incorrect) information may be less desireable than no information.

-----------------------------------------------

bad_perl_dependency:

The caching and mass processing facilities in PPI are getting close to being able to regularly process all of CPAN. The first demo of this I'm hoping to do is a use of Perl::MinimumVersion to find cases where a module is listed as working with (for example) Perl 5.005, but the module syntax shows that it needs 5.006. (and thus the version dependency is wrong).

I later plan to expand this to include cases where it says it should run with 5.005, but it has a dependency on some other module (recursively) that needs 5.006, or you accidentally put 5.006 code in your test scripts, and thus fails depsite the code in that actual module for the module being ok.

I like this a lot. I'd drop "has_perl_dependency" and just have "bad_perl_dependency" fail if there is no perl dependency listed. I.e., assume that no perl dependency is equivalent to "use perl 0" or maybe some arbitrarily old version of perl 5 (e.g. 5.004).

Regards,
David Golden

Reply via email to