The only way I can see to produce this information is to download each module and use existing dependency scanning modules (there are two or three of them, at least).
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.
That's a lot of work I'd rather avoid if somebody else has dependency information available.
(Also, if my idea overlaps with an existing project, I'd like to know about it too.)
I would email the CPAN-Testers list, as well as the perl-qa list (home of the Phalanx project) as well as the perl modules list(s),... that is if you haven't done that already. Other than that good luck and keep us updated as to your project, I think it could be a very useful thing for the community.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|