Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Safe to share a Subversion working copy between OS?

Tags:

svn

I've heard in the past that it's unsafe to share a Subversion working copy between OS.

E.g.:

  1. copy a working copy from a Windows machine to a Linux machine, and use the Linux build of SVN on it.
  2. On a Windows machine, access/manipulate an SVN working copy with both Windows binaries and CygWin binaries of SVN. (I might want to do this to use this solution for example).

But I haven't heard definitively whether it could cause corruption of the .svn data. It is true that EOL issues could be a problem if svn:eol-style is set to native.

What's the current status of this issue? Has it changed in more recent releases of SVN? Is it safe provided certain precautions are taken (e.g. not checking out/updating files with svn:eol-style=native on both platforms)?

like image 871
Craig McQueen Avatar asked Jun 30 '09 01:06

Craig McQueen


People also ask

What is working copy in Subversion?

A Subversion working copy is your own private working area, which looks like any other ordinary directory on your system. It contains a COPY of those files which you will have been editing on the website.

How do I find my svn working copy?

You've got the answer for command-line tools, but if you're using TortoiseSVN on Windows, you can just right-click your working copy and click "Properties". There is a Subversion tab in that dialog which tells you the URL your working copy is pointing to.

What is .svn folder?

svn, also known as the working copy's administrative directory. The files in each administrative directory help Subversion recognize which files contain unpublished changes, and which files are out of date with respect to others' work.

How to remove TortoiseSVN?

How do I uninstall TortoiseSVN? Simply uninstall from Add/Remove Programs in the Windows control panel. This does not affect your repositories or working copies at all.


2 Answers

I've used svn on a shared network directory between unix, linux, solaris, and windows; anecdotally the only problem I ran into is that different svn client versions are 'incompatable'. The linux and unix machines were equiped with a version of svn older then the solaris svn; which was in turn older then the windows machine client. The result is that running 'svn up' updates the metadata files to whatever client is running; and the client won't access files with a more recent metadata version. Final end result being that svn clients should be kept at the same version number.

So, yes, I've been able to move a working directory around between machines with minimal loss of life. That said, I've never used any svn options beyond what was default.

like image 97
CoderTao Avatar answered Oct 06 '22 20:10

CoderTao


My svn repository is on Linux. I have a working copy on Linux and another one on WindowXP.

On WindowXP, I use cygwin to access my working copy. Sometimes, I use also Tortoise to have a visual diff, a compplete history of a file...

I never try to restore ( or create form a backup) from a Linux repository created with svndump to a Window computer.

[EDIT]

I forgot to mention that update works perfectly with both working copy.

like image 32
Luc M Avatar answered Oct 06 '22 22:10

Luc M