Re^5: using perl installed in another computer

As nobull points out, you can simply install to the shared drive directly, and then everything would be updated automatically.

Let's say you decided that everyone would mount all shared utilities on drive "U" (for utility). You could just change all "C:\Perl"s to "U:\Perl" and everything should work fine after that. (As nobull also kind of pointed out, most things would work fine without this change, but debugging why your script doesn't work with use diagnostics on a remote machine is painful - trust me. So I'm trying to ensure you don't have that problem. Other problems, perhaps, but not the same ones I've had ;->). Something like this should work, given that you started with perl on drive C, and follow the above example:

  perl -pi.bak -e 's/C:\\Perl/U:\\Perl/g' Config.pm
[download]

Your favourite editor probably has a search&replace function, too. But when you have perl already, why not take advantage of it ;-)

Comment on Re^5: using perl installed in another computer Download Code

Replies are listed 'Best First'.
Re^6: using perl installed in another computer by Anonymous Monk on Apr 04, 2005 at 21:15 UTC
Hello there! I am implementing your suggestion and noticed that there were a couple of config.pm's in the perl directory. `Eg: C:\Perl\Lib C:\Perl\Lib\CPAN C:\Perl\lib\Encode C:\Perl\lib\Net C:\Perl\site\lib etc...` [download] Which config.pm file would need to be updated? all? Thanks in advance.	[reply] [d/l]
Re^7: using perl installed in another computer by Tanktalus (Canon) on Apr 04, 2005 at 21:32 UTC
I only ever updated the one in perl\lib - the CPAN, Encode, and Net directories have configurations for themselves which should be ok. I don't have one in perl\site\lib - so that may need to be kept in sync with the one in perl\lib, if you need to keep it at all (which I doubt). And please keep the correct capitalisation: it's "Config.pm" not "config.pm" - it's a bad idea to treat these filenames as case insensitive since perl treats the contents case sensitively. It'll just make a mess in one's head to ignore the case. As others have pointed out, "use config" may not end up crashing perl, but it usually won't work as intended either.	[reply]