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

Aaron J. Seigo aseigo at kde.org
Fri Apr 24 07:47:23 BST 2009

On Thursday 23 April 2009, Sune Vuorela wrote:
> On 2009-04-24, Aaron J. Seigo <aseigo at kde.org> wrote:
> > 2) please don't use libknotification-1.so, use libknotification.so.1
> Yes. this. and proper change .so.1 to .so.2 (and the SONAME as seen by
> the linker & friends)

i'm fine with that as long as you can guarantee me that nobody will link 
against libknotification.so, and thereby cause havoc when BC is broken between 
minor releases of kde.

`ls -l /usr/lib/*[1-9].so` is pretty enlightening as well

so, what's the benefit you see so so.1, so.2? i just see a potential landmine 
due to symlinking to .so and app devs making the mistake of linking to the 
wrong thing ...

Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software

-------------- 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/20090424/6337f8de/attachment.sig>

More information about the kde-core-devel mailing list