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

Alexander Neundorf neundorf at kde.org
Thu Apr 23 22:01:28 BST 2009

On Thursday 23 April 2009, Friedrich W. H. Kossebau wrote:
> Hi Aaron and all,
> So if there e.g. can be another module for libraries, in the dependency
> chain between the base lib modules (kdelibs and kdepimlibs) and the base
> modules (kdebase, kdeutils, kde...) and not bound to ABI stability between
> major releases, that would be helpful. To give new libraries a chance to
> develop.

Maybe new libs could be for the first release cycle in kdelibs-experimental 
and if they prove to be good advance to kdelibs for the next cycle, otherwise 
be removed again ?

> And if adding this module or another similar option, on this change also
> kdebase should be finally split up as well, by lifting the three hidden
> modules on the level where they belong.

You mean a kdebaselibs module ?
I'm all for it.


More information about the kde-core-devel mailing list