[SOLVED] Any difference in rpm package of different distributions?
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Any difference in rpm package of different distributions?
Is there any difference between rpm packages used in different distributions like red hat, centOS, openSuse, fedora, pcLinuxOS, mageia, mandriva etc? Can rpm used in one of these distributions be used in other distributions also? I checked on the net and at some places it is mentioned that they are essentially identical, while others say one cannot use rpm of one distribution in another. Thanks for your answers.
I checked on the net and at some places it is mentioned that they are essentially identical, while others say one cannot use rpm of one distribution in another.
Since we have no examples it's hard to say in what context what was said and the knowledge of those that posted their comments.
I've done it, but the process can be complex. The rpm metadata will contain a list of dependencies, but this won't be a list of actual libraries: it will be a list of the packages on that distro which contain those libraries, and they will be differently named in different distros.
To give you an example, I have one old Windows program which I need, which is very fussy about which version of Wine it will run with. CentOS had an unacceptable one, so I needed an acceptable one from the same year, so that the dependency versions would be the same. I got another distro's rpm and it couldn't install because of unmet dependencies. So I gave the command to install the CentOS version, made a note of its missing dependencies, aborted the install, and installed the dependencies. Then I installed the wine.rpm with the "--no-deps" option. See what I mean? If this computer were bigger and faster, it would have been quicker to compile the source code.
Getting the .src.rpm and compiling it (on a non-Production machine obviously) for the distro + release in question also enables you to satisfy dependencies and address distro-specific paths or scripts (and ideally give back results to the community).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.