Red HatThis forum is for the discussion of Red Hat 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.
We have an RPM here we create here for RedHat 8 that we'd like to use on RHEL4 as well. Everything's worked great except for the compat-libstdc++ dependency in the spec file:
Requires: compat-libstdc++
It looks like the package was renamed for RHEL4 (the files from the RH8 compat-libstdc++ package are installed by compat-libstdc++-296-2.96-132.7.2 in RHEL4). Is there any way I can change the dependency to work with both? Or is it at all possible to fix this without having to create two separate spec files? Thanks in advance for any advice on this.
Sorry, I missed the part where you said you want the rpm to work on both distros. The only possible solution that I can see is to build two separate rpms, one for each distro.
Don't put such hardcoded dependencies on package names into your spec files. Instead, let rpm-build do its job. It creates automatic dependencies on libraries by examining executable files in the buildroot. For your software you should see automatic dependencies on the needed library sonames, which is tons better than hardcoding package names.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.