https://bugs.kde.org/show_bug.cgi?id=499828
--- Comment #2 from Noah Davis <[email protected]> --- Thanks for providing a patch. I'm not sure if I want to use it though. I try to avoid optional dependencies in general for a few reasons: 1. To prevent users from installing it in a way that makes them think the software is buggy or missing features. This is most likely to happen with users of distros that like to split packages up or users of advanced distros (regardless of whether or not they are advanced users). While it is annoying for some users who don't need the feature that requires a dependency, I don't want users to wonder why a feature isn't there when they use Wayland. It is currently the default session type, so it's important to prevent that situation. 2. QML doesn't have anything like C preprocessor blocks. We'd need to let the frontend know at runtime whether or not the feature is available for the backend. We already do this for KPipeWire since we need to support X11 though, so this reason doesn't really apply to this request. You can try CMake text replacement, but that's not really the same and has limitations. 3. Simplicity. Having to write different logic in C preprocessor blocks can generate a lot of extra code and complexity sometimes. The extra complexity tends to only benefit a small number of users that could probably live with having to deal with another dependency. If it's a particularly large or difficult to work with dependency, I'd understand needing it to be optional though. 4. To prevent distros from packaging it in a way that is incorrect that leads to the scenario in reason 1. It's not that common, but it can happen and it generates bug reports for us. -- You are receiving this mail because: You are watching all bug changes.
