Different perl versions as loadable kernel modules


Do you know where your variables are?
	PerlMonks

Different perl versions as loadable kernel modules

by Amblikai (Scribe)

on Dec 11, 2014 at 17:00 UTC ( [id://1110068]=perlquestion: print w/replies, xml )

Need Help??

Amblikai has asked for the wisdom of the Perl Monks concerning the following question:

Hi Monks! So i have an issue which i'm sure has been encountered many many times before.

Basically we run RHEL5 on our systems and it ships with Perl 5.8.8. Obviously, i want to use 5.20.1. This presents a problem. I can install locally (and i have) but obviously if other people are to use scripts that we develop and roll out then we can't just have everyone installing perl locally.

Our Sys admins, refuse to upgrade as then they'd have to maintain it etc.

We do however use the "module" system for most of our tools. So, my question is, what's the usual way this is dealt with and what's involved in having various perl versions available as kernel modules, if it's even possible?

Cheers!

Comment on Different perl versions as loadable kernel modules

Replies are listed 'Best First'.

Re: Different perl versions as loadable kernel modules
by fishmonger (Chaplain) on Dec 11, 2014 at 17:35 UTC

The solution I use is to install perlbrew in a location (such as under /usr/local/) where all users can access the newer version(s) without disturbing the system perl.

to install perlbrew in a system wide location, you first need to set the PERLBREW_ROOT environment variable to point to the root path. The perlbrew docs give the examples.

http://perlbrew.pl/

https://metacpan.org/pod/App::perlbrew#INSTALLATION

[reply]

Back to Seekers of Perl Wisdom