I'd prefer to vote for pkgtools as the Main, and slackpkg as a sometimes adjunct since slackpkg is the database and gathering tool, not the package management engine and I still do base manual installs gathering my own from slackbuilds.org as well as making my own packages from source. I know the perceived bloat bothers Mr. Torvalds, but I have 2 appimages that I don't hate.
|
What I like the most with slackpkg is the track of new config files. From time to time (or on the build vm) I do use clean-system as well.
Otherwise, what fit my needs is to keep a local mirror up to date an use basic pkgtools. Third party is with sbopkg. |
Full install of Slackware, plus
Code:
sqg Code:
sbopkg -kRqi |
You also forgot pkgsrc and Flatpak.
Dependency management has not been a problem on Slackware for many years, but dependency hell remains a problem on other platforms. Try removing just Evolution from Debian or OpenSUSE, for example, and see for yourself how many hundreds of "dependencies" they kindly offer to remove for you. |
slackpkg to keep slackware updated and sbotools for slackbuilds
|
Quote:
|
Quote:
|
Quote:
https://slackbuilds.org/repository/1...tem/slackrepo/ that's how I set it up before: https://slackalaxy.com/2018/09/09/ow...es-repository/ hope that's useful |
When I was still using Slackware, it was sbotools.
|
Quote:
|
All times are GMT -5. The time now is 07:41 AM. |