this post was submitted on 16 Oct 2023
208 points (97.3% liked)
Linux
48255 readers
463 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In practice, Slackware package management after installation works like Arch's AUR.
You install (or build) packages from a community-maintained repo and are officially supposed to do it manually and always read the build scripts and READMEs, but a helper with dependency resolution (slpkg) exists, works well and most people use it.
What do you use? What are some problems you have with Slackware?
I use slackpkg+ which is an addon to the default package manager that allows you to install packages from community and third-party repositories.
And sbopkg which gives you a TUI frontend to install Slackbuilds (Slackware-specific build scripts for building from source).
Neither offer dependency resolution, which I don't really need anyway.
Now that I know how Slackware works and what its quirks are, I don't really have any issues with it. But it's pretty hard to figure that out when you're coming from more modern distros. It throws curveballs at you, like not booting after a kernel upgrade if you forget to copy the new kernel to your EFI partition and recreate the initramfs.
Most online documentation is wildly out of date and googling is no help due to how few users there are.
It took a while till I figured out the README files that come preinstalled with the distro are actually the official, up-to-date documentation and very helpful, and also that the place where most users (including the maintainers and author of the distro) gather and answer questions is the linuxquestions.org forum.
How do you install packages without appropriate dependency resolution?
I didn't know about that. I should probably run it in a VM for a while before trying
You read the package's .dep file, which lists dependencies, add those to your install queue in the right order and then install the queue.
It's not as daunting as it sounds, since the default Slackware installation already includes most common dependencies.
The most dependencies I ever had to install for a package were 3. But if you need a lot of additional software with many dependencies, it's best to do it just once for installing slpkg and then let that tool deal with it.
Thanks. I'm probably going to install some software for IOT devices alongside the usual workstation stuff (vim, tmux, browsers, audio, git, htop, a WM with add-ons etc). I'll take a look at
slpkg.