Hi, it's now public knowledge that Patrick Volkerding has shot down the age verification nonsense that's been getting a lot of attention in not just GNU/Linux, but FLOSS (e.g. OpenBSD, Haiku) in general. Does this automatically apply to downstream distros like Salix and Slackel? If not, could it be ...

I can see your point. At least CSD isn't an issue that I've seen. I miss the traditional look and feel of GTK2 themes, but using one with adequate GTK3 and Qt5 support is better than nothing. Won't be happy at all once GTK4 comes for us all. As for Elogind, simply not having it running (ConsoleKit2 ...

I spent the last two hours chasing down specific source versions of Xfce that I thought were on the right track, but eventual library conflicts within the system were creeping up, making it very unusable in the end. Good thing I made a system backup right before that.

On a slightly unrelated note ...

Nice to see newer kernels being maintained for this release.

You can build a package.
Download all from here in a folder consolekit2.
Enter the folder and type
fakeroot sh ConsoleKit2.SlackBuild
install the package
sudo spkg /tmp/ConsoleKit2-1.0.0-x86_64-3.txz
Just wanting to update you on that. I only needed to install one package:
linuxdoc-tools ...

Thanks. I'm currently having limited Internet, but the files have been downloaded for offline experimentation. I will update this thread as soon as possible. Thanks again.

Not even with a "dummy" package for a build workaround? A few other distros have that, and I was able to get ConsoleKit2 and Seatd working splendidly with software like KDE and Network Manager. Perhaps I'll do a reinstall of Salix 14.2 and try to exclude Elogind and the rest of them as much as ...

Is there a way I can do that and still keep Xfce? I am aware that Salix 15.0 follows Slackware's decision to drop ConsoleKit2 in favor of Elogind, plus adding more Wayland and other Freedesktop.org components in the dependencies. I would simply like to omit those kinds of things, if it's possible to ...

No, Salix should not use Debian at all. If I want Debian, I'll use Debian (or Devuan in this case, because I don't like Systemd or other Poetteringware in general). What I like about Salix is that I get an even more old school GNU/Linux experience than Debian, due to being more Unix-like and ...

My limited Slackware experience tells me this is a very bad idea. As has been said, Salix's repositories handle dependency tracking to mitigate breakages.

I think that as long as you know what you're doing (i.e. installing very specific software versions you can't find on official repositories that ...