RFC v2: adding a temporary, non-BC gauranteed, 'private' library

Modestas Vainius modestas at vainius.eu
Fri Apr 24 22:01:42 BST 2009


On 2009 m. April 24 d., Friday 23:31:40 Aaron J. Seigo wrote:
> > libplasma ABI breakages used to be very
> > constant from my POV.
> which is why we kept it in kdebase until it (and QGraphicsView, which was
> one of the major motivations for BC changes) was mature.
Yes, but libplasma had only 2 SONAME bumps whereas there were a lot more 
ABI/API breakages. That's why I'm saying that shared linkage for unstable 
API/ABI is a nightmare to manage.

> > So will you let yourself to break API/ABI for minor KDE stable release?
> it really depends on the library, and if it breaks between releases then it
> _should_ have the .so number changed.
Do you really expect to change SONAME of that lib between minor KDE releases? 
Btw, packagers release packages of KDE development releases these days and 
those non-SONAME ABI breakages are not fun. That's why I'm saying I would like 
static linkage to be allowed at least during beta/rc releases.

Modestas Vainius <modestas at vainius.eu>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090425/d02c9e2c/attachment.sig>

More information about the kde-core-devel mailing list