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

[Aaron J. Seigo]

On Thursday 23 April 2009, Aurélien Gâteau wrote:
> 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.

that's doable.

> - Put it as a separate lib in kdesupport, syncing its releases with kde
> releases.

it depends on libkdeui (KSystemTrayIcon), so it can't go into kdesupport.

> - When the lib is mature enough to maintain BC, move it to kdelibs,
> removing the "Experimental" namespace.

and the headers? that's really my big question. protecting symbols is easy, a 
policy on where to put such headers is less clear to me.

-- 
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/20090423/f7642cb7/attachment.sig>