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.
The slackpkg tool is for administering the official portion of your Slackware install. All dependencies are met within the recommended full install. I do not see a use case.
I forgot about the old slackware 'if you don't do a full install you're on your own' and I have a fairly basic install here. I'm sure a lot of people these days though skip kde* on install and just run with xfce or if you were maybe resurrecting an old pc or laptop and wanted to run with just fluxbox or something. Maybe it would help but I'm not a coder so maybe it is too difficult or too much work which is fair enough and I understand that.
Not sure how sbopkg do it, obviously it's a lot different to slackpkg and running from different packages in a different repository, but if I do:
I forgot about the old slackware 'if you don't do a full install you're on your own' and I have a fairly basic install here. I'm sure a lot of people these days though skip kde* on install and just run with xfce or if you were maybe resurrecting an old pc or laptop and wanted to run with just fluxbox or something. Maybe it would help but I'm not a coder so maybe it is too difficult or too much work which is fair enough and I understand that.
Not sure how sbopkg do it, obviously it's a lot different to slackpkg and running from different packages in a different repository, but if I do:
sbopkg -s <packagename>
it's all there.
There's metadata associated with each slackbuild that has that information in it. It's the package_name.info file, which contains something like (taking 14.1's libvirt SlackBuild as an example):
If you really want that functionality, then you should consider using slapt-get as well as one of the slapt-get repositories where someone's done that analysis for a standard slackware distribution. Like this one (look at the contents of PACKAGES.TXT at the link).
That will work in a majority of the cases (probably a vast majority of them).
If you need something that isn't binary from another package, you're pretty much stuck with someone documenting that fact in some location that a program can read and understand. Data files for games and python/perl/scheme/ruby/whatever scripts come to mind.
According to Matteo Rossini (zerouno, on Alien BOB's blog), the following works with some third party repositories using slackpkg+:
Quote:
slackpkg+, as slackpkg, does not have the dependency support, but some repository (as slacky and other) contains that information in metadata and slackpkg store that information in its database. So by typing “slackpkg info pkgname” you can see what package you must also install.
Also, there is slackyd, though I haven't tested it.
I forgot about the old slackware 'if you don't do a full install you're on your own' and I have a fairly basic install here. I'm sure a lot of people these days though skip kde* on install and just run with xfce or if you were maybe resurrecting an old pc or laptop and wanted to run with just fluxbox or something. <snip>
Why not follow the recommended procedure? Why not install KDE even if you plan to use Xfce as your WM? What do you hope to gain by a basic install except hard drive space?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.