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

Re: Detect incompatible (future) workingcopy format.

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Fri, 13 May 2011 07:52:42 -0500

On 5/13/11 7:30 AM, Erik Huelsmann wrote:
>
>>
>> What is the safest future-compatible way to check for an incompatible /
>> unknown working copy format which was written by a future subversion
>> version? (e. G. WC-NG by SVN 1.7?)
>>
>> My idea was to run status with depth=empty on the workingcopy root, and
>> check for SVN_ERR_WC_UNSUPPORTED_FORMAT error code.
>>
>> Is there a function specifically designed for this purpose?
>
> No. The current library functions are forward compatible for the
> entire 1.x range. The working copy storage is considered to be an
> internal artifact, meaning you're supposed to use the libraries (e.g.
> through the python bindings) to access the working copy data.

Doesn't that assume that there is only one version of the library that can
access a working copy location or at least that the versions only go forward
over time? There are a large number of ways that assumption can be wrong.

--
   Les Mikesell
    lesmikesell_at_gmail.com
Received on 2011-05-13 14:53:16 CEST

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

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