Re: How to suss out module dependencies...

At 2:53 PM on 27 May 2010, William Bulley wrote:

> I have a Perl application that uses many Perl modules.  Most come from
> CPAN, some I have written, others come with Perl distributions
> (core?).
> 
> I am faced with the need to transport this collection of Perl code
> from operating system A to operating system B, both of which are
> perfectly well supported by Perl.  Over several months I have added
> to system A lots of modules that need other modules.
> 
> Unfortunately, system B is rather devoid of most of the modules that I
> need for this application.  I dread having to make an inclusive list
> of all the modules and all the modules that those modules need, and
> so on, and so on.

The autobundle command of CPAN would give you a bundle file that lists
of all the modules you've installed on system A.  Then you can take
that bundle file over to system B and install it using CPAN.

Your bundle may end up with a lot of extra modules that your program
doesn't need, but you can edit the bundle file and remove them.

Or maybe you could see if you can get a profiler (like Devel::NYTProf)
to tell you which modules are loaded when you load and run your module.


-- 

C. Chad Wallace, B.Sc.
The Lodging Company
http://www.lodgingcompany.com/
OpenPGP Public Key ID: 0x262208A0

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkv+2PMACgkQKeSNHCYiCKBGiwCfU3w9MKM3ORzvOVHwQqbZArML
DBUAnir0AdSJIQcXHZdQ5QZUIFmKrvfD
=zbbt
-----END PGP SIGNATURE-----