Re: difftool uses hardcoded perl shebang

From: Jeff King <peff@peff.net>
Date: Dec 19, 2017, 17:12 UTC
Message-ID: <20171219171253.GA7526@sigill.intra.peff.net>
In-Reply-To: <xmqqh8smwspv.fsf@gitster.mtv.corp.google.com>

On Tue, Dec 19, 2017 at 09:08:44AM -0800, Junio C Hamano wrote:

Show 10 quoted lines

> 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.

-Peff