All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Macario, Gianpaolo" <Gianpaolo_Macario@mentor.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Installing git binaries on a non-default directory (Ubuntu)
Date: Thu, 23 Apr 2015 16:17:18 -0400	[thread overview]
Message-ID: <20150423201718.GB28338@peff.net> (raw)
In-Reply-To: <0CCD6BBA210ECA418BCD82271FCFD94C556A3CEA@EU-MBX-03.mgc.mentorg.com>

On Mon, Apr 13, 2015 at 11:10:51AM +0000, Macario, Gianpaolo wrote:

> Unfortunately it looks to me that the `--prefix=xxx` option provided
> to configure will be hardcoded to the path returned by 'git
> --exec-path', and I do not see how this may actually be made dependent
> on the directory where the binary tarball will be extracted.

Sorry for the late reply, but I just noticed this and happened to be
looking at RUNTIME_PREFIX issues recently.

You're right that no amount of --prefix or other settings can help you
with making binaries that are relocatable after the fact. You do need
something like RUNTIME_PREFIX, but as you found, it does not work very
well on Unix systems.

I do not know if there are other issues, but at least the _first_ issue
that must be dealt with is that git_extract_argv0_path may get a bare
name like "git", without its PATH. So you will have to compute the full
path to the binary in order to find the rest of the files.

There was some minor discussion here:

  http://thread.gmane.org/gmane.comp.version-control.git/267143/focus=267606

(see the notes after the commit message, and the response from
Jonathan).

I hope that helps.

-Peff

      reply	other threads:[~2015-04-23 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 16:34 Installing git binaries on a non-default directory (Ubuntu) Gianpaolo Macario
2015-04-13  6:05 ` Junio C Hamano
2015-04-13 11:10   ` Macario, Gianpaolo
2015-04-23 20:17     ` Jeff King [this message]

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=20150423201718.GB28338@peff.net \
    --to=peff@peff.net \
    --cc=Gianpaolo_Macario@mentor.com \
    --cc=git@vger.kernel.org \
    /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.