RFC v2: adding a temporary, non-BC gauranteed, 'private' library

[Aaron J. Seigo]

On Friday 24 April 2009, Modestas Vainius wrote:
> > if the API is going through constant ABI breakage, then it isn't ready
> > for this process. only when an API is ready for trialing for actual
> > inclusion in, say, kdelibs would you put it in there. that means a fairly
> > confident API, but not confident enough to commit to 5+ years of support.
>
> So you have to set a few rules here, because I might understand "constant
> breakage" differently than you.

i don't think we do, no.

> libplasma ABI breakages used to be very
> constant from my POV.

which is why we kept it in kdebase until it (and QGraphicsView, which was one 
of the major motivations for BC changes) was mature.

> May I remind you that you want to _release_ stable
> KDE depending on this library.

you don't need to remind me, it's the entire point of figuring this out and 
why i'm willing to subject myself to sprawling hydralike threads.

> So will you let yourself to break API/ABI for minor KDE stable release?

it really depends on the library, and if it breaks between releases then it 
_should_ have the .so number changed.

-- 
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/20090424/a1adcb64/attachment.sig>