4.0 -> 4.1 binary compatibility

[Michael Pyne]

On Wednesday 24 October 2007, Matthew Woehlke wrote:
> Michael Pyne wrote:
> > You've kind of answered your own question though.  If we break BC with
> > 4.1 then we'll have to tell all people that just switched to 4.0 that
> > they now have to port to 4.1.
>
> Keep in mind that it was suggested 4.0 -> 4.1 to be BIC, but **NOT**
> SIC. This is different, it means you have to re-link, not re-port.

Right.  So as soon as the user upgrades kdelibs to 4.1 they have to upgrade 
the rest of KDE all at once to 4.1.

And then if they have stuff laying around that they compiled from kde-apps.org 
they get to recompile it and until then it just sits there broken.

I'm not going to claim to be an old-timer but at least as far as I can 
remember (about KDE 2.1 and on) a binary incompatible kdelibs had a new major 
version number.

I'm also curious as to the changes that we could made which would be BIC yet 
remain source compatible besides stupid stuff we can control like class 
layout and stuff.

Regards,
 - Michael Pyne
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071024/db0b86af/attachment.sig>