You can also use a small script to set the perl path explicitly in the files before running on each environment. At least, for testing purposes - I would recommend keeping the production path in the files that are in version control.

For example, here's a quick version that would replace the #!/path/to/perl line at the top of each file with a path that you pass in:

#!/bin/sh PERL=$1 for file in `find . -name '*.pl'` do perl -i -ape 's/^#!\s*(.*perl)\s*(.*)$/#!$ENV{PERL} $2/;' $file done

I have a script similar to this that I use to increment the release version in all the 'configure.in' files in our release packages at work, so I think this might help you out.

---
echo S 1 [ Y V U | perl -ane 'print reverse map { $_ = chr(ord($_)-1) } @F;'


In reply to Re: Different perl locations on different servers. by tuxz0r
in thread Different perl locations on different servers. by JakeIII

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.