tags:

views:

62

answers:

3

Is it possible to prevent a newer SVN client (say 1.6) from automatically upgrading a working copy that was checked out with an older client (say 1.4 or 1.5)?

I find that as soon as I touch a working copy with a newer client, anyone using an older client to work with the same files can no longer do so (for obvious reasons).

Assuming requiring everyone to upgrade their SVN clients isn't an option, is there a configuration setting or flag I can set to prevent my newer client from making this change?

A: 

Working on a repo with multiple client versions is not recommended for this reason! You can set access permissions per user and use different clients on your local machines with different SVN users.

Andy
+1  A: 
Michael Hackner
+1  A: 

It seems counter-intuitive to me that you have multiple people using the same working copy. Having multiple clients is one thing (for example, I have AnkhSVN and TortoiseSVN that access my working copies) but having multiple people using the same working copy is - to me - not the normal way SVN should be used.

I would say the "ideal" solution would be to give each person their own working copy, and then let them use whatever client version they like.

Dean Harding
I have already seen wicked configurations like this: One WC on a shared directory with everyone working on that WC. It will fail every now and then and sometimes kill your work. So everyone should have their own WC!
Hardcoded
@Hardcoded A working copy in a shared directory?! That gives me chills. And not the good kind.
Michael Hackner