How to build SCL enabled packages

Latest response

Hi,

I'm trying to make it possible to build the same *.spec as SCL and as a conventional package. I have a meta package and a bunch of "dependencies" which I converted from conventional spec files. There is no problem when I try to build it as SCL package (as described here: https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/1/html-single/Software_Collections_Guide/#sect-Building_a_Software_Collection_Locally), but I still want to build it as a conventional (i.e. not defining scl at build time).

Also I have other SCLs installed in my system (rh-python34 for example)... So when I build a conventional package %scl macro gets defined anyway! And it came from /etc/rpm/macros.rh-python34-config which defines it to rh-python34... After build my "conventional" package named w/ rh-python34 prefix and installed to just another (random) SCL instead :(

Any hint how can I build a really conventional package?

Responses

Hi Alex,

I'm not sure I understand the problem correctly. I don't think you can use the same specfile for both an SCL and a regular package -- the SCL-specific tags and macros should define the name, the paths, etc. to conform to SCL guidelines. The point of an SCL is to make sure it doesn't conflict with the rest of the system (i.e. the parts installed by regular packages).

Please, use the latest version of the Packaging Guide, which is available from https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/2/html-single/Packaging_Guide.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.