[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: RFC v2: adding a temporary, non-BC gauranteed, 'private' library
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: 2009-04-24 20:31:40
Message-ID: 200904241431.41266.aseigo () kde ! org
[Download RAW message or body]
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
["signature.asc" (application/pgp-signature)]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic