From: Mark Levedahl <mlevedahl@gmail.com>
To: Paul Mackerras <paulus@samba.org>
Cc: "Shawn O. Pearce" <shawn.o.pearce@bankofamerica.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Allow gitk to start on Cygwin with native Win32 Tcl/Tk
Date: Sat, 20 Oct 2007 14:47:33 -0400 [thread overview]
Message-ID: <471A4D45.1040107@gmail.com> (raw)
In-Reply-To: <18201.59649.800748.780690@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Shawn O. Pearce writes:
>
>
>> Yes, I admit this is an odd patch. I can certainly carry it in
>> my own tree (I already carry some other patches) but I wonder if
>> we shouldn't include it as some users may actually try to do this,
>> just like I did. Latest git-gui `master` already has changes to its
>> Makefile and shell startup boilerplate to handle this weird case.
>>
>
> Why do you need to change gitk itself? If you're going to modify it
> with sed, why can't you change the $0 on the 3rd line to the installed
> path of the gitk script?
>
>
While gitk is most likely installed as /usr/bin/gitk in Cygwin's
filespace, that could resolve to anything in the Windows file system. It
might be c:\cygwin\usr\bin\gitk, but could also be "d:\Documents and
Settings\Bill\Programs\cygwin\usr\bin\gitk" depending upon who installed
it and with what options. Both are seen as /usr/bin/gitk by Cygwin.
Thus, Shawn is correct in using cygpath to resolve the name.
Also, as Cygwin's tcl/tk package is bound to the port of the insight
debugger to Cygwin, and that project is stuck for years on 8.4.1, this
patch (or something like it) may be the only way to allow gitk to access
a more recent version on Cygwin in the foreseeable future. So, I think
this is a good idea.
Mark
prev parent reply other threads:[~2007-10-20 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 5:04 [PATCH] Allow gitk to start on Cygwin with native Win32 Tcl/Tk Shawn O. Pearce
2007-10-20 11:39 ` Paul Mackerras
2007-10-20 18:47 ` Mark Levedahl [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=471A4D45.1040107@gmail.com \
--to=mlevedahl@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paulus@samba.org \
--cc=shawn.o.pearce@bankofamerica.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).