Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Taking 'Tie-TinyURL' as an example, it requires 'Test', which is why it lists 'HTML-Widgets-Index' as being dependent. Except that Tie-TinyURL doesn't use 'Test' anywhere. I suspect this is a hangover for when it was ported to use Test::More, which it does use. This threw up a couple of ideas to help filter the results you're getting to something that is perhaps a little more relevent.

    1. Filter based on the 'requires' and/or 'recommends' entries in META.yml. If there is no META.yml, assume all pre-requisites
    • > 1. Filter based on the 'requires' and/or 'recommends' entries in META.yml. If there is no META.yml, assume all pre-requisites are required.

      I'm working on this one already, separating the weight and volatility graphs out into the different dependency layers (configure, build and runtime).

      > It would be helpful if authors noted the 'has_tests_in_t_dir' CPANTS indicator, but then CPANTS listing 'HTML-Widgets-Index' as the definitive source of 'Test' probably needs investigating. 02packages.details.txt.gz should be the definitive source, as used by the CPAN and CPANPLUS installers.

      This is probably the better fix for this. The CPANTS dependency data already includes a "0" distribution that represents the core, so it's not like the CPANTS data model doesn't support that. The problem looks to be that it's preferring a distribution ahead of the core for certain core-only namespaces.