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.
Hi, I just don't understand why isn't a tool that can manage dependencies issues.
Swaret, pkgtool, slapt-get, are fine, but, they don't manage dependencies, or they do?
Isn't in Slackware that kind of tool ???
I'm confused about it.
Slackware's pkgtool doesn't check dependencies. It supposed to be for more control, so you can install stuff in any order, or something.
But swaret and slapt-get do. When you install or upgrade they will do a dependency check. Or you can just run "swaret --dep" (not sure what it is for slapt-get) to check.
Slackware is intentionally designed by Pat V. to do no dependency checking. It would appear that the dependency checking done by swaret is sort of half assed, just look at the recent problems upgrading gnome and yes I know you were able to get around the problems. But look at past problems with elflib -> aaaelflibs and other examples. Pat and most old time Slackers look at that as a feature of Slackware though. Each user is assumed to be knowledgeable enough to manage his own system. If you have ever used other distros that position should be understandable. There is RPM Hell for the RPM based distros. The Debian based distros can run into their own broken package, unmet dependency problems. In any system, you will have apps that simply will not work on your system and no amount of dependency checking will change that. Usually when you build a package or try to run it the error messages are clear and will tell you what dependency needs to be added. You can also use ldd to check what other packages you might need.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.