On Wed, 2004-01-07 at 14:28, Sean Cier wrote:
> I can buy that the problem may be on the Cygwin side; but given that other
> applications work fine (notably cvs), is there not a simple way to just make
> this work? If this is a specific design decision, a tradeoff made
> consciously, and a known issue that won't be addressed, that's okay; I just
> wanted to make sure it wasn't a real, fixable bug.
Here's my impression: most win32 console apps are really just "standard
C i/o" programs... they call printf() and scanf() directly from
stdio.h. That's why they work in both cygwin bash and the NT console.
But Branko and other svn developers have put considerable effort into
making the svn console app deal with complex things, like win32
codepages and i18n support... stuff the cvs binary doesn't handle, and
stuff that requires very specific win32 console APIs. That might be the
reason that your svn binary isn't "just working".
On the other hand, someone just mentioned that it does work for them in
cygwin, so maybe your EOL settings are the culprit, as you suggest. The
main point I'm trying to make, though, is that the svn win32 developers
aren't very keen on supporting the native win32 client within a cygwin
environment. If it works for you, great, but "you're on your own." The
better long-term solution is for the Subversion project to start
distributing true cygwin binaries; we just haven't found a volunteer
willing to do that yet. Maybe the cygwin project could even do it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 7 21:42:12 2004