Re: Git 2.18: RUNTIME_PREFIX... is it working?

From: Paul Smith <paul@mad-scientist.net>
Date: Jul 8, 2018, 18:52 UTC
Message-ID: <bf0d4f33701ec694917f2e710c3fb097085c8d69.camel@mad-scientist.net>
In-Reply-To: <CAD1RUU-4a_jV_JjozjXOR4bi+_7rFW_AjmHbbrw6NHJ77=oGkw@mail.gmail.com>

On Fri, 2018-07-06 at 09:18 -0400, Daniel Jacques wrote:

Show 6 quoted lines

> I forewent autoconf because I was concerned that the option was too
> obscure and the configuration too nuanced to be worth adding via
> flag, as RUNTIME_PREFIX requires some degree of path alignment and is
> fairly special-case. If you prefer autoconf, though, it sounds like a
> good thing to add, and I'm happy that you are finding the feature
> useful!

Well, far from obscure, I actually think that RUNTIME_PREFIX should be the default behavior on all platforms. In fact speaking for myself, I see no value at all in the hardcoded path behavior and it could be removed and RUNTIME_PREFIX be the only option and that would be fine with me.

The only possible advantage I can see to the current default that you can copy the Git binary alone somewhere else, but that's of very little value IMO: you could instead create a symbolic link or a two-line shell script wrapper if you wanted to have "git" available outside of its normal relation to the rest of the installation for some reason.

Thanks for making this work in any event, Daniel!