>>860968
By the way, the package manager supports templates, and sbopkg supports queuefiles.
Which it can also generate for you for packages that don't have a queue already, with a tool, based on the readmes, which usually have a "requires" section.
This means you can set up your dream setup once and then just use the template to replicate it on any slackware computer, provided the packages are in the repo.
Which you can make yourself, easily since it's basically just a directory with some infos in it.
Making your own packages is also super easy, and if you're that advanced then you've most likely got experience with compiling programs and whatnot, and you need to "manually resolve" dependencies for those, too.
Even if that involves apt-getting them, or something.
In other words.
If I wrote some really cool piece of software you want to use, and it's not in your "automatic dependency resolving repository" because it's new.
Then, you, too, need to resolve the dependencies for my piece of software, unless you want to use prebuilt binaries that have things I decided to include.
Which can be annoying if you have a different taste.
In any case, just install the fucking base repo in full and omit shit you really don't want to use, in my case emacs and some other things.
Then save a template.
Go from there.
Also, this "big hammer" approach actually got me into Linux proper.
Why?
Because after a full install I had so many programs to try out I wouldn't even have known to "install on my dependency resolving distro" because I flat out didn't know about it.
But Slackware had it all.
A freaking playground with awesome shit, both retro and modern and it all worked and the tools and init scripts were all plaintext and everything.
I had a fucking field day exploring Linux thanks to Slackware.
It's great and I pity the fools who use something else.
I will continue using it forever unless something better comes along, and I doubt that.
Just like I am keeping an old build of Firefox alive so I can continue using Pentadactyl.
Maybe qutebrowser will some day be good enough to replace that, but that day is not today.
Anyway. Give slack a try, in a vm or something.
It's fun and it has the potential to grow on you, if you like Linux.
It also has little easter eggs here and there and it handles configurations sensibly and it's awesome.
Also, people use software more than they install it.
It's not like you fuck with packages every damn day.