All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jurko Gospodnetić" <jurko.gospodnetic@docte.hr>
To: git@vger.kernel.org
Subject: Re: git-gui not working in a non-default Cygwin installation.
Date: Sun, 17 Feb 2008 12:25:50 +0100	[thread overview]
Message-ID: <fp95jr$r08$1@ger.gmane.org> (raw)
In-Reply-To: <20080217080255.GQ24004@spearce.org>

   Hi Shawn.

> First, let me point out that Cygwin's Tcl/Tk is stuck on 8.4.1 and
> will probably never get updated again.  I have had some bugs with
> git-gui on 8.4.1 on Windows where git-fetch/git-push processes
> get hung and don't function correctly.  Upgrading Tcl/Tk to the
> native Windows binaries of version 8.4.15 resolves the problem,
> but that binary cannot handle Cygwin paths and Cygwin mount points.

   Sorry, I seem to be a bit confused about this... Why does cygwin not 
support Tcl/Tk above version 8.4.1?

   What about the information found on 
http://opencircuitdesign.com/cygwin under 'Tcl-Cygwin binary 
distribution download and install:'? It lists some additional downloads 
that may be used to install the latest Tcl/Tk on cygwin... Why is this 
not included in the regular Cygwin distribution (setup.exe)?


> git-gui assumes its going to be running on a newer (and more stable)
> Tcl/Tk so its build process embeds the Windows path into the script.
> *sigh*

   But new version of Tcl/Tk or not, this will not work unless you 
actually *build* git-gui on your final target system. Why does this 
information need to be hardcoded in the script at all? Can it not be 
detected at run-time?


> I'll try to work up a Makefile patch in the next few days and get
> it into a gitgui-0.9.3 maint release, which will probably roll up
> into git 1.5.4.3.

   Thanks!

   Best regards,
     Jurko Gospodnetić

  reply	other threads:[~2008-02-17 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16  1:48 git-gui not working in a non-default Cygwin installation Jurko Gospodnetić
2008-02-17  8:02 ` Shawn O. Pearce
2008-02-17 11:25   ` Jurko Gospodnetić [this message]
2008-02-17 13:39     ` Brian Dessent
2008-02-22  6:46   ` Shawn O. Pearce

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='fp95jr$r08$1@ger.gmane.org' \
    --to=jurko.gospodnetic@docte.hr \
    --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.