From: Junio C Hamano <gitster@pobox.com>
To: Paul Smith <paul@mad-scientist.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git 2.9.2: is RUNTIME_PREFIX supposed to work?
Date: Tue, 27 Sep 2016 09:15:12 -0700 [thread overview]
Message-ID: <xmqqh991qpyn.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1474982294.3190.32.camel@mad-scientist.net> (Paul Smith's message of "Tue, 27 Sep 2016 09:18:14 -0400")
Paul Smith <paul@mad-scientist.net> writes:
> On Mon, 2016-09-26 at 14:57 -0700, Junio C Hamano wrote:
>> 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?
I do not think of any reason offhand. It just is that we never
needed it.
If you want to add support without making the resulting codebase too
ugly, without breaking the classic way of installing into a fixed
locations, and without breaking the existing support of platforms
that does know the runtime-prefix thing, not just I wouldn't mind
but I would welcome such an addition ;-)
Thanks.
next prev parent reply other threads:[~2016-09-27 16:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 21:32 git 2.9.2: is RUNTIME_PREFIX supposed to work? Paul Smith
2016-09-26 21:57 ` Junio C Hamano
2016-09-27 13:18 ` Paul Smith
2016-09-27 15:34 ` Johannes Schindelin
2016-09-27 16:15 ` Junio C Hamano [this message]
2016-09-27 16:37 ` 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=xmqqh991qpyn.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=paul@mad-scientist.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.