> If we backport your unlock_prompt_func patches to 1.7.3, someone
> downgrading the bindings from 1.7.3 to 1.7.2 will get runtime linker
> errors, correct? If so we cannot backport it.
I think that will not happen, since the C function is defined in the
bindings, not in the main subversion libraries. In other words, the C
code required is included with the bindings (so there's even three
versions of the function, one for each binding), so downgrading the
bindings removes the py/pl/rb function as well as the C function
wrapped. The C function itself only uses pre-existing stuff in the main
subversion libraries, so that should not cause any problems either.
I just did some tests with the python example: When doing a "make
install" from the latesst tree and "make install-swig-py" from a 1241553
tree (before my patch was added), I get no linker errors (but I don't
get a prompt either, the hasattr() call in the example can detect the
absence of the function just fine [or an AttributeError would be called
When doing it the other way around (old main libraries with new
bindings), everything works fine, I even get the prompt.
Received on 2012-02-08 17:11:34 CET