From: Han-Wen Nienhuys Date: Thu, 26 Jul 2007 07:18:45 GMT Subject: Re: Windows support Message-ID: In-Reply-To: <20070726071316.GE18114@spearce.org> 2007/7/26, Shawn O. Pearce : > Han-Wen Nienhuys wrote: > > 2007/7/25, Johannes Schindelin : > > >Did you succeed in adding perl? > > > > >It is not that important, because I plan > > >to make git-gui the main user interface with this installer. But Junio > > >keeps adding Perl scripts (ATM add -i and remote) that I have to convert > > >later... > > > > I don't see what this is good for. > > What git-gui is good for? Its a GUI. For people who perfer to use > mice and push buttons over keys and a command prompt. A large number > of people in this world (many of them on Windows) like these things. > Me, I'm more command line than I am GUI, yet I develop git-gui. > So I find myself using it a lot, just so I can eat my own dogfood. > > Or do you mean Dscho's other point about rewriting tools into C? The last one. The windows installers actually includes a copy of tcl/tk so you can run gitk on windows. . > > I would suggest to making a clear > > decision of what are recommended languages, and move everything else > > to contrib/ .. Currently, C and bash seem the most reasonable choice, > > but you could decide for perl, but then the consequence should be that > > the bash scripts are translated into perl. Having both bash and perl > > serves no purpose, and will lead to duplication of library code to > > interact with the git binary. > > Sure, but there's some stuff that shell is good at, and other stuff > that Perl is good at. Forcing everything into one mold while we > prototype new features is really limiting. I'm not contradicting that, but merely suggesting that they go into contrib/ and are not recommended as standard git commands, and don't need to be packaged for windows. -- Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen