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.
3.Changing .tar.gz extension to .tgz renaming the file, then
installpkg <name>.tgz
(this always create a folder in the root folder)
This is not the correct way to do this. You have to use installpkg, upgradepkg, removepkg, with Slackware or Slackware compatible packages not just ordinary tarred and gzipped bundles.
You should look for a package called sbopkg it makes compiling and installing Slackware packages easy.
Quote:
How do I find out if an application requires additional libraries?
Dependencies are normally listed in the documentation, but if they're not, run the program from the command line and read the error message. Then install that package and re-run the program. Carry this on until it works.
samac
WhiteWolf1776 type faster than samac, samac must drink less!
Oh, almost forgot to mention a kinda cool bit... sbopkg can do queue files and there are a ton of them. Just follow the site and once you see how easy, you can make your own. I have all my extra software in a custom queue file so when I need to build a new box it's as easy as install slackware, install sbopkg, run sbopkg with the queue file and go get some pizza.
Also, just as it will save you much headachs, su is not sudo... you don't have to su this and su that. you should "su -" (the - matters) then run any slackbuild scripts. Not doing this can cause problems. For a full writeup, read up on slackbuilds web site.
Last edited by WhiteWolf1776; 05-25-2011 at 05:40 PM.
Long story short, you could install binary packages from repos like slacky.eu or build them yourself using slackbuilds. Check out sbopkg, it's a cli interface to the aforementioned website and allows you to browse and install packages much faster and easier. It also supports queues - a list of packages to build - for the packages with more deps - which speed up the process significantly.
Very often the required dependencies are listed in the description of the program. Running the newly installed application from terminal and checking the input usually is informative enough to see what exactly is missing.
Also, if you want automatic dependency resolving, you could install slapt-get, although IMHO that would defeat the purpose of using Slack in the first place.
src2pkg works automagically on many downloaded source tarballs (or zips), and gives you the package management advantage (mostly: it shows in all package tools and lists, and can be uninstalled or upgraded cleanly)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.