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.
Well, the title says it all.
I have no problem with resolving dependencies on my own, but when I uninstall a programm, how could I keep track of the dependencies, thus remove them?
Is there a possibility to store this information in the /var/log/packages files, or better yet, is it possible to include the dependencies in the the .tgz's, so a 'removepkg' would get rid of them as well?
In Debian the program is called deborphan, this is not possible with Slackware because there is no dependency database. SalixOS which is compatible with Slackware lists all of the dependencies for both their own and Slackware packages.
Packaging the dependencies with the package is not a good idea, as a dependency may be required for multiple packages, and if you removed one of these mega bundles you would break several others, there is also the risk of dependency hell where different versions of an essential program are required by different programs. They try to replace each other and therefor at least one program can never work, or worse your entire system dies.
There was and probably still is (see slacky.eu) a utilitiy called slackdeptrack that displays all dependencies of all ELF executables and libraries by walking through your filesystem so it is, or at least was, possible to figure out packages no other package depends on. It was several years ago I played with this tool so I cann't guarantee or even recommend it because I don't know its current state. I simply did not need such feature ever.
slackdeptracj still works fine. But, it shows you the packages needed by each package -not the 'reverse' depends( list of all packages which depend on a package)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.