What are the steps to build and install a Slackware package from a RPM package?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I know about sbopkg. But I want to be able to install manually from RPM packages.
There is a near 100% chance you do not want to do this. RPM's are not made for slackware.
You can not install just any old RPM and have it work and there is a good chance you would
also break your slackware install. There are a few 3rd party applications that are distributed
in RPM as sort of a universal package but even these need special care to integrate with
slackware.
In my view it would be better to build a package using a slackbuild because you should make a slack-desc and might need a doinst.sh. You can look at the open office slackbuild on sbo for an idea: http://slackbuilds.org/slackbuilds/1...org.SlackBuild
The conversion bits:
Code:
for FILE in *.rpm ; do rpm2cpio < $FILE | cpio -imdv ; done
mv opt usr $PKG
Distribution: Linux Mint 11 (Katya), Slackware 13.1, Slackware 13.37
Posts: 30
Original Poster
Rep:
Quote:
Originally Posted by XGizzmo
There is a near 100% chance you do not want to do this. RPM's are not made for slackware.
You can not install just any old RPM and have it work and there is a good chance you would
also break your slackware install. There are a few 3rd party applications that are distributed
in RPM as sort of a universal package but even these need special care to integrate with
slackware.
Assuming that you cannot find a slackbuild for your package, put rpm package in its own directory and cd to that directory, then
Code:
rpm2cpio package.rpm | cpio -vidm
Then inspect the contents of the folder to make sure it is compatible with slackware's layout: binaries are in /usr/bin , libraries in /usr/lib or /usr/lib64, startup configurations in /etc/rc.d, and so forth. If it seems like it's compatible go ahead and use makepkg to create a slackware package , and then installpkg to install it... the beautiful thing about slackware packages, is you can use removepkg to remove it if it doesn't work or somehow breaks the system, unless it breaks system so much that you can no longer use the pkgtools, in which case you boot from the install media, and mount your file system(s) and then use removepkg from the startup media with the ROOT=/mountpointofyourfilesystem to remove the package...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.