--===============3151940721919278870==
Content-Type: multipart/signed; boundary="nextPart38146513.siauL4d1go"; micalg="pgp-sha1"; protocol="application/pgp-signature"


--nextPart38146513.siauL4d1go
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"

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
--nextPart38146513.siauL4d1go
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEABECAAYFAlQZWK4ACgkQqVXwidMiVrqLpgCgimw3tAyoXZAyU3YGg4JOylwh
68AAn1OkKJQBCBKi7MjclQO5nNbZubi4
=9L7M
-----END PGP SIGNATURE-----

--nextPart38146513.siauL4d1go--


--===============3151940721919278870==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============3151940721919278870==--