Sounds good overall, but one question: On Sunday 08 November 2015 12:04:54 Ivan Čukić wrote: > Hi everybody, > > We have a few problems at the moment because all the activities > components are in a single repository. Sometimes dependencies of the > service creep up into the library, builds break because components > that are meant only for Plasma start requiring Qt versions that Plasma > require, while KF5 requirement is lower, and similar. > > The way I want to split the repository is as follows: > > - KActivities framework (essentially a Tier 1, integration or solution, all > OSs) > - kactivitymanagerd (service, kcm settings module, dolphin plugin; > officially linux-only)
Shouldn't the service be part of the framework? How usable is the framework without the service? Compiling is good, but running is even better :-) -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5 _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel