Note that if you have NFS problems, -x "/path/to/perlY" may take a really long time, so doing this check for every invocation of a program that expects to be run by perl may be confusing to users.

How did your second approach fail, and why? I'm not exactly sure what error conditions there are that would make it fail. Maybe you need to add the invoked script name $0 after perlX in the command line, unless the argument is -e? You might need to (re)implement a Perl option parser for that, mostly from perlrun to mirror that.

In reply to Re: wrapper script to conditionally exec different perls? by Corion
in thread wrapper script to conditionally exec different perls? by stackspace

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.