Hi Martin! On Sun, Jan 06, 2019 at 09:14:59PM +0100, Martin Graesslin wrote: > QtWayland consists of a client part (providing the qpa platform plugin) and > a compositor part (providing an API to implement a Wayland server). > In Debian it's not possible to just install the client part. Thus the Plasma > session requires to install the server components, although it doesn't > use anything of it. This results in a wrong impression that KWin depends on > Qt compositor. Overall this package is just weird. Currently from the qtwayland source package we build multiple binary packages, including separate binary packages for client shared library and header files, compositor shared library and header files, and plugins. All plugins are currently in the same binary package, qtwayland5. It contains: 1) /usr/lib/*/qt5/plugins/platforms/libqwayland*.so 2) /usr/lib/*/qt5/plugins/wayland-decoration-client/libbradient.so 3) /usr/lib/*/qt5/plugins/wayland-graphics-integration-client/*.so 4) /usr/lib/*/qt5/plugins/wayland-graphics-integration-server/*.so 5) /usr/lib/*/qt5/plugins/wayland-shell-integration/libivi-shell.so Can you please suggest us how to further split this package? Of these file groups, only 4) adds a dependency on libqt5waylandcompositor5. Will splitting it into a separate package be enough? -- Dmitry Shachnev
Attachment:
signature.asc
Description: PGP signature