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

RE: Working copy corruptions due to dual use of SVN on Linux and Windows against same working copy

From: Wayne Johnson <wayne_at_zk.com>
Date: Tue, 20 Nov 2012 15:34:10 -0800

> This may be true, there may be implementation decisions made that
> prevent using a working copy from one system on another. But if this is
> the case, I think this is a bad design decision; or at the very least,
> bad documentation. Consider a person who keeps a working copy on a
> thumb drive to cart around with them to whatever computer they happen
> to be working on. Shouldn't they be able to commit, update, whatever,
> on any of these systems, as long as a compatible version of SVN is
> installed? At the very least, the fact that SVN does not operate well
> across OSes should be documented. Using git or Hg, for example, I would
> certainly expect this to Just Work, I see no reason why SVN should be
> different in this regard. A program should be able to read and write
> its own data regardless of where the program was running at the time
> the data was created.

This is more than just an issue of how the code is written. You also have
to take into account how the code is built. Further there are things you
can do with a Linux file system that cannot be done (or is done very
differently) than a Windows file systems.

So, I think it would be unreasonable to expect a tool built by Bob for
windows and the same tool built by Jack for Linux to necessarily play nice
together since we don't even know of the same build options were used for
all the libraries used by the tools.

Finally, there are configuration options that can be set in subversion
that will create confusions if used from multiple OS's. Setting line
endings to OS default comes to mind. There may be others.

To complicate the matter the original poster was using TSVN on a Samba
share. This pulls in another set of build/configuration issues that must
be handled by the user.

That's not to say that there aren't things that the SVN devs can do to
make this better or worse. It just to point out that even if they did
everything possible it still won't solve the problem 100% (assuming they
don't do the official releases.) Also keep in mind that they are in the
same boat as the rest of us. They have features and bugs to fix and they
have to decide which ones are more important.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-11-21 00:34:47 CET

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.