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.
Thanks, but I think this is about Dependency Management. In which a program like YUM finds the dependencies and does them for you. My question is regarding "dependency Checking". To let you know what you have missing. That way you can find it and install it before running into problems.
Yes, ruario's article is a good article on this topic. My short version is: The only supported type of installation for Slackware is the full installation, in which dependency checking is simply pointless. If you don't want to install a full installation then it is up to you to do the work. Why should the distro maintainers be bothered with maintaining dependency information that is only needed for unsupported configurations?
Thanks, but I think this is about Dependency Management. In which a program like YUM finds the dependencies and does them for you. My question is regarding "dependency Checking". To let you know what you have missing. That way you can find it and install it before running into problems.
The question is why slackpkg doesn't do dependency tracking, not why Slackware doesn't do dependency tracking, right?
The answer is that slackpkg assumes a full install.
Yup, that was my initially distorted question. Thanks for bringing that up
However, programs and deps do get updated. So "rpm -q" personally makes more sense to me but no need to flame this one, as I understand the reasoning behind the "KISS" slackpkg approach from what I have read so far. So I respect the reasoning/philosophy behind why. Also as Ruario wrote in his blog that rpm doesnt work well with other distros.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.