RFC: adding a temporary, non-BC gauranteed, 'private' library .. where?

Sune Vuorela nospam at vuorela.dk
Thu Apr 23 16:00:05 BST 2009

On 2009-04-23, Allen Winter <winter at kde.org> wrote:
> On Wednesday 22 April 2009 4:21:51 pm Aaron J. Seigo wrote:
>> hi all ..
>> i'd like to move libknotificationareaitem somewhere that apps can get to it 
>> for 4.3, before looking at moving the actual class into libkdeui for 4.4.
>> is there any guidance on where it could go, how it should be installed, etc? 
>> right now i'm thinking of putting the headers in knotificationarea/, but half 
>> of me wonders if a generic private/ or experimental/ include dir wouldn't be a 
>> bad idea ...
>> any thoughts?
> We really don't have a policy on something like this.. to my knowledge.
> But we could make one.

Please don't.

Please don't put anything in kdelibs that doesn't have a stable ABI.

>From a packaging point of view, libraries with a unstable abi should not
be public.

And libraries with public headers should remember to change their SONAME
on BIC changes.

(and kdelibs should not have any changes of SONAME)


More information about the kde-core-devel mailing list