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

Aaron J. Seigo aseigo at kde.org
Fri Apr 24 18:00:42 BST 2009

On Friday 24 April 2009, Friedrich W. H. Kossebau wrote:

> And it might not work if there are also libraries which are not behind
> kdepimlibs in the dependendy chain, but between kdelibs and kdepimlibs. Or
> if even parts of kdelibs might depend on it. So such a module would only
> catch a subgroup of new libs. Hm, one should go and collect all candidates,
> current, future and previous. I guess e.g. plasmalib developers would be
> glad if they still could improve the API.

yes, if nothing else, extragear/libs/ is dependency chain neutral.

> Hm. Perhaps the best would be to rethink the policy for the modules. And
> start to allow explicitely marked parts of it to be unstable with regard to
> the next major release. No idea if packagers could solve this dependencies
> in a sane way.

that was my original proposal, and it was rejected.

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

More information about the kde-core-devel mailing list