From: Junio C Hamano <junkio@cox.net>
To: Michal Rokos <michal.rokos@nextsoft.cz>
Cc: git@vger.kernel.org
Subject: Re: [Patch] Using 'perl' in *.sh
Date: Sun, 09 Jul 2006 13:33:04 -0700 [thread overview]
Message-ID: <7v4pxqfri7.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200607091441.16161.michal.rokos@nextsoft.cz> (Michal Rokos's message of "Sun, 9 Jul 2006 14:41:15 +0200")
Michal Rokos <michal.rokos@nextsoft.cz> writes:
> Hello,
>
> On Sunday 09 July 2006 12:14, Junio C Hamano wrote:
>> Michal, is there a reason you do not want to have the version of
>> perl you teach git tools via #! lines with PERL_PATH on your $PATH?
>
> I have no problem with that. I can set $PATH.
> But then I'd suggest to change magic #!
> from #!/usr/bin/perl
> to #!/usr/bin/env perl
> for *.perl
>
> It that what you meant?
No, that is not what I meant.
Invocation of perl _in_ scripts can be controlled by user's
PATH, but #! cannot be. As Merlyn says 'env' is a nice hack,
but we configure the scripts we install to have #! pointing at
the right interpreter as a more cleaner (than using 'env', that
is) workaround anyway, so #! pointing at PERL_PATH and scripts
relying on user's $PATH would be the right thing to do.
next prev parent reply other threads:[~2006-07-09 20:33 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
2006-07-09 16:24 ` Jan-Benedict Glaw
2006-07-09 20:33 ` Junio C Hamano [this message]
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=7v4pxqfri7.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=michal.rokos@nextsoft.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.