This starts to become a dangerous path (Was: New Feature for kdelibs)

David Faure faure at
Thu Nov 17 09:41:44 GMT 2011

On Wednesday 16 November 2011 19:07:51 Jaime wrote:
> Hello,
> Probably I've missed something, or what I propose is unpractical (or too
> late), but here I go, anyway:
> If the frameworks branch still depends on Qt 4,
> Is it possible to have a "public" version of it once the
> refactoring has been completed, but before it depends on Qt 5?
> It could be used as a frozen master for SC 4.9 (or SC 4.10?) and, to some
> degree, make the migration path to it easier.
> Let's say it is Milestone 1 of 2. After that Milestone, it could be changed
> to use Qt 5.

This would require 1) that frameworks is ready before qt 5 is (with the 
current development speed, that remains to be proven), and
2) that apps port twice. Once to frameworks, and then once again to Qt5.
Not sure that would be a good idea.

It also shortens the window of API changes in kdelibs-frameworks, basically.

David Faure, faure at,
Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5

More information about the kde-core-devel mailing list