[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: Erik Huelsmann <ehuels_at_gmail.com>
Date: Fri, 13 May 2011 14:30:04 +0200

Hi Markus,

On Fri, May 13, 2011 at 11:20 AM, Markus Schaber
<m.schaber_at_3s-software.com> wrote:
> Hi,
>
> 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.

Why do you want to know if a working copy changed its storage type?

Bye,

Erik.
Received on 2011-05-13 14:30:36 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.