[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: Move of kglobalacceld from plasma-workspace to kglobalaccel framework
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2014-12-12 12:04:59
Message-ID: CACcA1Rq-v0E_akEJp3tCPBTXYsz10jBuDYuNU54rjfmkFzcTXQ () mail ! gmail ! com
[Download RAW message or body]

On Wed, Sep 17, 2014 at 11:47 AM, Martin Gräßlin <mgraesslin@kde.org> wrote:
> Hi all,
>
> I just prepared moving kglobalacceld from plasma-workspace into kglobalaccel.
> You can find the code in my personal clone of kglobalaccel at [1] in branch
> master.
>
> The following steps were performed so far:
> * filter-branch on plasma-workspace to just have all kglobalacceld commits
> * move all files to src/runtime
> * merge code in kglobalaccel
> * adjust CMakeLists to find additionally needed dependencies for runtime part
> * raise tier to 3 in metadata
>
> Please have a look at it, whether I have forgotten something or should do
> something differently.
>
> Things I'm unsure about is:
> * how does the raise of framework needs to be reflected in cmake
> * how do one expose the different licences?
> * is it needed to export the new dependencies? After all they are just runtime
> deps?
>
> Cheers
> Martin
>
> [1] kde:clones/kglobalaccel/graesslin/kglobalaccel
> _______________________________________________

+1
I guess this means it will only have the daemon on X11/Linux, no? What
happens with the other platforms?

Aleix
_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel

[prev in list] [next in list] [prev in thread] [next in thread]