But will that not mess up any updates you (later) need to make to the system Perl?Or worse, the system Perl will start using the local perl modules which may be incompatible between the versions of local and system Perl?
CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics
| [reply] |
But will that not mess up any updates you (later) need to make to the system Perl?
Or worse, the system Perl will start using the local perl modules which may be incompatible between the versions of local and system Perl?
Thats a good question :)
I don't think you can mess up the system perl
any installs would be done as root and root ought to have a different %ENV :)
but if root doesn't, then the system installs just go in a different directory
now that might cause something tricky to happen, but if you're using system tools to update the system perl, then those tools should remove PERL_ vars from the equation
But yeah, the possibility exists, maybe :D
However , the system perl shouldn't start using incompatible versions, as using INSTALL_BASE ought to include both version number and archname -- it doesn't do this on win32 (for some unknown reason), but it should do it on other operating systems
| [reply] |