http://www.perlmonks.org?node_id=851578


in reply to Module distribution

I was thinking of just rsync'ing the following directories
/usr/opt/perl5/lib/5.8.8
/usr/opt/perl5/lib/site_perl/5.8.8

Sounds like a reasonable plan (if the machines are binary-compatible).  But note that if modules depend on 3rd-party shared libraries (installed in different locations), you'd have to distribute them too...  For the latter case, some packaging/distribution tool might be easier to use.

In case you intend to do larger cpan installations, in particular of modules that might risk destabilizing any system tools that rely on the Perl installation as it ships, you might want to think about setting up a second separate Perl installation for your own use (e.g. in /usr/local/perl/...), into which you then install the CPAN modules (and rsync them...).

Replies are listed 'Best First'.
Re^2: Module distribution
by ikegami (Patriarch) on Jul 27, 2010 at 19:42 UTC

    Sounds like a reasonable plan (if the machines are binary-compatible).

    And the perl binaries were built using the same settings.

Re^2: Module distribution
by syphilis (Archbishop) on Jul 27, 2010 at 23:06 UTC
    But note that if modules depend on 3rd-party shared libraries (installed in different locations), you'd have to distribute them too...

    There's often a good case for building those modules against static libraries - as there's then no additional files to distribute.
    Another problem with shared libraries is that there's a possibility that the shared library being distributed is not the shared library that gets loaded by the perl module - which is something that needs to be considered when troubleshooting. (Obviously, this aspect is also avoided if the module is built against a static library.)

    Cheers,
    Rob