From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: jnareb@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH] gitweb-lib.sh: Set up PATH to use perl from /usr/bin
Date: Tue, 01 May 2012 18:23:37 +0200 [thread overview]
Message-ID: <4FA00E09.2090708@in.waw.pl> (raw)
In-Reply-To: <201205011323.45190.tboegi@web.de>
On 05/01/2012 01:23 PM, Torsten Bögershausen wrote:
> When there are different version of perl installed on the machine,
> the $PATH may point out a different version of perl than /usr/bin.
> One example is to have /opt/local/bin/perl before /usr/bin/perl.
>
> Sanitize the PATH by adding /usr/bin at the beginning
Hm, I see that most scripts have #!/usr/bin/perl, and only two have
#!env perl [1]. So in general we usally rely on using perl in /usr/bin.
But your patch affects other stuff than perl, and unconditionally
changing PATH set by the user is not nice, as it affect programs called
recursively. Wouldn't simply replacing all calls to bare perl in
t/gitweb-lib.sh with invocations of /usr/bin/perl be better?
[1]
% git grep 'env perl\b'
git-relink.perl:#!/usr/bin/env perl
git-svn.perl:#!/usr/bin/env perl
-
Zbyszek
next prev parent reply other threads:[~2012-05-01 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 11:23 [PATCH] gitweb-lib.sh: Set up PATH to use perl from /usr/bin Torsten Bögershausen
2012-05-01 16:23 ` Zbigniew Jędrzejewski-Szmek [this message]
2012-05-01 16:34 ` Jeff King
2012-05-01 16:47 ` Junio C Hamano
2012-05-01 17:03 ` Zbigniew Jędrzejewski-Szmek
2012-05-01 17:08 ` Jeff King
2012-05-01 17:50 ` Torsten Bögershausen
2012-05-01 17:53 ` Junio C Hamano
2012-05-01 17:55 ` [PATCH] t/gitweb-lib: use $PERL_PATH to run gitweb Jeff King
2012-05-01 20:18 ` [PATCH] Consistently use perl from /usr/bin/ for scripts Zbigniew Jędrzejewski-Szmek
2012-05-01 20:54 ` Randal L. Schwartz
2012-05-01 16:44 ` [PATCH] gitweb-lib.sh: Set up PATH to use perl from /usr/bin Junio C Hamano
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=4FA00E09.2090708@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=tboegi@web.de \
/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).