On Thursday 2014-01-09 14:42, Simo Sorce wrote:
Sorry, but in my book changing the SONAME for a backwards compatible
change is not ok [...] I do, maintaining a stable SONAME is
important [...] The only solution for backwards compatible changes
that require a new symbol with the same soname is to have an
explicit version dependency in the package management system. That
can be enforced only at build time.
Hey, keeping SONAME and doing symbol version maps was my preferential
pick as well, but Lukas Slebodnik did not want to. Come on, is it
really _so much_ work to maintain a symbol version file? How many
symbols get added anyway?
Just give me a clear answer already. Will sssd address the issue,
or is it going to be a "fuck you" to downstream packagers?