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

Kevin Krammer kevin.krammer at gmx.at
Fri Apr 24 11:51:48 BST 2009

On Friday, 2009-04-24, Friedrich W. H. Kossebau wrote:
> Vrendedi, le 24 avril 2009, à 12:10, Thiago Macieira a écrit:
> > We want to have knotificationitem-0.1.tar.gz. The place for individual
> > packages is extragear.
> Also for those which are a hard dependency for e.g. kdebase?

It is just another external library, i.e. it is either optional for additional 
features or required, in which case it needs a CMake check for the required 

> Or kdepimlibs
> (who perhaps might be happy to have some more time to make the
> akonadi-based APIs stable)?

We do that in module private libs in kdepim.

> For myself I would be happy to publish the okteta{core,gui} libs for reuse
> by others. But they are not extra to Okteta, they are fundamental. And will
> just change and be released along major KDE versions. So _extra_gear really
> does not fit for it IMHO. I would very much like another solution.

If they are specific to a certain version of Okteta, just release them with 
that version, no?

Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090424/7921f974/attachment.sig>

More information about the kde-core-devel mailing list