[KScreen] [Bug 361954] Make kwayland backend optional

2016-06-01 Thread Martin Gräßlin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 Martin Gräßlin changed: What|Removed |Added Resolution|--- |WONTFIX

[KScreen] [Bug 361954] Make kwayland backend optional

2016-05-30 Thread Luke-Jr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 Luke-Jr changed: What|Removed |Added Resolution|WONTFIX |---

[KScreen] [Bug 361954] Make kwayland backend optional

2016-05-30 Thread Sebastian Kügler via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |n...@kde.org -- You are

[KScreen] [Bug 361954] Make kwayland backend optional

2016-05-30 Thread Sebastian Kügler via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #15 from Sebastian Kügler --- @Jeremy Please note that there's no Wayland protocol "running" in an X11 session. This backend is loaded at runtime under specific conditions, namely when you run a Wayland session. Nothing of

[KScreen] [Bug 361954] Make kwayland backend optional

2016-05-29 Thread Jeremy Andrews via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 Jeremy Andrews changed: What|Removed |Added CC|

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-22 Thread steveL via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #13 from steveL --- (In reply to Martin Gräßlin from comment #11) > Please note that KWayland is a library, it does not mean that you have to > run Wayland. If you want to switch the desktop environment because

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-22 Thread steveL via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #12 from steveL --- (In reply to Sebastian Kügler from comment #8) > Thanks for educating me about whole point of my work and my aim of > participating in KDE. :-D Eh? Who said anything _at_all_ about *your*

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-21 Thread Martin Gräßlin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #11 from Martin Gräßlin --- > If KWin/Plasma 5 will require KWayland Things which require KWayland as of today: * mandatory in kscreenlocker - used for private communication between the daemon and the greeter *

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-20 Thread Luke-Jr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #10 from Luke-Jr --- In my case, I still run KDE 4, with a few KF5-based applications. If KWin/Plasma 5 will require KWayland, I will probably switch to LXQt when KDE 4 ceases to be viable. LXQt, however, still

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-20 Thread Sebastian Kügler via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #9 from Sebastian Kügler --- By the way, out of interest: why do you want libkscreen sans wayland? Kwin and plasma-workspace depend on KWayland as well, so you'll need Kwayland anyway to build Plasma, or are you also going to

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-20 Thread Sebastian Kügler via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #8 from Sebastian Kügler --- 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

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-20 Thread steveL via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 steveL changed: What|Removed |Added CC|

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-19 Thread Luke-Jr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #6 from Luke-Jr --- Quite a few distros are source-based now. -- You are receiving this mail because: You are watching all bug changes.

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-19 Thread Sebastian Kügler via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #5 from Sebastian Kügler --- The split would have to be done in the binary packages, only. -- You are receiving this mail because: You are watching all bug changes.

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-19 Thread Luke-Jr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #4 from Luke-Jr --- I don't understand your final sentence. It doesn't look like the build system currently supports splitting the backends into different packages: it always wants to build them together. --

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-19 Thread Sebastian Kügler via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #3 from Sebastian Kügler --- Well, in the end, those that have to do the work have to make this decision, and that's (among others), me. We take these decisions based on priorities and past experience. When looking at the

[KScreen] [Bug 361954] Make kwayland backend optional

2016-04-19 Thread Luke-Jr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361954 --- Comment #2 from Luke-Jr --- It increases complexity far more to force end users and/or distros to do it on their own instead... -- You are receiving this mail because: You are watching all bug changes.