Wolfgang Bauer wrote:
Am Donnerstag, 3. März 2016, 23:46:41 schrieben Sie:
Compatibility with KDE3 is not an issue for me. But for me.
And I'm not going to add a patch to our packages that causes such a regression (and it doesn't seem to help in your case anyway).
In fact I will even report this problem upstream and hope that commit gets reverted or fixed... Yes, good idea.
Personally I think that GTK+ 3 and Java support is important.
And I wanted to compile plasma-workspace/xembed-sni-proxy without all the other plasma-workspace directories. But why? This is basically the same as I packaged.
There only have been 3 changes to xembed-sni-proxy in master (compared to 5.5). I backported 2 of them, the 3rd one is about transparency which I'm pretty sure won't help you either.
Thanks for the hints. But I have libxcb-devel installed. I also manually checked all the required packages from the recommended xembed-sni-proxy.spec file (e.g. with something like "rpm -q extra-cmake-modules" or "pkg-config --version xcb-xfixes"). Currently I do not know, how to test the cmake requirements (e.g. "BuildRequires: cmake(KF5WindowSystem)"). As mentioned: zypper wp "cmake(KF5WindowSystem)" This gives: S | Name | Summary | Type --+---------------------+----------------------------------------------+-------- | kwindowsystem-devel | KDE Access to window manager: Build Environm-> | package
You can also tell zypper to automatically install all build dependencies of the xembed-sni-proxy source package (I don't think the BuildRequires have changed): zypper si -d xembed-sni-proxy
OTOH, you can also get the latest master version of plasma5-workspace from the KDE:Unstable:Frameworks repo. If you don't want to install that (which would be understandable of course ;-) ), you can just extract the xembedsniproxy executable and copy it to your system as I already wrote. Thanks for the hints. I installed all the build-dependencies from xembed-sni-proxy, e.g. like suggested
# zypper wp "cmake(Qt5X11Extras)" Command 'what-provides' is replaced by 'search --provides --match-exact'. See 'help search' for all available options. Loading repository data... Reading installed packages... S | Name | Summary | Type --+--------------------------+--------------------+-------- | libqt5-qtx11extras-devel | Qt Development Kit | package # zypper install libqt5-qtx11extras-devel Anyway, the Git master source for plasma-workspace/xembed-sni-proxy still complains: -- Detecting CXX compile features - done CMake Error at CMakeLists.txt:8 (find_package): By not providing "FindXCB.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "XCB", but CMake did not find one. Could not find a package configuration file provided by "XCB" with any of the following names: XCBConfig.cmake xcb-config.cmake Add the installation prefix of "XCB" to CMAKE_PREFIX_PATH or set "XCB_DIR" to a directory containing one of the above files. If "XCB" provides a separate development package or SDK, be sure it has been installed. I tested xembedsniproxy extracted from http://ftp5.gwdg.de/pub/opensuse/repositories/KDE:/Frameworks5/openSUSE_Fact..., but it also shows the discussed problems (Java tray icons not working, tiny Pidgin 3.0.0 icon). I will probably wait for fixes from the KDE or Pidgin teams. For Pidgin I will probably file a bug report. For KDE I will re-check, if all important details are already reported. Fortunately the Pidgin tray icon is optional and can be disabled in preferences in the meantime. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org