Keeping binary compatibility

Esben Mose Hansen kde at
Mon Oct 4 14:47:06 BST 2010

On Sunday 03 October 2010 19:55:07 Andreas Pakulat wrote:
> I think in most cases you'll simply get a new soname with each release
> of the KDE modules because most devs don't (want to/can) care about
> wether a particular change they're doing is bc or not. So they end up
> increasing soname shortly after trunk is unfrozen and thats not going to
> benefit you either (except that it would document that any two minor
> releases are incompatible).

That is actually preferable, I think. In this way, both the old versions and 
the new versions can coexists on the users hard drives until all applications 
have updated. If the same SO-number is used, this is not possible (you'd get 
conflicting packages instead).

The downsides --- wasted memory and disk resources --- are hopefully enough 
that most developers would take on the burden of only increasing when 
necessary. Which, if we have a tool that can do the checking for them, is not 
that hard.

kind regards, Esben

More information about the kde-core-devel mailing list