This shouldn't be a problem. I am regularly working on machines that have more than one perl, and frequently where I don't have root. Which perl binary you get is dependent on the order of directories in $ENV{PATH}, so if you want the new perl, make sure it goes in PATH first.
The suplementary libraries that are part of perl are specific to your perl binary. If your perl is in /home/foo/perl5/bin, these will be in /home/foo/perl5/lib/... Note that these are set up at perl's build time and saved in Config.pm (usable by scripts that need to check that sort of thing). All installed modules are specific to the perl you are using. The other perl will have a different directory tree with a different set of modules. The same is true of extensions (XS modules); they live under the perl lib directory in an architecture specific directory.When it comes to libraries for external code, these are searched for in $ENV{LD_LIBRARY_PATH}, which won't change if you switch which perl executable you are using.
Hope this helps
--
Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)
In reply to Re: Two versions of perl in same machine
by rinceWind
in thread Two versions of perl in same machine
by kprasanna_79
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |