Re: [PATCH v7 0/3] RUNTIME_PREFIX relocatable Git

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 26, 2018, 06:01 UTC
Message-ID: <xmqq4ll3e5pb.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20180325205120.17730-1-dnj@google.com>

Dan Jacques <dnj@google.com> writes:

Show 13 quoted lines

> This patch set expands support for the RUNTIME_PREFIX configuration flag,
> currently only used on Windows builds, to include Linux, Darwin, and
> FreeBSD. When Git is built with RUNTIME_PREFIX enabled, it resolves its
> ancillary paths relative to the runtime location of its executable
> rather than hard-coding them at compile-time, allowing a Git
> installation to be deployed to a path other than the one in which it
> was built/installed.
>
> Note that RUNTIME_PREFIX is not currently used outside of Windows.
> This patch set should not have an impact on default Git builds.
>
> This is a minor update based on comments from the v6 series. If all's
> well, I'm hoping this set is good to go.

When testing the non-relocatable (i.e. traditional) Git, we use GIT_EXEC_PATH and bin-wrappers/ trick to ensure that we test the version we just have built, not a random version that happen to be on the $PATH, without requiring the built product first to be installed before being tested. From the diffstat for this patchset, I am guessing that you are using the same mechanism even when testing the relocatable one.

I wonder if the relocatable Git would allow a simpler arrangement to test without installing.

I am asking merely out of curiosity, not suggesting to make a trial install somewhere in the build area and run the built Git normally without GIT_EXEC_PATH trick.

Thanks.