From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Michael Witten <mfwitten@MIT.EDU>
Cc: git@vger.kernel.org
Subject: Re: [PATCH review] Build: make PERL_PATH = /usr/bin/env perl
Date: Sun, 01 Jun 2008 10:22:01 +0200 [thread overview]
Message-ID: <vpqabi5o992.fsf@bauges.imag.fr> (raw)
In-Reply-To: <1212258886-87484-1-git-send-email-mfwitten@mit.edu> (Michael Witten's message of "Sat\, 31 May 2008 14\:34\:46 -0400")
Michael Witten <mfwitten@MIT.EDU> writes:
> [problem with different versions of perl]
There's also the case where perl simply isn't available in /usr/bin,
but is somewhere else.
> It would seem to me that something like '/usr/bin/env perl' is slightly
> more vanilla in the sense that it can handle more cases.
>
> Perhaps the Makefile can be smarter about guessing the right path?
Perhaps something like this?
diff --git a/Makefile b/Makefile
index 865e2bf..5828745 100644
--- a/Makefile
+++ b/Makefile
@@ -323,7 +323,7 @@ ifndef SHELL_PATH
SHELL_PATH = /bin/sh
endif
ifndef PERL_PATH
- PERL_PATH = /usr/bin/perl
+ PERL_PATH = $(shell which perl)
endif
export PERL_PATH
(untested)
This would generate the same files in the common case, but detect
another installation at compile time.
Note that this is indeed different from the original proposal in the
case of a multi-user system: here, the perl installation is chosen
once and for all by the guy who installs git, but can't be overridden
later (e.g by a user having his own custom perl installation in his
$HOME). I don't know which is better.
--
Matthieu
next prev parent reply other threads:[~2008-06-01 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 18:34 [PATCH review] Build: make PERL_PATH = /usr/bin/env perl Michael Witten
2008-05-31 19:55 ` Junio C Hamano
2008-06-01 4:48 ` Michael Witten
2008-06-01 8:22 ` Matthieu Moy [this message]
2008-06-01 9:01 ` Junio C Hamano
2008-06-01 18:11 ` Steven Walter
2008-06-02 2:17 ` David Christensen
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=vpqabi5o992.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=mfwitten@MIT.EDU \
/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