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

[Aaron J. Seigo]

On Thursday 23 April 2009, Aaron J. Seigo wrote:
> On Thursday 23 April 2009, Sune Vuorela wrote:
> > > We're guaranteeing that for the public libraries of kdelibs, not for
> > > anything thats considered private.
> >
> > Once you install the headers, it is a public library.
>
> so phonon's experimental lib is a problem too? because as i understand it,
> it's doing the same thing. how do you handle that in packaging?

nmind; it was pointed out to me that this is all (at least in theory?) private 
to libphonon itself. though i'm mildly curious about that as the headers are 
actually installed and marked with exports.

-- 
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/6561883a/attachment.sig>