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.
I started in Linux using Red Hat. Now I use Fedora Core. Both have a tool called RPM for installing and upgrading packages. For example you can download all the KDE packages to a folder and then, install them all with just one command: 'rpm -ivh *.rpm". It also take cares about the dependencies issues.
Is in Slackware a tool like this?
How many tools does Slackware have?
I only know:
1. installpkg
2. pkgtool
3. swaret
4. slapt-get
I used pkgtool to install all the KDE packages manually one by one, but it didn't warn me about any dependency problem, I don't think that is right? Does pkgtool manage the dependency issues?
Which tool should I use to install them all and of course taking caring about the dependencies issues?
I'm having a lot of trouble with the depency problems right now. My sound doesn't work after upgrading to kde 3.2.2 from kde 3.1 for some reason or another even after checking dependencies. So either the new stuff just doesn't work with my relatively normal soundcard or it's missing something...
I find that It's usually a much bigger hassle to install anything with rpm than with the standard .tgz tarballs slack uses. The package will install. And when it won't run, it tells you what it's missing. You find out what package has that -- you install it. Kaboom, running app.
In red hat/rpm you can't even install it if dependencies aren't present. If you use the force option, or nodep, you can run into big problems down the line -- I've seen some rpm databases bunked up from a lot of forcing, and ignoring dependencies.
slapt-get and swaret do the apt-get type thing of downloading everything needed for dependencies and installing them.
how exactly can you figure out which package has the file you need though.. this is my problem atm with a few things.. actually I upgraded everything so I haven't had any dependency issues (this time) but last time I did and several apps wouldn't load because of gtk errors (I had the newest gtk, and searching lead me to something that said I needed the newest pango also).. I mean.. who would even know gtk and pango were connected... but anyway.. that didn't end up working either..
As far as I know, pkgtool and installpkg are the same tool. I only used them and it worked quite fine until now.
Aoh, another thing, I really think they should rename the Emerde project if it's not a fake, since "merde" means "shit" in French...
When you install a package:
-It works.
-It don't works, then, as you've launched it in a terminal, you can see a message like:
libXXXXX.yyy missing. So you have to install libXXXXX.yyy, or XXXXX.yyy.
When you run swaret, then it takes care of dependencies. You can have some trouble, but nothing compares to RPM's losses of hair.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.