[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: "same inode" problems with cygwin svn client

From: Bill Tutt <rassilon_at_lyra.org>
Date: 2002-09-06 09:55:15 CEST

> From: Dylan Cuthbert [mailto:dylan@q-games.com]
> "Bill Tutt" <rassilon@lyra.org> wrote:
> > a) Cygwin == evil porting library
> > So, any issues you have with using a svn client compiled under it
are up
> > for grabs. IMNSHO, any official svn client binary should be
> > using cygwin. If you want it to be compiled with GCC then use mingw.
> Hey, cygwin isn't quite that evil, it gives windows users a breath of
> fresh
> air, allowing the use of emacs, bash, even Xfree86.. not to mention
> another 500+ really useful unix tools and libraries.

For things that don't port well to Windows, then yes it does, and all
power to folks who like such things.

However, for projects like Subversion that have been ported to work on
Windows, cygwin just shouldn't be used. It makes the maintainer's job
more annoying by introducing the machinery cygwin uses to accomplish
some of the API calls used in Unix programs. Usually to a perf
detriment, not to mention assuming the users cygwin install is bugfree.

If it works lucky you, but don't expect everybody to be terribly
thrilled about helping you solve problems with cygwin hosted Subversion

We have more important things to care about than chasing down possible
cygwin bugs. :)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 6 09:55:49 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.