From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: git@vger.kernel.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: MinGW binary installer available
Date: Wed, 7 Feb 2007 15:55:58 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.63.0702071552470.22628@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <45C9E470.7030609@xs4all.nl>
Hi,
On Wed, 7 Feb 2007, Han-Wen Nienhuys wrote:
> I had a try to see whether I could make GUB
> also produce a MinGW installer for Git.
Great!
> You can download the result at
>
> http://lilypond.org/mingit/mingit-1.4.9993-1.mingw.exe
>
> the odd version number was because I was too lazy to write code
> to extract the version number from the repository automatically.
>
> I don't actually have a windows copy, so it's basically untested.
> However, I did succeed in running rev-list in wine.
I played a little with it. IMHO it makes no sense to use it without a
bash, and without less. For example,
$ git init
$ git add git.exe
$ git status
$ git commit -a -m initial
$ git show HEAD
do not produce any output when issued in cmd.
Also, many scripts rely on bash and/or perl, so you'd have to include
them, too.
> PS. I'd be interested in comments on using GUB from others.
> GUB is a cross-compiling build tool, probably best described
> as a "Poor Man's Conary".
>
> Once I have the boilerplate code committed, building this
> installer should amount to
>
> darcs get http://lilypond.org/vc/gub.darcs/ gub
> cd gub
> make -f Makefile.mingit bootstrap mingw
I'll try that if I get the time.
> (yes, GUB itself is still hosted in Darcs. Shoot me.)
I will.
Ciao,
Dscho
next prev parent reply other threads:[~2007-02-07 14:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 14:38 MinGW binary installer available Han-Wen Nienhuys
2007-02-07 14:55 ` Johannes Schindelin [this message]
2007-02-07 15:05 ` Johannes Schindelin
2007-02-07 15:14 ` Han-Wen Nienhuys
2007-02-08 8:09 ` Johannes Sixt
2007-02-07 15:08 ` Han-Wen Nienhuys
2007-02-07 15:26 ` Johannes Schindelin
2007-02-07 15:34 ` Han-Wen Nienhuys
2007-02-07 16:16 ` Johannes Schindelin
2007-02-07 17:05 ` Han-Wen Nienhuys
2007-02-07 17:10 ` Johannes Schindelin
2007-02-07 17:35 ` Han-Wen Nienhuys
2007-02-07 21:10 ` Han-Wen Nienhuys
2007-02-08 8:12 ` Johannes Sixt
2007-02-08 8:09 ` Johannes Sixt
2007-02-08 10:14 ` Han-Wen Nienhuys
2007-02-08 21:15 ` Robin Rosenberg
2007-02-08 21:18 ` Johannes Schindelin
2007-02-08 21:22 ` Shawn O. Pearce
2007-02-08 21:26 ` Johannes Schindelin
2007-02-07 16:03 ` Han-Wen Nienhuys
2007-02-07 20:18 ` Jan Nieuwenhuizen
2007-02-07 21:21 ` Han-Wen Nienhuys
2007-02-07 23:51 ` Johannes Schindelin
2007-02-07 22:10 ` Han-Wen Nienhuys
2007-02-07 23:52 ` Johannes Schindelin
2007-02-08 19:58 ` Jan Nieuwenhuizen
2007-02-08 20:08 ` Johannes Schindelin
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=Pine.LNX.4.63.0702071552470.22628@wbgn013.biozentrum.uni-wuerzburg.de \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
--cc=janneke@gnu.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.