Baloo wants to become part of KF5, starting with KF 5.13. Is this going to create a problem for packagers who had baloo as part of plasma in the last release?
I'm not sure how to help avoiding the issue, I guess the only solution is for such distros to put KF 5.13 on hold until the next Plasma release? I think this shows that code should first move, then be named like libKF5Baloo.so, rather than the other way round. -- David Faure, [email protected], http://www.davidfaure.fr Working on KDE Frameworks 5 _______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
