Re: Windows support

["Han-Wen Nienhuys" <hanwenn@gmail.com>]

2007/7/25, Johannes Schindelin <Johannes.Schindelin@gmx.de>:
> Hi,
>
> [Funny, you quoted me, but culled _me_ from the Cc: list]

It's because gmane does not do SMTP

> > If you supply me with a shell script that will x-compile bash, I'll
> > hapily code the python spec. IMO the real problem is that bash is a unix
> > shell (tied to unix internals) and therefore, compiling it for something
> > as horrid as windows is far from trivial.
>
> Will do.
>
> Did you succeed in adding perl?

God forbid no. Perl is enormous, and I shudder at the thought of
making all those modules compile, or even worse, writing actual perl
code.

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

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