git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Dmitry Kakurin <dmitry.kakurin@gmail.com>
Cc: git@vger.kernel.org, Mike Pape <dotzenlabs@gmail.com>,
	Marius Storm-Olsen <marius@trolltech.com>,
	Johannes Sixt <J.Sixt@eudaptics.com>
Subject: Re: Bootstraper for Git Dev Environment for Windows (Light version)
Date: Sun, 5 Aug 2007 14:51:15 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708051444560.14781@racer.site> (raw)
In-Reply-To: <26F4E92272F14115959CFA0C23809617@ntdev.corp.microsoft.com>

Hi,

On Sun, 5 Aug 2007, Dmitry Kakurin wrote:

> ----- Original Message ----- From: "Johannes Schindelin"
> <Johannes.Schindelin@gmx.de>
> 
> 
> > - How about calling your package msysGit-netInstall-<version>.exe?
> No problem. Feel free to reupload it with a different name.

I'll do so later... When it has to change.

> >   mingw.git as well...  Still, on dial-up, 40MB or 60MB makes a 
> > difference, no?
>
> Sorry, I didn't have dialup for years so I don't take it into 
> consideration. Still 60MB is not that dialup unfriendly.

Okay.

> > - There is one big caveat with your bootstrapper: things have been 
> > known to break, and I think msysgit.git is no exception.  So I'd like 
> > to have a fallback in case things go awry, also to have something that 
> > is tested (for example, Mike tested msysGit-0.4.exe before releasing 
> > it).  Of course, we could solve that issue by branching off of the 
> > last release tag.
>
> That, or better yet always maintain master branch in a working 
> condition. Seriously. If it (VERY rarely) breaks we'll just revert the 
> offending checkin to bring it back in shape. Where I come from, 'main' 
> or 'master' should ALWAYS be functional.

Okay, let's try to be anal then.

> > - AFAICT it is possible to make nicer installers with 7-Zip, and also
>
> I have no preference here. I just use what I know (WinRAR). If you feel 
> strongly about 7zip (which I can see you do for some reason :-) feel 
> free to repackage it.

Yeah ;-)  I like it because it is Open Source... and easily scriptable.  
Even if you want to make a graphical installer.

> > - I wanted to hold off a little, until Hannes can apply the fix-up 
> > patch we need in mingw.git.  Because when he does, your bootstrap will 
> > run into problems...
>
> Not sure why...

Neither am I anymore.

What would you say about this idea:

- upload a branch "mingw-devel" to msysgit.git, which is identical to 
  mingw.git's devel, plus our patches.

- convert /git to a submodule, fetching from msysgit.git's mingw-devel 
  branch.

- adjust /etc/profile for the changes.

- make a new net installer and upload it.

- But keep doing some full releases in the meantime, which do not clone 
  anything, but rather initialise /git/.git so that people can send in 
  patches?

> > It would be nice to have insight in how you went about to identify 
> > what is needed?
>
> Well, I've set path to a single directory (C:\GitMe\bin), copies over 
> bash and git-clone and started running it until it worked. Which 
> happened surprisingly fast.

Ah, thanks.  Valuable work, this.

Ciao,
Dscho

  reply	other threads:[~2007-08-05 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05 11:00 Bootstraper for Git Dev Environment for Windows (Light version) Dmitry Kakurin
2007-08-05 12:27 ` Johannes Schindelin
2007-08-05 12:51   ` Dmitry Kakurin
2007-08-05 13:51     ` Johannes Schindelin [this message]
2007-08-16  9:06   ` Johannes Sixt
2007-08-07 20:18 ` Nguyen Thai Ngoc Duy

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.64.0708051444560.14781@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=J.Sixt@eudaptics.com \
    --cc=dmitry.kakurin@gmail.com \
    --cc=dotzenlabs@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=marius@trolltech.com \
    /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).