This is an interesting thread:
http://lists.centos.org/pipermail/centos/2014-April/141871.html about the problems you can find building perl modules for CentOS
releases (new or old).
I agree with John R. Pierce: cpan is very very bad tool ( in fact, I
hate it) to build perl modules for CentOS systems, breaks all other
By default rpm looks for the perl modules inside the rpm itself and throws dependency error if it is not found.
For eg., I have a perl script in the rpm that uses Crypt::DES perl module.
I have that perl module in the system (/usr/local/lib64/perl5/Crypt/DES.pm ) and this directory is included in @INC
When I try to install the rpm package:
I was attempting to upgrade my Perl modules through CPAN, but I did not supply a regex/module name to upgrade: perl -MCPAN -e 'upgrade'; I can only assume the worst (which seems to be supported by the output of perldoc perllocal), i.e. all Perl modules from CPAN are installing.
We have RHEL 5.X OS installed here, where we need few Perl modules installed. I have local copy of Perl modules in .tar.gz format. The problem is that we don't have Internet available here and it is really pain to install all the modules manually on all the servers one by one.
So can I copy the modules and reuse in some other servers of Same OS and architecture. Please guide.
Florian Pritz wrote:
Perl 5.20, as any other new perl version, requires all modules that are
not purely perl code to be rebuilt. We did that for all packages in our
The last couple major updates printed an error message when trying to load modules built against the wrong version, 5.20 seems to cause segfaults.
I'm migrating from one server to another and using perl -MCPAN -eautobundle to work out which modules I should be bringing along.
Some modules are a bit problematic at install-time though (mainly due to relying on non-perl libraries etc), and it would be good to be able to see a list of the modules that it wants to install/update, rather than doing a full install of the bundle and looking at larg