Re: How to suss out module dependencies...

We dealt with a similar problem, moving from comfortable old server to a 
shiny new one.  Perlmonks had some interesting advice:

	http://perlmonks.org/?node_id=203148

which I think is pretty cool (even though I only barely understand what 
it's going).

One of our folks ended up, though, using the CPAN::FindDependencies 
module and writing some stuff that walks up through our use statements 
until it finds something that's not ours, then asks CPAN.  You mention 
you're not using the normal CPAN model, but FindDependencies acutally 
goes back to a cpan site to get its answers, so maybe that's OK.

Maybe this is helpful,

dave

William Bulley wrote:
> I have a question for which I have not been able to find a good answer.
> 
> 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.
> 
> This is something that CPAN does when I install a new module that has
> dependencies on other modules.  BUT in my case I am NOT using the blib,
> lib, t, MANIFEST, etc., etc., distribution model of CPAN, so I cannot
> use those tools - including several others on CPAN that compliment or
> implement this functionality.
> 
> So my question is: is there a way to ask the Perl compiler/interpreter
> to spit out all the modules (and the other dependent modules) in my
> application in some format (a structured tree, a linear text file, etc.)?
> 
> Failing that, are there some external tools that can accomplish this
> given my "main" module as a starting point?  Thank you in advance.
> 
> Regards,
> 
> web...
> 
> --
> William Bulley                     Email: [email protected]
> 
> 72 characters width template ----------------------------------------->|