Does anyone know why #Slackware kernel went back to 5.15.117 from 5.15.118?

Also, the package itself seems messed up in subtle ways... 🤔

@ParadeGrotesque very pleased to learn that Slackware is still a Thing. That was my first Linux!

@DrHyde

It was my first Linux too. Somehow, I still use it to this day. Easiest thing to maintain when you need something that just works(tm).

@ParadeGrotesque I stopped using it when I found out that Redhat could resolve package dependencies. Later moved to Debian, and now to #Devuan because #systemd smells of poo. I assume that Slackware at least has package dependency management now?

@DrHyde

Nope, still no dependency management in the base system!

There is some dependency management in stuff like #sbopkg or (if you are a weird person like me) in runing #pkgsrc or #guix on #slackware ...

@ParadeGrotesque the idea of running #pkgsrc on Slackware just tickles me pink! I think I have to spin up a VM just to play with that!

@DrHyde

Works as advertised. One of my (long delayed) project was to make bulk build on Slackware, and provide a repos for Slackware users using 'pkgin'.

No, it's not coming out any time soon. 😔

@ParadeGrotesque @DrHyde I have pkgsrc-2023Q2 packages for Slackware ready be uploaded on my public repo. Not doing bulk builds as they would be too time/electricity consuming, but I have ~1000 packages for desktop use, which included several things not provided by the Slackware ISO (e.g. vlc, libreoffice, gimp, cutting-edge firefox, MPD, a lot of useful CLI utils, TUI programs and development-oriented stuff). Desktop environments are noticeably missing, as I'm using fvwm3