Preferred method of package management and software installation?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
View Poll Results: What methods do you use to install, update and maintain packages and sodtware in Slackware?
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.
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.
...Some people use slackrepo to manage their SlackBuilds, which is a very powerful tool but has a bit steeper learning curve and has features that might be overkill for the average user (e.g., to build a complete repo of binary packages that can then be accessed via slackpkg+).
This is how I'm spending this weekend . Thanks for the tip. I had seen it mentioned before but was put off by the 2015 date.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.