At all times, I maintain a
Module::Build's OO interface to produce a report of required modules. This can be used in any situation where I need to rebuild/upgrade/recover in a hurry.
For example:
#!/usr/bin/perl
use common::sense;
use Module::Build;
use Sys::Hostname qw/hostname/;
my $build = Module::Build->new
(
module_name => 'DLS',
license => 'perl',
requires => {
'perl' => '5.8.0',
'CGI' => '3.11',
'ACME::EyeDrops' => '1.23',
},
dist_version => 0.1,
);
print "CPAN Dependencies for ".hostname()."\n";
print "=============================================\n";
print $build->prereq_report;
Then on my target machine:
snoopy@snoopy-laptop:~$ perl cpan_deps.pl 2>/dev/null
Checking prerequisites...
CPAN Dependencies for snoopy-laptop
=====================================
requires:
Module Need Have
-----------------+---------+----------
! ACME::EyeDrops 1.23 <none>
CGI 3.11 3.42
perl 5.8.0 5.10.0
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.