Re: How to suss out module dependencies...

According to "C. Chad Wallace" <[email protected]> on Thu, 05/27/10 at 16:41:
> 
> 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.

Sounds like an early 20th century internal combustion vehicle...  :-)

I never heard of the "autobundle command" until now, but it does not
sound like it would address all those other modules such as those I
contributed and those that "come with" Perl installed on system A.

Nor have I heard of Devel::NYTProf (or any other Perl profilers) but
when I skimmed through the Devel::NYTProf POD on CPAN just now, it
looks like Devel::NYTProf is more interested in performance and the
time it takes for statements and/or subroutines to execute.  This is
not quite what I was looking for.

Thanks for the great suggestions.

Regards,

web...

--
William Bulley                     Email: [email protected]

72 characters width template ----------------------------------------->|