Hi, Daniel,
> Von: Daniel Shahaf [mailto:d.s_at_daniel.shahaf.name]
> Markus Schaber wrote on Fri, May 13, 2011 at 11:20:11 +0200:
> > 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.
>
> What about SVN_ERR_WC_UPGRADE_REQUIRED?
I did read this error code as "the working copy is in an known, but
older format, I need and can perform an explicit upgrade" - just the
opposite of what I need. And it is marked as /** @since New in 1.7. */,
so 1.6.16 is unlikely to raise it.
> > Is there a function specifically designed for this purpose?
>
> If there isn't, it seems like a good idea to have one, in order for
the
> library to clearly communicate "I cannot perform <a contract-specified
set
> of basic operations> on this working copy unless you upgrade it".
[> ]
Best regards
Markus Schaber
___________________________
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 |
Fax +49-831-54031-50
Email: m.schaber@3s-software.com | Web: http://www.3s-software.com
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects:
http://www.3s-software.com/index.shtml?sample_projects
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner |
Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
Received on 2011-05-16 07:49:23 CEST