a) requires that the module in question has a Meta.YAML file

That's why there's Module::Depends::Intrusive :-)

b) only checks what modules are required to make and load the module. This will miss, for example, modules that do on-the-fly requiring i.e. that depend on another module in certain situations but do not depend on that other module for just making and loading the original module.

True, but it's impossible to determine this programatically in the general case. The other issue is that it conflates build-time, test-time and run-time dependencies. If you're dealing with PPMs, for example, you don't really care about build- or test-time dependencies.

In reply to Re^2: identifying module dependiencies by adrianh
in thread identifying module dependiencies by blueAdept

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.