I am working on a module that when given a CPAN distribution, will return which modules the distribtion requires (by parsing the Makefile.PL using Module::MakefilePL::Parse if the META.yml file is not available).

A companion module will actually try to fetch the distribution information from CPAN (since it can query a .meta file if it exists before downloading an entire distribution).

Because it is more closely tied to CPAN and works with distributions rather than modules, I am thinking of calling it CPAN::Distribution::Depends.

Comments or suggestions about the namespace would be appreciated.

FYI--I am writing yet another module to do this because existing modules either do not work on my platform or they require preqrequisite modules to be installed. Basically they either compile the module or run Makefile.PL/Build.PL and see what modules are asked for. I'd rather use a safer (and I think faster) method to partially-parse the Makefile.PL if no META.yml is available.

Some tests using all the latest distribution on CPAN show that it works for all but a handful of distributions.

This is actually part of a larger project to show test results (organized by platform) of module dependencies. If there is a failure in the dependency tree, authors can check for this.

In reply to What to name a module? by rrwo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.