From: Charles W. <cwi...@us...> - 2011-03-12 17:11:42
|
On 3/12/2011 1:52 AM, LRN wrote: > On 12.03.2011 8:56, Charles Wilson wrote: >> (fyi: the 'msysgit' >> version of git is actually a *win32* port, bundled with an msys environment) > I know. It was a shocking thing to discover. > Though, if msysgit (which is really a mingw-git) works as intended > without using msys - why not use it? I suspect -- but do not know for certain -- that an msys port will be a better approach, mainly because upstream git is, by and large, a unix-oriented tool. AFAIK, msysgit's win32 patches have not been accepted upstream -- but we DO know that the cygwin port is well supported. In fact, the maintainer of cygwin's official package of git applies some patches because: > When compiled out of the box, the upstream git maintainers cater to > older cygwin releases, and intentionally disable certain features that > have been reported on their mailing list, even though they work with > the latest cygwin. Therefore, this build turns those features back > on. that is, upstream git focus on working with old cygwin -- which means that (unlike, for instance, openssh) we can expect stock upstream git to play nicely with MSys. (Sadly, as cygwin gains or improves support more features, openssh is updated to use them, or to remove old workarounds. With each new openssh release, I have to do code archeology and put those workarouds back in, to allow openssh to operate with MSys's more primitive featureset) Further, git has several library dependencies for optional functionality, and by and large porting random-package-X to MSys is a lot easier than porting it to 'native' win32 (openssh's counterexample notwithstanding). So, we can more easily get a relatively-full-featured git by going the MSys route, than by sticking with a more-or-less stripped-down mingw32 version of git. I'm also thinking about automation. If we port git -- either borrowing msysgit's mingw version, or our own msys port (*) and eventually transition our sourceforge.net CVS repo to the new format, we have several automation tools such as the Makefiles associated with building mingw-get xml manifests that would need to be ported. Making these all work and accept win32 paths will be...awkward, so I'd prefer to stick with unixish formulations wherever possible. (*) or some other modern DVCS tool; it's just that git is under discussion in this thread That's just my gut feeling, but... -- Chuck |