Re: How to suss out module dependencies...

2010-05-28 Thread Bruce Sears
One difference with what I did is that mine determines if the mod is a core mod and does not list it, if so. I was trying to parse through all of our homegrown packages and see what non-core mods (and versions) they depended on. didn't spend a lot of time making it prettier, so some calls

Re: How to suss out module dependencies...

2010-05-27 Thread C. Chad Wallace
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

Re: How to suss out module dependencies...

2010-05-27 Thread Hendrik Schumacher
A crude solution would be to print the contents of %INC somewhere in your application: perl -e 'use DBI; use Time::Local; print join (\n, keys %INC);' Am Do, 27.05.2010, 22:41, schrieb C. Chad Wallace: At 2:53 PM on 27 May 2010, William Bulley wrote: I have a Perl application that uses many

Re: How to suss out module dependencies...

2010-05-27 Thread William Bulley
According to Hendrik Schumacher h...@activeframe.de on Thu, 05/27/10 at 17:05: A crude solution would be to print the contents of %INC somewhere in your application: perl -e 'use DBI; use Time::Local; print join (\n, keys %INC);' Good suggestion, but won't that list a whole bunch of other

Re: How to suss out module dependencies...

2010-05-27 Thread William Bulley
According to C. Chad Wallace cwall...@lodgingcompany.com 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

Re: How to suss out module dependencies...

2010-05-27 Thread David McMath
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,

Re: How to suss out module dependencies...

2010-05-27 Thread C. Chad Wallace
At 6:09 PM on 27 May 2010, William Bulley wrote: According to Hendrik Schumacher h...@activeframe.de on Thu, 05/27/10 at 17:05: A crude solution would be to print the contents of %INC somewhere in your application: perl -e 'use DBI; use Time::Local; print join (\n, keys %INC);'

Re: How to suss out module dependencies...

2010-05-27 Thread William Bulley
According to David McMath mcd...@stanford.edu on Thu, 05/27/10 at 18:27: 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

Re: How to suss out module dependencies...

2010-05-27 Thread William Bulley
According to Bruce Sears bse...@epgy.stanford.edu on Thu, 05/27/10 at 18:41: One difference with what I did is that mine determines if the mod is a core mod and does not list it, if so. I was trying to parse through all of our homegrown packages and see what non-core mods (and versions)

Re: How to suss out module dependencies...

2010-05-27 Thread William Bulley
According to C. Chad Wallace cwall...@lodgingcompany.com on Thu, 05/27/10 at 18:41: Actually, no. %INC only lists modules that have been loaded into the current instance, via the 'do', 'require', or 'use' operators.[1] Okay, my ignorance of %INC is showing. Thanks. The only extraneous