library soversion
I have a library package at version 2.01, and the soversion in it is 0.0.0
(seems upstream hadn't heard about library versioning). Now, I'm
considering packaging a new upstream version (2.3.4, still in prerelease
though), but they *still* haven't heard about library versioning, so
compiling the new source still just yields 0.0.0. And the new version is
binary-incompatible with the old release (some C++ classes changed).
What course of action is recommended here? I guess that perhaps I could
hack the upstream makefiles to add some library version, but then which
version to use? Or just rename the library? Hmm... or simply drop the old
version, since I seem to maintain all the packages that currently depend
on it anyway?
Reply to: