[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Deploying new kdelibs classes
From:       "David Jarvie" <djarvie () kde ! org>
Date:       2011-04-26 8:25:13
Message-ID: 420a7ef81e9cbb7d1a002fa200e90291.squirrel () www ! sensical ! net
[Download RAW message or body]

On Sat, April 23, 2011 10:22 pm, Jaroslaw Staniek wrote:
> Aurélien, I am writing regarding
> http://agateau.wordpress.com/2011/04/21/kde-ux-2011/
> One thing, about deploying the kmessagewidget (and similar things) in
> kdelibs. If it's part of kdelibs 4.7 or something, apps that support
> kdelibs < 4.7 would have to fork it (unless distro backports given
> classes to previous kdelibs but this it very bad idea and technically
> and coordination-wise). How to solve that? I am
> thinking about releasing additions to kdelibs as separate libraries
> like kdelibs47.so etc. and then merging only in 5.0.
>
> Perhaps there's already solution I am not aware of.

I'm not aware of any policy in the past to prevent new classes being added
to kdelibs. It's something that third party apps have always had to cope
with. Are you perhaps thinking of the rule in kdepim which says that it
must build against the previous version of kdepimlibs?

-- 
David Jarvie.
KDE developer.
KAlarm author - http://www.astrojar.org.uk/kalarm


[prev in list] [next in list] [prev in thread] [next in thread]