git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <johannes.sixt@telecom.at>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Windows: set gitexecdir = $(bindir)
Date: Fri, 18 Jul 2008 17:32:33 -0700	[thread overview]
Message-ID: <7vej5q67dq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 1216366485-12201-5-git-send-email-johannes.sixt@telecom.at

Johannes Sixt <johannes.sixt@telecom.at> writes:

> The "dash-less" change aims to remove git commands from $PATH. It does so
> by defining a GIT_EXEC_PATH that is different from $(bindir). On Windows
> we want a relocatable installation of the git tool, so we cannot use an
> absolute GIT_EXEC_PATH.  Therefore, the implementation of
> builtin_exec_path() on Windows derives the exec-path from the command
> invocation,...

Sorry, I am not sure if I understand what you are trying to solve.  If you
have ../libexec/git-core/ in GIT_EXEC_PATH (or have builtin_exec_path()
use it), then your installation would look like this:

	[[some random place]]
        	bin/git
                libexec/git-core/git-add
                libexec/git-core/git-del
                libexec/git-core/git-dir
                ...

and if "git" can figure out it is "[[some random place]]/bin/git",
it can find its subcommands from neighbouring directory, that is still
inside the random place the user told the installer to use, can't it?

> This counteracts the aims of the "dash-less" change on Windows, but better
> this way than having no working git at all.

I'd agree to the extent that anything is better than having no working
git, but this somewhat feels backwards.

  reply	other threads:[~2008-07-19  0:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18  7:34 [PATCH] Windows related patches Johannes Sixt
2008-07-18  7:34 ` [PATCH] Teach lookup_prog not to select directories Johannes Sixt
2008-07-18  7:34   ` [PATCH] builtin-clone: Use is_dir_sep() instead of '/' Johannes Sixt
2008-07-18  7:34     ` [PATCH] Add ANSI control code emulation for the Windows console Johannes Sixt
2008-07-18  7:34       ` [PATCH] Windows: set gitexecdir = $(bindir) Johannes Sixt
2008-07-19  0:32         ` Junio C Hamano [this message]
2008-07-19  8:52           ` Johannes Sixt
2008-07-19 17:10             ` Steffen Prohaska
2008-07-19 17:28             ` Junio C Hamano
2008-07-19 19:31               ` Johannes Sixt
2008-07-19  0:32     ` [PATCH] builtin-clone: Use is_dir_sep() instead of '/' Junio C Hamano
2008-07-19  9:32       ` Johannes Sixt
2008-07-19 11:35         ` Johannes Schindelin
2008-07-19 13:49         ` Johannes Sixt
2008-07-19 17:44           ` Daniel Barkalow
2008-07-21 13:43             ` Kristian Høgsberg

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=7vej5q67dq.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.sixt@telecom.at \
    /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).