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

Aurélien Gâteau aurelien.gateau at canonical.com
Thu Apr 23 17:36:19 BST 2009

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?

What about this:
- Enclose all classes in a "Experimental" namespace.
- Put it as a separate lib in kdesupport, syncing its releases with kde
- When the lib is mature enough to maintain BC, move it to kdelibs,
removing the "Experimental" namespace.


More information about the kde-core-devel mailing list