You could be optimistic and assume that all dependencies will be in the Makefile.PL files (or equivalent). Of course the reality is that they should be in there anyway, and when they are not, the CPAN-Tester should fail. So while it might be optimistic, it is more how it "should be" anyway.

I would rather use existing modules such as Module::ScanDeps to scan dependencies than to trust that a Makefile.PL or Build.PL or META.yml is accurate.

Errors from missing pre-requisites are not often posted to CPAN Testers, unless the tester notices that it's something not specified in the pre-reqs.

After all, this is for a tool to look for points of failure that the author may not be aware of.

In reply to Re^2: A master-list of module dependencies? by rrwo
in thread A master-list of module dependencies? 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.