Slackware’s package manager is extremely easy to use:
slackpkg upgrade-all upgrades all installed packages slackpkg install-new installs all packages that were added to the repo slackpkg clean-system uninstalls all packages that were removed from the repo
It’s Slackware’s approach to dependency resolution. You don’t need to resolve dependencies on your system if you just install every package in the repo.
The installed size is under 15 GB, and you get a system that works equally well for a desktop as for a server with lots of app choices out of the box.
(Throwing the kitchen sink at you was the common way to install Linux in the old days, before quick Internet)
Slackware’s package manager is extremely easy to use:
slackpkg upgrade-allupgrades all installed packagesslackpkg install-newinstalls all packages that were added to the reposlackpkg clean-systemuninstalls all packages that were removed from the repoAnd that’s all.
That reads easy but what’s with installing all packages that were added to a repo? How does that help anything?
It’s Slackware’s approach to dependency resolution. You don’t need to resolve dependencies on your system if you just install every package in the repo.
The installed size is under 15 GB, and you get a system that works equally well for a desktop as for a server with lots of app choices out of the box.
(Throwing the kitchen sink at you was the common way to install Linux in the old days, before quick Internet)
That’s a horrendous approach since probably two decades. They shouldn’t slack so hard.