AW: Auto Upgrade Behavior
From: Markus Schaber <m.schaber_at_3s-software.com>
Date: Mon, 27 Aug 2012 13:39:03 +0000
Von: Stefan Sperling [mailto:stsp_at_apache.org]
I'm not sure whether a disabled auto-upgrade will improve Pauls situation here, it will most likely cause the "checkout" operation in the nested working copy to fail.
That said, for CoDeSys SVN we cannot perform automatic upgrades. The reason is that we guarantee that projects can be still opened with older CoDeSys versions as long as the user did not explicitly allow the format to be upgraded. (This is part of a rather strict backwards compatibility strategy, which even includes a guarantee of providing bit-identical compilations including bugs when the user configures an older compiler version.) On the other hand, we're using our own metadata for that check even before the svn libraries are allowed to touch the working copy, so we can cope with whatever SVN implements here. :-)
-- ___________________________ 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: email@example.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 167014915Received on 2012-08-27 15:42:03 CEST
This is an archived mail posted to the Subversion Dev mailing list.