The least one can do downstream is to stay in sync with that (e.g. by contacting the Debian maintainer), but if the jsoncpp API/ABI changes, this could quickly inflate the SONAME version.
Hence it would be strongly recommended that the jsoncpp developers decide which SONAME to use and which versioning scheme. If there are still frequent changes during development, a compromise would be to add the major version of a stable series somewhere, e.g. libjsoncpp-0.6.so.0, which would require dependencies to be rebuilt any time that version changes.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, Debian have introduced a SONAME in a patch ( LINKFLAGS='-Wl,-soname,libjsoncpp.so.0' ) calling the library
libjsoncpp.so.0.6.0: http://packages-powell.debian.org/en/wheezy/armhf/libjsoncpp0/filelist
The least one can do downstream is to stay in sync with that (e.g. by contacting the Debian maintainer), but if the jsoncpp API/ABI changes, this could quickly inflate the SONAME version.
Hence it would be strongly recommended that the jsoncpp developers decide which SONAME to use and which versioning scheme. If there are still frequent changes during development, a compromise would be to add the major version of a stable series somewhere, e.g. libjsoncpp-0.6.so.0, which would require dependencies to be rebuilt any time that version changes.
If this is not fixed by using cmake, please re-open at: https://github.com/open-source-parsers/jsoncpp/issues/new