Note that “tarballs” can be expected to work across machines only if the surrounding environment ... installed libraries and library-versions ... are known to be identical across the machines. Many CPAN modules install themselves by compiling C programs, checking installed library versions, and other magickal things. Then, they run a slew of self-tests to make certain everything works. Everything should be copacetic if, say, the machines are known to be “corporate clones” of one another.
What most-certainly won’t work is a migration from AIX to (Red Hat or otherwise) Linux. Apples and oranges. The binary modules upon which many Perl libraries actually depend will not load or run correctly. You must repeat the install on one Red Hat machine ... letting CPAN discover and compile and link and otherwise do whatever it takes to accommodate Linux. Then, perhaps, you can tarball-clone that. When the dust finally settles, the Perl programs should then run more-or-less identically.
| [reply] |
| [reply] |
Thanks! Can I use the perllocal.mod on machine1 to clone the installed modules on machine2? If yes, how, are there any scripts that parse the content and make the installation?
| [reply]
[d/l] |
