The thread you cited refers to my Devel::Modlist package, but the example they use overlooks an option called "cpandist":
perl -d:Modlist=cpandist,nocore,stop upj_post.pl
(The upj_post.pl is one of my sample scripts that demonstrates the SOAP interface to the use Perl; journal system.)
This produces the output:
G/GA/GAAS/Digest-MD5-2.16.tar.gz
G/GA/GAAS/libwww-perl-5.64.tar.gz
K/KU/KULCHENKO/SOAP-Lite-0.51.tar.gz
If the cpan option is used instead of cpandist, it simply refers to the first module of a given package, since "install Module" from within the CPAN shell is sufficient:
perl -d:Modlist -MDevel::Modlist="cpan,noversion,nocore,stop" upj_post.pl
Digest::MD5
HTTP::Cookies
SOAP::Lite
An important note: all of these examples used the "stop" option, which stops prior to the execution of the program, and prints results then. If any of the libraries listed were to include others, you would see them here unless they were included at compile-time. For example, if the nature of the run included encoding MIME data using base-64, LWP probably doesn't load MIME::Base64 until it is explicitly needed.
--rjray
In reply to Re: Re: Module dependencies
by rjray
in thread Module dependencies
by Stegalex
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |