KF5 porting

[Albert Astals Cid]

El Dijous, 27 de febrer de 2014, a les 19:03:59, Kevin Kofler va escriure:
> Hi,
> 
> Is there any centralized plan and/or timeframe to port kdesdk to Qt 5 and
> KF5? Or is it all left to the individual application maintainers? Or are we
> on the contrary to follow some global KDE plan I don't know about yet?
> 
> In particular, I would like to know:
> * Is now the time to port kdesdk applications to KF5?
> * If yes, how do we do it? Do we create a "frameworks" branch? (I'm
> personally opposed to #ifdef abuse as seen in Marble, I'd rather have a
> separate branch.)

Yes please, if you're going to do a KF5 port, name the branch "frameworks" 
like everybody else is doing.

Cheers,
  Albert

> * If this is up to the individual maintainer, does creating a "frameworks"
> branch for Kompare sound sound to you? (And no, "sound sound" is not a typo.
> ;-) ) I DON'T intend to lock master or anything like that, just to create a
> separate porting branch.
> 
> We also need a plan for libkomparediff2, because Kompare obviously depends
> on it (and so does KDevelop now). (In other words, before I can think of
> porting Kompare, I need libkomparediff2 ported, and I can't do that without
> a plan.) Should libkomparediff2 try to become a KDE Framework or should it
> keep living in kdesdk?
> 
>         Kevin Kofler
>         (who is still a bit lost in Frameworks land)
> 
> _______________________________________________
> kde-sdk-devel mailing list
> kde-sdk-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-sdk-devel