Even more annoying, as KDE5 relates to Wayland,beastDemian said:Plasma 5 was just released. There are barely a few Linux distros that have packages available.
PC-BSD's area 51 repositroy shows that we are at least up to version 4.13 ( http://src.mouf.net/area51/browse/trunk/area51/KDE ). I'd love to see KDE5, though, but it requires a bunch of QT5 stuff. I don't know how far from it are we.
https://plus.google.com/u/0/+MartinGr%C ... w31EE21BXVBreaking News: kwin_wayland will hard runtime depend on logind
Personally, I'm just waiting for PC-BSD's Lumina to mature a bit, I'm glad there is going to be a BSD-centric Qt DE outside of KDE going forward.For Slackware (which will not adopt systemd for as long as we can avoid it) this would mean that we will not support KDE under Wayland. I mean, it would not be sensible to run another window manager in KDE. We could just as well switch to LXQT then.
Note that I do not have any issue with Wayland, but it is also not part of Slackware. If the KWin team can avoid adding a hard dep on systemd components for their X11 libraries then that would be good news.
Personally, I'm just waiting for PC-BSD's Lumina to mature a bit, I'm glad there is going to be a BSD-centric Qt DE outside of KDE going forward.
retrogamer said:Even more annoying, as KDE5 relates to Wayland,https://plus.google.com/u/0/+MartinGr%C ... w31EE21BXVBreaking News: kwin_wayland will hard runtime depend on logind
Crivens said:Does anyone know what the reason for this is?
retrogamer said:It doesn't seem to be in doubt, Eric Hameleers from Slackware Linux says in the comments:
For Slackware (which will not adopt systemd for as long as we can avoid it) this would mean that we will not support KDE under Wayland. I mean, it would not be sensible to run another window manager in KDE. We could just as well switch to LXQT then.
Note that I do not have any issue with Wayland, but it is also not part of Slackware. If the KWin team can avoid adding a hard dep on systemd components for their X11 libraries then that would be good news.
retrogamer said:Personally, I'm just waiting for PC-BSD's Lumina to mature a bit, I'm glad there is going to be a BSD-centric Qt DE outside of KDE going forward.
https://plus.google.com/+MartinGr%C3%A4%C3%9Flin/postsAlthough the post is tabloid style it carried quite some information. I explicitly restricted to kwin_wayland. This implies that kwin_x11 is not affected. It also doesn't mean anything for other KDE software or Plasma. It's just kwin_wayland.
Second of all it says "runtime depend on logind". Notice that it doesn't say systemd, it's logind. And runtime depend indicates that it's only interacting with the DBus interface provided by logind. I don't understand how people could think that this means systemd as an init system is demanded given that there is a large distribution using logind without systemd.
Now why does kwin_wayland need to use logind's dbus interfaces? It's quite simple: I started integrating libinput into kwin_wayland and run into the obvious problem that one needs to be privileged to open the input devices. Running kwin_wayland with suid bit is a no-option, going to complicated wrappers is a no-option. Logind on the other hand allows the session controller to take a device and opens it for the session controller and returns the file descriptor. In addition it notifies whether the session is active. This is exactly what we need: it manages the device files in a secure way and we get notified when we need to suspend/resume the device files.
Obviously the required dbus interface could easily be provided without requiring logoind. I myself implemented a fake logind service for unit tests in the screen locker daemon and I will move that fake logind also to kwin to properly unit test that code. So this is possible.
And now how important is the dependency. Well I called it a "hard runtime dependency" which means that I consider kwin_wayland to have deficits if not used. Nevertheless the complete code is in an ifdef section (libinput is an optional build dependency) and there is even a command line option to disable libinput in kwin_wayland. kwin_x11 does not even try to use it. But yes if you want to use kwin_wayland in a Wayland session you will only get the full experience with libinput and the required logind integration used in KWin's libinput module.
The solution I picked will work for the large majority of our user base without introducing security risks. If there are other solutions which would provide us the same I'm happy to take patches, though I'm not interested in complicating the code base.
phoenix said:If you actually read Martin's G+ thread about that post, you'd see that he's just trolling people. There aren't any hard dependencies on systemd in KWin 5.
beastDemian said:phoenix said:If you actually read Martin's G+ thread about that post, you'd see that he's just trolling people. There aren't any hard dependencies on systemd in KWin 5.
There is a dependency on logind, which is a part of systemd.
http://www.freedesktop.org/wiki/Softwar ... md/logind/
I don't know how much it does matter to us anyway, since we would have to code arround whatever linux-specific solution they ended up going with.
phoenix said:Ah, but they're not depending on systemd, they're using the logind d-bus interface, so anything that provides that interface will work. And he specifically mentions a distro doing just that: providing logind d-bus interface without having any systemd bit installed on the system.
Ask and you shall receive.Personally, I'd rather have a mature KDE4 with all the little corner-cases fixed, than start over with KDE5. KDE4 is pretty nice by itself, and I hear that 4.13 onward got rid of Nepomuk.
Woot!Ask and you shall receive.
(Why always porting things from the linux world? Why not develop a nice FreeBSD desktop environment so that they have to port it? )
Personally, I'd rather have a mature KDE4 with all the little corner-cases fixed, than start over with KDE5. KDE4 is pretty nice by itself, and I hear that 4.13 onward got rid of Nepomuk.
Not the hottest news any more, but I guess the howto on installing KF5 posted to kde-freebsd@kde.org might still be relevant enough to be posted here:
https://mail.kde.org/pipermail/kde-freebsd/2015-May/019248.html
http://area51.pcbsd.org/branches/Hi,
Is there any update for KDE Plasma 5 under FreeBSD? This KDE release looks cool really.
Thanks in advance