<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Hi,</div><div><br></div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Lucida Sans'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">But indeed it mean, you need to care about the versionning of your public C API/ABI.</span></blockquote></div><br><div>First it would be a C++ ABI in the cctbx case but, see my earlier email, we do not provide any shared library that is linkable by a generic C++ program. We only provide shared libraries that are to be loaded by the Python runtime. So those shared libraries are just Python module and their being written in C++ is an implementation detail. What matters is therefore only the Python API, in which I include the Python API exposed by our *.so, on the one hand and the C++ API on the other hand. But then each cctbx release contains a TAG file providing a version number the set of which is sortable, e.g. 2012_05_08_2305 </div><div><br></div><div>Thus it seems to me that you only need to get that version number through to the Debian packaging system. And we are done with that.</div><div><br></div><div>Again, have I missed something?</div><div><br></div><div>Best wishes,</div><div><br></div><div>Luc</div><div><br></div></body></html>