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:08:44 -0800 [thread overview]
Message-ID: <xmqqh8smwspv.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171219164532.GA6745@sigill.intra.peff.net> (Jeff King's message of "Tue, 19 Dec 2017 11:45:32 -0500")
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.
next prev parent reply other threads:[~2017-12-19 17:08 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 [this message]
2017-12-19 17:12 ` Jeff King
2017-12-19 17:47 ` 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=xmqqh8smwspv.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.
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.