From: Tor Arntsen <tor@spacetec.no>
Date: Fri, 21 May 2010 15:26:34 GMT
Subject: Re: [PATCH] perl shebangs: Use /usr/bin/env, not /usr/bin/perl
Message-ID: <AANLkTikGS4vjsjTj_hIClT_KEWhH1zaacyKhBM70Qgb6@mail.gmail.com>
In-Reply-To: <A612847CFE53224C91B23E3A5B48BAC74483234EEB@xmail3.se.axis.com>

On Fri, May 21, 2010 at 17:15, Peter Kjellerstedt
<peter.kjellerstedt@axis.com> wrote:
> This does not work. You cannot give arguments to an application
> started via /usr/bin/env; it will interprete everything after
> /usr/bin/env as the application name and fail with:
>
> /usr/bin/env: perl -w: No such file or directory

Yep. It would have to be changed to
/usr/bin/env perl
and add
BEGIN {$^W = 1;}
to the script.

That been said, I've used /usr/bin/env perl for customer applications
for years and years, without problems.  Things wouldn't have worked
otherwise, because on e.g. IRIX systems the /usr/bin/perl version
would be 5.005 and the /usr/freeware version would be 5.6.1.BUt the
caveat is that you'll need to change -w to the above.

-Tor