From: Jan Hudec <bulb@ucw.cz>
To: Kees-Jan Dijkzeul <k.j.dijkzeul@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: gitk doesn't start due to cygwin wish not following symlinks?
Date: Fri, 6 Jul 2007 11:33:55 +0200 [thread overview]
Message-ID: <20070706093355.GD3991@efreet.light.src> (raw)
In-Reply-To: <fa0b6e200707031202g4a1248d8na22fbf99b215804@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
On Tue, Jul 03, 2007 at 21:02:35 +0200, Kees-Jan Dijkzeul wrote:
> Hi,
>
> I'm using "stow" to manage several versions of git on my cygwin
> system. As a result, my /usr/local/bin contains a bunch of symlinks to
> the actual binaries in /usr/local/stow/git-1.5.2.2/bin.
>
> This works like a charm, except that gitk won't start up, claiming, in
> turn, that it is unable to start git itself. After some investigation,
> I found that the "wish" that is supplied with cygwin isn't a true
> cygwin one, and hence doesn't understand cygwin style simlinks, and
> thus cannot start the /usr/local/bin/git symlink. It needs the true
> binary.
>
> So for now, I've worked around this by updating the first few lines of
> the gitk script to read:
>
> #!/bin/sh
> # Tcl ignores the next line -*- tcl -*- \
> export PATH=$PATH:/usr/local/stow/git-1.5.2.2/bin
> # Tcl ignores the next line also \
> exec wish "$0" -- "$@"
>
> This works for me, but is admittedly butt-ugly. Any tips on how to
> handle this kind of situation?
Ask cygwin folks to teach their wish their symlinks?
You could also try putting a git.bat somewhere in path, that would set the
path and run true git from /usr/local/stow/git-1.5.2.2/bin.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-07-06 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 19:02 gitk doesn't start due to cygwin wish not following symlinks? Kees-Jan Dijkzeul
2007-07-06 9:33 ` Jan Hudec [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=20070706093355.GD3991@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=k.j.dijkzeul@gmail.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 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.