options for keeping -current with KDE4 (elogind+ConsoleKit2?)
by wirelessmc from LinuxQuestions.org on (#5CA1W)
I am maintaining two Slackware64-current installations on a new development box. On one of the installs I am fully current Slackware64 including KDE5/Plasma5.
On the other I still have KDE4 installed and wish to keep this system current running this window manager.
The other day I attempted a complete update on the KDE4 system, blacklisting KDE and elogind packages. I quickly learned this is a no-go since many important libraries (including X) are now linked against elogind libraries.
First question: Would it be possible to install elogind along side ConsoleKit2 and just not run it? i.e. make /etc/rc.d/rc.elogind non-executable?
Would this break other things like running the KDE4 window manager?
Thanks for any/all insights. It seems it was a big decision to move to KDE5 and it may no longer be possible to run KDE4 on a current Slackware OS.
On the other I still have KDE4 installed and wish to keep this system current running this window manager.
The other day I attempted a complete update on the KDE4 system, blacklisting KDE and elogind packages. I quickly learned this is a no-go since many important libraries (including X) are now linked against elogind libraries.
First question: Would it be possible to install elogind along side ConsoleKit2 and just not run it? i.e. make /etc/rc.d/rc.elogind non-executable?
Would this break other things like running the KDE4 window manager?
Thanks for any/all insights. It seems it was a big decision to move to KDE5 and it may no longer be possible to run KDE4 on a current Slackware OS.