git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Faye-Lund <kusmabite@gmail.com>
To: Michael Weiser <M.Weiser@science-computing.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Extend runtime prefix computation
Date: Tue, 16 Apr 2013 17:18:49 +0200	[thread overview]
Message-ID: <CABPQNSbd_baEe7pstZPSdNQQCAUMBCgV2FGcszy-8zoeuD+M5w@mail.gmail.com> (raw)
In-Reply-To: <20130306081942.GA11151@science-computing.de>

On Wed, Mar 6, 2013 at 9:19 AM, Michael Weiser
<M.Weiser@science-computing.de> wrote:
> Hello Junio,
>
> On Tue, Mar 05, 2013 at 08:13:50AM -0800, Junio C Hamano wrote:
>
>> >> Support determining the binaries' installation path at runtime even if
>> >> called without any path components (i.e. via search path).
>
>> The default for any change is not to include it.  Is there any
>> reason why we want this change?
>
> It makes a binary git installation fully relocatable. Seeing how git
> already has basic support for it I thought other people might be
> interested in this.

I think the motivation for the feature in the first place is Windows,
where the installation path isn't known at build-time. In the
unix-world, this is generally known (/usr/bin or something like that).
What's the reason you want it on other platforms?

  parent reply	other threads:[~2013-04-16 15:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27 16:30 [PATCH] Extend runtime prefix computation Michael Weiser
2012-11-30 10:20 ` Erik Faye-Lund
2012-11-30 10:45   ` Michael Weiser
2013-03-05 11:58 ` Michael Weiser
2013-03-05 16:13   ` Junio C Hamano
2013-03-06  8:19     ` Michael Weiser
2013-04-16 14:56       ` Michael Weiser
2013-04-16 18:23         ` Junio C Hamano
2013-04-16 15:18       ` Erik Faye-Lund [this message]
2013-04-17  6:06         ` Michael Weiser
2013-10-04 13:32           ` Michael Weiser
  -- strict thread matches above, loose matches on Subject: below --
2016-04-15 14:30 Michael Weiser
2016-04-15 16:43 ` Junio C Hamano
2016-04-18  7:20   ` Johannes Schindelin
2016-04-20 17:52   ` Michael Weiser

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=CABPQNSbd_baEe7pstZPSdNQQCAUMBCgV2FGcszy-8zoeuD+M5w@mail.gmail.com \
    --to=kusmabite@gmail.com \
    --cc=M.Weiser@science-computing.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).