Specifying multiple perl interpreters for a script

[Yash]

In our perl scripts, we give the path to the perl interpreter on the
first line of the script as :
#!/usr/bin/perl

But our customers sometimes have perl installed in some other place
such as /opt/perl/bin/perl or /usr/local/bin/perl

Is there a way to specify all such possible paths and make sure the
one that exists gets used?

This is so that no change needs to be done at the customer's end.

Thanks

 

[mr.happy]

But our customers sometimes have perl installed in some other place such
as /opt/perl/bin/perl or /usr/local/bin/perl

Is there a way to specify all such possible paths and make sure the one
that exists gets used?

'env' can be used for this:

env(1) is often used with the #!-mechanism to start an interpreter, which
then only needs to be somewhere in your PATH, e.g. "#!/usr/bin/env perl".

However, env(1) is not /usr/bin/env but /bin/env on OpenServer 5 and on a
very few Linux older distributions. Free-, Net- and OpenBSD in turn only
come with /usr/bin/env. So the env-mechanism is increasing convenience,
but not really assuring portability.

http://www.in-ulm.de/~mascheck/various/shebang/

greets,
-- dirk
You will be run over by a beer truck.

 

[svenne]

#!/usr/bin/perl

remove the path in the shebang line and add the path to your PATH env var.
/G

 

[Peter Scott]

In our perl scripts, we give the path to the perl interpreter on the
first line of the script as :
#!/usr/bin/perl

But our customers sometimes have perl installed in some other place
such as /opt/perl/bin/perl or /usr/local/bin/perl

Is there a way to specify all such possible paths and make sure the
one that exists gets used?

If you subscribe to The Perl Journal, you'll find an article in
the April 2003 issue (http://www.tpj.com/archives/0304/) covering
exactly that. The mother of all shebang lines, you might say.