On 2015-06-16 09:12:36 -0700, Russ Allbery wrote: > There are a lot of really complex things you can do with versioning and > cases where that version number is meaningful, but for the vast majority > of libraries, I recommend not worrying about it and just always using some > simple transform of the SONAME as the version for all symbols in the > library. When you bump the SONAME, bump all the symbol versions. When > you introduce a new symbol, use the SONAME as the symbol version. > > This is not strictly correct in that the symbol version doesn't correspond > to a specific API (you're adding new symbols with the same symbol version > as old symbols), but most of the functionality you lose is just meaningful > error messages when running new binaries against too-old versions of the > shared library. And it's way simpler to implement.
But can this be detected so that a versioned dependency of the shared library can *automatically* be added when the binary packages are generated, avoiding this problem? -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150617065734.ga11...@xvii.vinc17.org