"Cornelius's grand plan" - Merging KDElibs into Qt
kde-devel at arnorehn.de
Sun Oct 31 12:49:19 GMT 2010
On Sunday 31 October 2010 13:37:00 Modestas Vainius wrote:
> But what happens when you (KDE) decide that you really need a new feature
> of kioslaves for the next release. But the next Qt release is not due in 7
> months or you (again) have trouble merging changes back to Qt with
> patience running out? Sure, developers compiling from source can patch Qt,
> install differently configured builds to different prefixes with/without
> specific features etc. But what are poor packagers supposed to do? Phonon
> situation all over again? It was *really* bad and my mind is still
> recovering from that experience. I really doubt I'm ever going to trust
> such merges to Qt again.
> In my opinion, KDE should keep libraries small, *modular* and develop them
> in- house. Try not to attach binaries and esp. daemons to the libraries.
> Maybe strip KDE branding from library names to gain wider acceptance. Only
> this way you as a project will be in control of release schedules and
> feature sets.
I second that. Once our libraries are modular, we can still advertise them as
additional Qt modules, similar to Qxt, QtLua or Qwt.
But integrating them with Qt as tightly as proposed has more drawbacks than
advantages, imho (all of which were already posted).
arno at arnorehn.de
More information about the kde-core-devel