Re: git 2.9.2: is RUNTIME_PREFIX supposed to work?
- From
Paul Smith <paul@mad-scientist.net>
- Date
- Sep 27, 2016, 13:18 UTC
- Message-ID
- <1474982294.3190.32.camel@mad-scientist.net>
- In-Reply-To
- <CAPc5daU_nnHRjtC02bxqRaoU+0Rgi7pS6e912Fqk-Xy=qdKWFA@mail.gmail.com>
On Mon, 2016-09-26 at 14:57 -0700, Junio C Hamano wrote:
Show 7 quoted lines
> On Mon, Sep 26, 2016 at 2:32 PM, Paul Smith <paul@mad-scientist.net> wrote: > > > > Hi all. I'm trying to create a relocatable installation of Git 2.9.2, > > so I can copy it anywhere and it continues to run without any problem. > > This is on GNU/Linux systems, FWIW. > > I had an impression that the setting was only to support MS Windows.
Hm. You may be right. If so that's too bad, because a relocatable Git is very handy even on UNIX systems. Is there a reason for invoking the subcommands by providing the plain command ("fetch", "merge-base") as argv[0], rather than giving the fully-qualified path to a Git command?