https://bugs.kde.org/show_bug.cgi?id=361954
--- Comment #8 from Sebastian Kügler <se...@kde.org> --- Thanks for educating me about whole point of my work and my aim of participating in KDE. :-D I don't know how "KDE's sponsored purpose as a showcase for Qt" is to be understood or where you're coming from with this, but let's concentrate on technical rather than philosophical or academical topics. I'm speaking as maintainer (so bug-wrangler and developer). These roles cannot be split, or at least we don't have people who just triage bugs. In practice, it's the developers having to shoulder this work as well as development. (Your help is welcome here.) In the end it all boils down to a resources available versus complexity. A higher degree of complexity means more possible cases to investigate, which in turn means more resources needed to deal with this complexity. We've made a conscious decision to not support building libkscreen without Wayland support for these reasons. That said, from a cursory glance, your patch looks like the way I'd do it as well. I just don't want it upstream, and I won't spend any effort supporting your patched version of libkscreen. Please clearly mark your patched version as such to avoid confusion. -- You are receiving this mail because: You are watching all bug changes.
