in reply to Different perl locations on different servers.

The env approach isn't bad. You'll find this to be kind of an ongoing issue though. It may be overkill, but you might look into auto-confiscating your code.
In the end you could deploy your code with something akin to:
./configure --with-perl=/sw/perl/5.6.1/WS/7/bin/perl make make install
This would automatically re-write (substitute) the path string in the files you wanted to. It's an extra layer, but it's precisely why autoconfiscation was invented. To handle the niggling differences between systems.

Autoconfiscating works pretty well across platforms. If you'd need a template for setting it up, let me know. It's a lot easier than it looks initially. (Kind of like perl itself).
--
I used to drive a Heisenbergmobile, but everyone I looked at the speedometer, I got lost.

Replies are listed 'Best First'.
Re^2: Different perl locations on different servers.
by JakeIII (Novice) on Nov 27, 2007 at 13:12 UTC
    Thanks. My code is rarely complex enough to require the configure/make approach. Also, I only have ftp access to one of the servers so I couldn't actually run it. Well, I could, but I'd have to write it in a CGI script and then "run" that web page. Jake