in reply to Re: Changing locations of Perl builds on different machines
in thread Changing locations of Perl builds on different machines
I suppose the simplest thing might be to grep for the #! line at the top of each Perl script and change that line to the build on that particular client system. However that does have the potential to cause problems while they upgrade their code base periodically.
I am still curious to see if there is a way of getting the Perl script to look for other Perl builds on the system and use them instead - I suppose a CPAN module might do this?
I have built Perl a number of times before and then later wanted to move it to another directory (ran out of disk space, whatever...), I have found the most effective way of doing it was to delete Perl and reinstall it. Simply moving it screwed up relationships to modules, man pages etc. Perl must keep the information on the $PERL_BIN, $PERL_LIB, $PERL_MOD somewhere, do you know of any environmental options that might be tinkered with to allow for the Perl directory to be moved somewhere else?
Thanks for your help.
MadraghRua
yet another biologist hacking perl....
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re (tilly) 3: Changing locations of Perl builds on different machines
by tilly (Archbishop) on Sep 05, 2001 at 22:41 UTC | |
by MadraghRua (Vicar) on Sep 08, 2001 at 02:49 UTC | |
|
Re: Re: Re: Changing locations of Perl builds on different machines
by tachyon (Chancellor) on Sep 05, 2001 at 00:34 UTC |