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

RE: Re: Determining TrotoiseSVN version from a script.

From: Bob Cunningham <bcunningham_at_sandel.com>
Date: 2007-08-06 21:07:50 CEST

Stefan Küng wrote:
> Bob Cunningham wrote:
>> Huh? "svn:native" is EXACTLY what we do, and it works FINE for us
>> using both TortoiseSVN and Cygwin svn (both at 1.4.3). Using
>> anything other than Native ensures our cross-platform builds will
>> have problems.
>> SVN's use of properties was one of the many factors that led us to
>> choose svn instead of cvs when switching from MS VSS.
> And that's EXACTLY your problem (as we mentioned before):
> Cygwin will checkout/handle the files with LF lineendings, while
> native SVN clients will checkout/handle the files with CRLF
> lineendings.
> If you use both clients, everything gets mixed up and your working
> copy gets broken.
> But that's just one incompatibility which arises (the most obvious
> one).
> The working copy format is handled a little bit different on Linux
> and Windows. And they are not compatible. That's a fact which won't
> get changed (you can try asking on the Subversion mailing list, but
> you will discover that they gave up trying to keep them compatible
> long ago).
> Stefan

No, Stephan, you are mistaken. All my arguments about version conflicts apply if you substitute the Tigris CLI svn client instead of the Cygwin client.

We are NOT having any problems with checkouts and checkins when the versions of the Cygwin svn and TSVN match. None at all.


To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Aug 6 21:06:01 2007

This is an archived mail posted to the TortoiseSVN Users mailing list.

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