I never had this problem in Fedora. Doesn't Slackware come with latest program dependiencies installed? I had no problem with Fedora. What do I need to do? I understand the GLIBC part, but what is the other stuff I need?

well...with Slackware you do not really use rpm prog.'s
can't you compile it from source ?

...or maybe find a Slack-package for it.

egag

Slackware is not Fedora. RPMs are not its native package format, and consequently, Slackware does not have an RPM database and therefore cannot handle the dependencies. You must either:

1) Get hold of the program in *.tgz form
2) Compile from source
3) Use rpm2tgz to convert the RPM to a Slackware package
4) Install the rpm with '--nodeps'

Having looked at the LimeWire website, 1 & 2 are out (but keep in mind for future reference). Therefore, I would go with 3 - convert the rpm to a tgz package using rpm2tgz, then install (using the command 'installpkg') the tgz file.

Thanks. I got it to work with rpm2tgz. I thought Slackware didn't come with any dependencies because of the first problem, but now I know it is loaded. Anyways, can I do this with Openoffice also? I want to install the 2.0 beta, can I do that rpm2tgz?

A better idea for openoffice would be to use the premade Slackware 10.1 package available from LinuxPackages.net, if you do use rpm2tgz from all the RPM's you download from openoffice.org I believe you need to delete the 2 menu packages for RH and SuSE and then also do a few more modifications and symbolic links to get OO2 Beta working.
http://www.linuxpackages.net/search_...ffice&ver=10.1

You're more than welcome to compile LimeWire from source, if you're into that kind of thing. Instructions are at http://www.limewire.org

You really need to get in the habit of using available slackware packages instead of rpms as this will save you from future headaches.

It's always a good idea to use the package system designed for the distro you're using.

I have an even better idea- install everything from source, that will save you so many problems, it's not even funny, it is also much easier to install than some stupid RPMs or packages, just an advice from me- install checkinstall and then all you have to do is
./configure
make
checkinstall

and you can uninstall using pkgtool, as a matter of fact checkinstall will tell you how to uninstall after installation. Install Open Office from source, I didn't have any problems whatsoever.

Well, installing from sources is not always that easy I think. I am not too deep in Linux, and particularly Slackware(learning fast, though ), so sometimes I can't handle errors given after ./configure script, or some things happen which I don't understand. Example? I compiled arts from sources "just for fun", and i had fun indeed; didn't work, so I fell back to the original Slackware pack I had..
BTW, is that openoffice....tgz package faster than the normal "distro-independent" one?

I can't compare between the tgz package on slack and the distro independent package on slack, because I have only installed it from source on slack. But it seems like my OpenOffice runs faster on slack than any other distro, so I can't tell if it's from the distribution, or because it is compiled from source. There is a difference though. My OpenOffice used to run slower on FC and SuSe, where I used packages.

I use the installation files from openoffice.org, Slack starts it a little bit faster than SuSE(which I used previously), but it still takes 12 seconds or more, after clicking on the button.

PS: I didn't want to open a topic just for this, should I??