Re: Subversion problems with "svn switch", "svn co", "svn switch", because of 'wrong' permissions in .svn/ directories

[Brian Dessent <brian at dessent dot net>]

Bernard Blackham wrote:

> Why doesn't the Cygwin SVN build simply just #define WIN32 (or
> whatever it takes) so the code which is _already in SVN_ to work
> around this problem is actually used to fix the issue? I have not
> seen anyone give a reason as to why this shouldn't be done. (If
> there is, please feel free to flame me :)

Because defining WIN32 would enable all of the native Windows codepaths
and disable all the POSIX codepaths... that would not work very well
considering that all Cygwin functions expect POSIX paths not Win32
paths.  You'd essentially be building a native Win32 svn client that has
no POSIX capability but still uses the Cygwin library, the worst of all
possible worlds.  But I'm quite sure you wouldn't even get that far
since all those MSVCRT-specific things would stop it from even building,
such as 1-arg vs 2-arg mkdir(), %lld vs %I64d, : vs ;, _foo vs foo, etc.

What really needs to happen is to find just those places where a virus
scanner workaround exists and change "#ifdef _WIN32" to "#if
defined(_WIN32) || defined(__CYGWIN__)".

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/