From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Jakub Zaverka <jakub.zaverka@deutsche-boerse.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: difftool uses hardcoded perl shebang
Date: Tue, 19 Dec 2017 09:47:06 -0800 [thread overview]
Message-ID: <xmqqd13awqxx.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171219171253.GA7526@sigill.intra.peff.net> (Jeff King's message of "Tue, 19 Dec 2017 12:12:53 -0500")
Jeff King <peff@peff.net> writes:
> On Tue, Dec 19, 2017 at 09:08:44AM -0800, Junio C Hamano wrote:
>
>> Jeff King <peff@peff.net> writes:
>>
>> > In the meantime, pointing to the actual build-time perl is a workaround
>> > (but obviously not if it's being done by a third-party packager who has
>> > no idea where your perl is).
>>
>> Is such a binary packaging scheme actually in use that deliberately
>> leaves it up to the end user where/if a perl is installed and if it
>> is an appropriately recent version? It sounds rather irresponsible
>> to me.
>
> No, I mean that the user can do:
>
> make PERL_PATH=/path/to/perl/in/my/PATH
>
> but if they are not building Git themselves, that is not an option for
> them. And a binary packager cannot help them there, because they do not
> know that path.
I think we are saying the same thing. A third-party binary packager
cannot guess where your custom Perl is nor if it is recent enough.
I just was wondering if such an irresponsible packaging scheme is in
use that lets you install Git without somehow making sure that the
box also has a version of Perl that can be used with the version of
Git. Then the presence of /path/to/perl/in/my/PATH does not matter,
as it does not have to be used with Git.
prev parent reply other threads:[~2017-12-19 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 13:28 difftool uses hardcoded perl shebang Jakub Zaverka
2017-12-19 16:12 ` Junio C Hamano
2017-12-19 16:16 ` Jakub Zaverka
2017-12-19 16:25 ` Jeff King
2017-12-19 16:33 ` Junio C Hamano
2017-12-19 16:45 ` Jeff King
2017-12-19 17:08 ` Junio C Hamano
2017-12-19 17:12 ` Jeff King
2017-12-19 17:47 ` Junio C Hamano [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqd13awqxx.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jakub.zaverka@deutsche-boerse.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).