Re: GIT on MinGW problem

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 26, 2007, 22:26 UTC
Message-ID: <Pine.LNX.4.64.0705262318190.4648@racer.site>
In-Reply-To: <f3a2ke$9s7$1@sea.gmane.org>

Hi,

On Sat, 26 May 2007, Han-Wen Nienhuys wrote:

Show 24 quoted lines

> 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.

Well, I would not call it derision. But many people have had bad experience with that big mess which is autoconf, so we were more than reluctant to do it.

In the meantime, we do have a configure.ac, though. In general, you do not have to run it, but you can if "make" does not work out of the box.

I have to admit that it is unclear to me what are the problems with the Makefile with regards to gub. I think I will just bite the apple, and download that beast to try it myself.

> In this, part of the pain is that Git tries to guess the version number
> by itself in a complicated way.

Yes, I never understood that myself why it has to be so complicated. But then, it did not make _my_ life hard, so I did not care.

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

Alas, no. We even have picked up a few since.

OTOH, it _is_ a nice thing to protohype the new commands as shell or perl scripts. When they stabilize enough, convert them to builtins.

There are exactly 4 perl scripts left that I regularly use:

add--interactive, cvsimport, remote and svn.

I somehow have the feeling that it is not worth the effort to convert cvsimport and svn. With add--interactive, I think it's better to leave it as is before Junio goes on another "what have I done? why did I have to add _this_?" spree.

But remote will soon be the center of my crosshairs.

Ciao, Dscho