Comment 4 for bug 1505187

Marble/kgeomap uses in wily qt5/kf5
digikam 4.* is qt4/KDE4

you can mix qt4 with qt5 (plugins), therefore no kgeomap support in digikam 4.* anymore.
As qt4/kde version of marble is no longer maintained it can't be included into a new release.

As soon as digikam 5.* finds it's way into a kubuntu release kgeomap support will return.

I suggest to set the bug to 'won't fix'.

Achim

 #kubuntu-devel:

[23:52:22] <yofel> clivejo: what's the actual problem?
[23:52:51] <clivejo> libkgeomap is looking for marble-config.cmake
[23:53:06] <ahoneybun> I'll be working but g2g for now
[23:53:19] <yofel> oops
[23:53:30] <yofel> I guess nobody removed that. libkgeomap is unbuildable in wily
[23:53:50] <clivejo> nice to know
[23:53:52] <yofel> looks for qt4 marble, and we only ship qt5 marble
...
[02:21:22] <claydoh> what happened to libkgeomap for digikam/kipi in wily?
[02:25:25] <sgclark> no clue
[02:52:54] <claydoh> https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1459443
[02:52:55] <ubottu> Launchpad bug 1459443 in digikam (Ubuntu) "Reenable gpssync plugin in digikam" [High,Triaged]
[02:53:16] <claydoh> but I can't find why it is gone or if it is coming back
[02:54:53] <sgclark> umm well http://osdir.com/ml/ubuntu-bugs/2015-08/msg16295.html
[02:55:14] <sgclark> seems odd
[02:56:15] <sgclark> ahh indeed it is qt4 only
[02:56:26] <sgclark> won't work in wily
...