The reason for all the machines to see perl as installed in the same location is so that you can update Config.pm. (I realise that case is unimportant on Windows, but I like to use the Unix case since it works everywhere.)
If the values in Config.pm are incorrect, then diagnostics won't work, and I'd imagine there may be other modules that may not work, although I haven't yet hit upon them (because I use diagnostics, I already have Config.pm fixed everywhere, so I wouldn't see further problems).
Just scan through your Config.pm (the one in your lib directory) for where you have perl already installed, and change those instances of the directory to the new directory, and you're all set.
In reply to Re^3: using perl installed in another computer
by Tanktalus
in thread using perl installed in another computer
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |