I'm working out how to set up a clutch of CentOS 7 servers to run a Perl application, and I realise that I am not understanding (or liking!) what cpan is doing.
System perl comes with @INC set to be
/usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .
So, matched pairs of a "lib64" and a "share". Fine.
I want everybody on the machine to be able to run our perl application with a consistent set of perl modules. And I don't want to skirmish with the vagaries of vendor_perl. So I tried, as root, installing them "locally", with
cpanm -l /usr/local --installdeps MYAPPLICATION
The first thing I noticed was that this installed things in /usr/local/lib/perl5 I couldn't imagine why I ever would want two different sets of perl libraries in /usr/local so I put in a symlink from /usr/local/lib/perl5 -> /usr/local/share/perl5 (But was that a mistake?) And now lots of dependencies get installed in /usr/local/share/perl5, where MYAPPLICATION can find them.
But...
cpanm puts lots of other dependencies not in /usr/local/lib64/perl5, which is on @INC, but in /usr/local/share/perl5/x86_64-linux-thread-multi, which isn't!
What is the right way to fix this?
Should I be trying to steer cpanm to put "local" things in the "expected" places? If so, how?
Should I just symlink /usr/local/lib64/perl5 to /usr/local/share/perl5/x86_64-linux-thread-multi? Or are they meant to be subtly different things?
Or what?
In reply to Misplaced local cpan modules by Robert II
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |