Re: svn1.7.x compatibility issues

On 27 October 2011 17:50, Alexander Stohr <alexander.stohr_at_gmx.de> wrote:
> when updating TortoiseSVN from 1.6.x or earlier to 1.7.0 and later any of the repositories needs updating - this can be a more or less lengthy process. the user needs to manually initiate this for any single repository tree.

I think you mean working copy. Please use the correct terminology or
it becomes very confusing.

> the result will be a .svn subdir in the root of every local repo copy whilst all .svn subdir in the non root-level of the local repo will be gone.

Correct.

> as soon as it comes to "compatibility" alternate command line tools wont work any longer since the new repo format is only compatible with 1.7.0 and newer. if i am right there is no downgrade path.
>
> so if you are having more than just TortoiseSVN placed in your environment or even heavily depend on some other older version tool then an update to 1.7.0 or newer should be avoided on your critical machine.

Also correct. This is clearly mentioned in the release notes for TortoiseSVN 1.7

> hint 1: some other win32 clients might be listed earlier in the shell path - normally TortoiseSVN will provide command line tools with a path extension - its not granted that it will be your first SVN command line tool in that list.
>
> hint 2: if you need support for both repo types you have to fiddle out how to have two concurrent toolings side to side. maybe a bit renaming or some case-to-case path definition might help.

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2865477
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].