From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Michal Rokos <michal.rokos@nextsoft.cz>
Cc: Junio C Hamano <junkio@cox.net>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>,
Alex Riesen <raa.lkml@gmail.com>,
git@vger.kernel.org
Subject: Re: [Patch] Using 'perl' in *.sh
Date: 09 Jul 2006 07:02:13 -0700 [thread overview]
Message-ID: <86ejwuuba2.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <200607091441.16161.michal.rokos@nextsoft.cz>
>>>>> "Michal" == Michal Rokos <michal.rokos@nextsoft.cz> writes:
Michal> I have no problem with that. I can set $PATH.
Michal> But then I'd suggest to change magic #!
Michal> from #!/usr/bin/perl
Michal> to #!/usr/bin/env perl
Michal> for *.perl
Michal> It that what you meant?
No, don't do that. Use the path to Perl that they chose during
configuration because
(a) it might not be the first one in PATH
(b) even if it's the first one in *my* path, it might not be the
first one in *everyone's* path
(c) env requires an *extra* fork/exec
(d) some systems don't have env
The env hack is a nice hack, but it's just a hack. Don't
rely on it when the right thing is nearby.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2006-07-09 14:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-08 15:32 [Patch] Using 'perl' in *.sh Michal Rokos
2006-07-08 18:27 ` Junio C Hamano
2006-07-09 9:46 ` Alex Riesen
2006-07-09 9:51 ` Jan-Benedict Glaw
2006-07-09 10:14 ` Junio C Hamano
2006-07-09 12:41 ` Michal Rokos
2006-07-09 14:02 ` Randal L. Schwartz [this message]
2006-07-09 16:24 ` Jan-Benedict Glaw
2006-07-09 20:33 ` Junio C Hamano
2006-07-09 21:20 ` Jan-Benedict Glaw
2006-07-10 5:41 ` Michal Rokos
2006-07-10 13:09 ` Randal L. Schwartz
2006-07-10 13:16 ` Johannes Schindelin
2006-07-10 13:29 ` Randal L. Schwartz
2006-07-09 10:09 ` Yakov Lerner
2006-07-09 12:17 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ejwuuba2.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=jbglaw@lug-owl.de \
--cc=junkio@cox.net \
--cc=michal.rokos@nextsoft.cz \
--cc=raa.lkml@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).