Hi, On Sat, 1 Nov 2008, Alex Riesen wrote: > Johannes Schindelin, Sat, Nov 01, 2008 01:23:32 +0100: > > > > Well, if you install Git for Windows (as opposed to cygwin), it is > > minimum hassle, and Perl is delivered right with it. > > I'd like to try it again, but weren't ther some fatal problems with > cygwin1.dll being in PATH? I always work either in Cygwin's bash or just > have to have it in PATH, because of the build environment even being > strictly Windows based (case-insensitive and alike) just have to use > sane tooling in its scripts. I was talking about Git for Windows, i.e. the result of msysGit (as opposed to Git in Cygwin). So no, there have not been any conflicts with cygwin1.dll in the PATH, as far as I can recall. There have been problems with shell utilities being found in the Cygwin PATH before being found in the MSys PATH, but I thought we just prepended the MSys PATH to avoid that. Haven't checked, though. > > P.S.: some guys at the GSoC mentor summit convinced me in at least > > trying to fix _their_ problems on msysGit, so chances are good I'll > > fix issues you would encounter in the same run. > > Do you still plan to distribute MinGW with it? It's very nice to be able > to track Junio's repo, have own branches and rebuild Git from time to > time. For me, at least. You mean to distribute a minimal MSys environment where you have bash? Yes, we have to do that, as there are still too many important parts of Git written in Shell. Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
