From: Johannes Sixt <j6t@kdbg.org>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git@vger.kernel.org, gitster@pobox.com,
Steffen Prohaska <prohaska@zib.de>
Subject: Re: [PATCH 0/2] RUNTIME_PREFIX enhancements
Date: Wed, 18 Feb 2009 20:38:42 +0100 [thread overview]
Message-ID: <499C63C2.3050405@kdbg.org> (raw)
In-Reply-To: <cover.1234969572u.git.johannes.schindelin@gmx.de>
Johannes Schindelin schrieb:
> When I ran "make" in msysGit's /git/, I was greeted by a pretty unfriendly
> message about a RUNTIME_PREFIX that could not be determined.
;)
I have a patch in my private tree that removes the warning.
Actually I wouldn't mind the warning because it is only visible for
developers. Unfortunately, it is poison for gitk (you know, Tcl/Tk
treats any output on stderr as program failure...)
> The real meat comes in patch 2/2:
>
> The problem is that Windows will look in the current directory before
> looking in the PATH when it tries to execute a program. So it will find
> the executable C:\msysgit\git\git.exe and be unable to strip the suffices
> "libexec/git-core" or "bin".
>
> I just added "git" (which should not hurt other users, but instead help
> them if they did not install Git but run it in-place).
This only silences the warning, but there is no guarantee that the
resulting git suite works because your msysgit developer may not have
installed stuff in C:\msysgit\libexec\git-core, yet. What the patch does
is exactly the same as if the compiled-in prefix that the warning
mentions were used, which in the msysgit case on your machine happens to
be C:\msysgit. Or am I missing something?
I think that the better solution is to remove the warning instead of
introducing this special case suffix "git".
-- Hannes
next prev parent reply other threads:[~2009-02-18 19:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 15:10 [PATCH 0/2] RUNTIME_PREFIX enhancements Johannes Schindelin
2009-02-18 15:11 ` [PATCH 1/2] Introduce the function strip_path_suffix() Johannes Schindelin
2009-02-18 19:39 ` Johannes Sixt
2009-02-18 21:13 ` Johannes Schindelin
2009-02-18 22:27 ` Johannes Sixt
2009-02-18 23:18 ` Johannes Schindelin
2009-02-19 19:10 ` [PATCH v2 0/2] RUNTIME_PREFIX enhancements Johannes Schindelin
2009-02-19 19:10 ` [PATCH v2 1/2] Introduce the function strip_path_suffix() Johannes Schindelin
2009-02-19 20:12 ` Johannes Schindelin
2009-02-19 20:26 ` Johannes Sixt
2009-02-19 20:44 ` Johannes Schindelin
2009-02-19 19:10 ` [PATCH v2 2/2] system_path(): simplify using strip_path_suffix(), and add suffix "git" Johannes Schindelin
2009-02-19 20:39 ` Johannes Sixt
2009-02-19 20:48 ` Johannes Schindelin
2009-02-20 8:35 ` Junio C Hamano
2009-02-18 15:11 ` [PATCH " Johannes Schindelin
2009-02-18 19:38 ` Johannes Sixt [this message]
2009-02-18 21:11 ` [PATCH 0/2] RUNTIME_PREFIX enhancements Johannes Schindelin
2009-02-18 22:52 ` Johannes Sixt
2009-02-18 23:19 ` Johannes Schindelin
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=499C63C2.3050405@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=prohaska@zib.de \
/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.