Hi everybody.

Just a simple question: Can I use rpm packages with Slackware?

You can use the "rpm2tgz" utility that comes with Slackware, but it's probably better to find a Slackpkg (not too common) or the source code for the program (almost always available).

Thanks jrdioko.

The main reason I ask is that I'm having problems with Mandrake and I'm thinking of changing distros to Slackware/SUSE and I've got a lot of rpms (for things like Celesia, some games, like prboom etc.

Any suggestions?

I believe SUSE has its own packaging system so I'm not sure how it would work for that. For Slackware, I have had some luck with rpm2tgz and it's worth a try (it's just not 100% effective). It might take some time to redownload everything, but most applications do provide source code and it's not that difficult to install that way once you get used to the process. In fact, that's one of the things I like best about Slackware. I install almost everything from source which gives me control and shows me exactly what's being done, and then use checkinstall instead of make install so that it is installed as a package that can easily be viewed and removed.

Welcome to LQ. If you are interested in finding a specific package for Slackware, *definitely* bookmark LinuxPackages -- J.W.

As well as rpm2tgz, you can install rpm as well although it is "unsupported".

tools like rpm2tgz and alien are great as last-ditch alternatives. The situation I have used them in is where someone provides a binary RPM, and no source code. In any other case, there is always a better alternative.

In other words, converting all your old RPMs to TGZs and trying to use them in slack is going to be a mess. Truthfully, even taking them into a distro like Red Hat or SuSE which natively uses RPMs would be messy too.

Chances are good that you will find slack packages if what you need, especially at linuxpackages.net. If not, in almost all cases you can find source. Its really not as hard as you might think to compile from source, and truth be told, you'll need to learn eventually. They usually come with instructions. I reccomend using the tool "checkinstall" which i believe is in slackware /testing or /extra when compiling from source, as it makes for a cleaner system...which means its easier for you to remove things later

HI again.

Had a look at all the rpms/stuff I downloaded. A lot of it (~75%) is source code and of the rest I seem to remember that the source is available.

Any other tips, like on installation/cofiguration?

I have, at one time, had both Mandrake and Slackware installed, on different partitions, and seem to remember that I couldn't get the sound, samba or LAN to work properly. Also, It apparently didn't see the DVD drive.

Regards
k

Hi
Tell me, would I have to recompile the kernel to use "checkinstall"?

I don't think so

Hi mrcheeks.
If I don't have to recompile the kernel, then how do I make use if it? I tried "checkinstall" in bash and bash couldn't find it.
k

No need to recompile the kernel unless you're making major changes. To use checkinstall you just need to download and install it like any other program.

http://asic-linux.com.mx/~izto/checkinstall/

I'd recommend using the checkinstall from a slackware mirror, the other one will work, but I've found at least in my exp. it seems to sometimes screw up the symlinks created during install, also the one from the slackware mirror has been modified to only make slackware packages:

http://slackware.cs.utah.edu/slackwa.../checkinstall/

thanks.
will give it a try.

I had no idea there was a different version. Time for me to update I guess.