Binary compatiblity for

Thomas L├╝bking thomas.luebking at
Sat Feb 25 14:12:06 GMT 2012

Am 25.02.2012, 12:17 Uhr, schrieb Pino Toscano <pino at>:

>> In both cases it does not fix (sorry for repeating myself) the true
>> issue, which is that your plugin_path is not consistent with your

> Which "pernicious effects"? Only the old plugin being loaded?
Using wrong ABI stable lib or libexec dir
a) should however only hit users which can be expected to know what they  
do? (ie. kdelibs developers)
b) hinting that by a crash isn't the ideal way (nasty AND unreliable ...  

Maybe one could trick around here to get -rpath away from that lib, but  
since there's also an independent version of oxygen (ARGB enabled) which  
probably links liboxygenstyle as well(?) bumping the .so would be quite  
reasonable - at least to avoid conflicts on this side.

> Remember that potentially who compiles trunk usually is interested in
> working on their stuff,
Now actually those really should care about the lib path  - and actually  
better the plugin path as well - for their own good :-P


More information about the kde-core-devel mailing list