git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Subject: Re: GIT on MinGW problem
Date: Sat, 26 May 2007 16:41:22 -0300	[thread overview]
Message-ID: <f3a2ke$9s7$1@sea.gmane.org> (raw)
In-Reply-To: <4656A304.AF39A0B6@eudaptics.com>

Johannes Sixt escreveu:
>>
>> http://lilypond.org/git/binaries/mingw/git-1.5.1-2.mingw.exe
>>
>> it should also set $PATH.
> 
> I gave this some more testing and it turns out to be a well working
> toolset. Thank you very much!
> 
> There were still some issues remaining. These are the ones that should
> be fixable easily:
> 
> * git version reports just:
> 
> 	git version -dirty
> 
> Since git-gui parses the output of git version, but does not expect it
> to be of this format, and fails with an error message that it cannot
> parse the version.

My biggest problem is that the makefiles of git are an unmitigated
disaster, and there seems to be little interest in solving this
problem. For example, my suggestion to introduce autoconf was met with
derision.  Most of the effort was patching out makefile parts that
made my life harder. I may have patched the version part out as well.

In this, part of the pain is that Git tries to guess the version number
by itself in a complicated way.  It would be easiest if I could just 
specify the version number externally. In that case I can sync the installer
version number (1.5.1-2 in this case) and the version that git reports.


> * git without an correct git subcommand should list 20 or so commands,
> but it doesn't. The list is just empty.


there was a problem in generate cmd list,  (I have sort in /bin/ ). I
recommend to add

  set -u -v   

to all shell scripts so this doesn't go unnoticed.

> * I personally think that the files should go into
> 
> 	$PROGRAMFILES/Git/{bin,share,lib}
> instead of
> 	$PROGRAMFILES/Git/usr/{bin,share,lib}
> 
> The more difficult to solve problems are:

I understand, but it makes my life a lot more difficult.

> * git-gui and gitk don't work out of the box because they have the path
> to wish hardcoded. They can't be started from CMD at all. I have written
> wrappers gitk.cmd and git-gui.cmd with these 2 lines:
> 
> @echo off
> start wish84 D:/MSYS/1.0/git/bin/gitk %*
> 
> But as you can see, the path is still hard-coded (but it is good enough
> for me for the moment).

The only solution is to x-compile wish and include it as well.  I need several 
strong drinks to start trying this.  Is there a MinGW wish port?

> * perl scripts like git-remote contain a hard-coded path to the
> installation directory and don't work for this reason.

I actually commented out most perl stuff because the Makefile is just
too spaghetti-ish. I seem to have forgotten commenting out git-remote.

I thought the policy was to abandon Perl scripts for git commands?

-- 
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

  parent reply	other threads:[~2007-05-26 19:43 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12  1:13 GIT on MinGW problem Aaron Gray
2007-05-12  1:17 ` Junio C Hamano
2007-05-12  2:25   ` Aaron Gray
2007-05-12  3:30 ` Han-Wen Nienhuys
2007-05-25  8:49   ` Johannes Sixt
2007-05-25  9:45     ` Marco Costalba
2007-05-25 10:20     ` Johannes Schindelin
2007-05-25 11:07       ` Johannes Sixt
2007-05-26 19:42       ` Han-Wen Nienhuys
2007-05-26 22:17         ` Johannes Schindelin
2007-05-27  6:56           ` Han-Wen Nienhuys
2007-05-27 10:52             ` Johannes Schindelin
2007-05-27 17:04               ` Han-Wen Nienhuys
2007-05-28 16:54                 ` Nix
2007-05-27 20:44           ` Han-Wen Nienhuys
     [not found]             ` <Pine.LNX.4.64.0705272213350.4648@racer.site>
     [not found]               ` <f329bf540705271417k1874c1f2u3acc98dc25e058b9@mail.gmail.com>
2007-05-27 21:26                 ` Johannes Schindelin
2007-05-25 21:37     ` Aaron Gray
2007-05-26 19:41     ` Han-Wen Nienhuys [this message]
2007-05-26 22:26       ` Johannes Schindelin
2007-05-26 22:39         ` Junio C Hamano
2007-05-26 22:45           ` Johannes Schindelin
2007-05-26 22:53         ` Han-Wen Nienhuys
2007-05-26 23:47           ` Jakub Narebski
2007-05-27  6:30             ` Han-Wen Nienhuys
2007-05-27  6:39               ` Shawn O. Pearce
2007-05-27  7:02                 ` Han-Wen Nienhuys
2007-05-27  7:21                   ` Steven Grimm
2007-05-27  9:09                     ` Jakub Narebski
2007-05-27 23:18                       ` Han-Wen Nienhuys
2007-05-28  0:04                         ` Johannes Schindelin
2007-05-28  0:31                           ` Han-Wen Nienhuys
2007-05-27 10:46               ` Johannes Schindelin
2007-05-27 18:50       ` Han-Wen Nienhuys
2007-05-27 19:52         ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-27 20:39           ` Aaron Gray
2007-05-27 21:19             ` Han-Wen Nienhuys
2007-05-27 21:24               ` Aaron Gray
2007-05-27 21:39                 ` Aaron Gray
2007-05-27 21:55                   ` Han-Wen Nienhuys
2007-05-27 22:22                     ` Aaron Gray
2007-05-27 22:28                       ` Han-Wen Nienhuys
2007-05-27 22:56                         ` GIT on MinGW - No symbolic links support Aaron Gray
2007-05-27 23:56                           ` Johannes Schindelin
2007-05-29  7:11                             ` Johannes Sixt
2007-05-27 22:22                   ` GIT on MinGW, with tcltk for gitk Han-Wen Nienhuys
2007-05-29 10:54       ` GIT on MinGW problem Johannes Sixt
2007-05-29 11:45         ` Marius Storm-Olsen
2007-05-29 12:10           ` Johannes Sixt
2007-05-29 14:29             ` Han-Wen Nienhuys
2007-05-29 14:49               ` Johannes Sixt
2007-05-29 12:11           ` Johannes Schindelin
2007-05-29 13:05             ` Marius Storm-Olsen
2007-05-29 13:24               ` Johannes Sixt
2007-05-29 14:36                 ` Marius Storm-Olsen
2007-05-29 13:47               ` Johannes Schindelin
2007-05-29 14:13                 ` Johannes Sixt
2007-05-29 15:28                   ` Nguyen Thai Ngoc Duy
2007-05-29 15:47                     ` Johannes Sixt
2007-05-29 18:45                       ` Nguyen Thai Ngoc Duy
2007-05-30  3:03                         ` [PATCH] Make git-k an alias to gitk Johannes Schindelin
2007-05-30  7:06                           ` Johannes Sixt
2007-05-30  2:16                       ` GIT on MinGW problem Han-Wen Nienhuys
2007-05-30  2:39                         ` Johannes Schindelin
2007-05-30  2:57                           ` Shawn O. Pearce
2007-05-30  3:25                             ` [PATCH] Git wrapper: add --redirect-stderr option Johannes Schindelin
2007-05-30  3:38                               ` Shawn O. Pearce
2007-05-30  3:45                                 ` Johannes Schindelin
2007-05-30  3:53                                   ` Shawn O. Pearce
2007-05-30  4:12                                     ` Johannes Schindelin
  -- strict thread matches above, loose matches on Subject: below --
2007-05-12 14:20 GIT on MinGW problem Aaron Gray
     [not found] ` <033501c79710$a2eb0290$0200a8c0@AMD2500>
2007-05-15 19:51   ` Han-Wen Nienhuys
2007-05-16  8:02     ` Johannes Sixt
2007-05-21 18:22       ` Nguyen Thai Ngoc Duy
2007-05-26 23:08         ` Han-Wen Nienhuys

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='f3a2ke$9s7$1@sea.gmane.org' \
    --to=hanwen@xs4all.nl \
    --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 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).