Chapter 4. Extending Red Hat Software Collections

Procedure 4.2. Using your own scldevel subpackage in a dependent Software Collection

1. Consider adding the following at the beginning of the metapackage's spec file:

   %{!?scl_ruby:%global scl_ruby ruby200}
   %{!?scl_prefix_ruby:%global scl_prefix_ruby %{scl_ruby}-}

   Copy to Clipboard Toggle word wrap
   These two lines are optional. They are only meant as a visual hint that the dependent Software Collection has been designed to depend on the ruby200 Software Collection. If there is no other scldevel subpackage available in the build root, then the ruby200-scldevel subpackage is used as a build requirement.
   You can substitute these lines with the following line:

   %{?scl_prefix_ruby}

   Copy to Clipboard Toggle word wrap
2. Add the following build requirement to the metapackage:

   BuildRequires: %{scl_prefix_ruby}scldevel

   Copy to Clipboard Toggle word wrap
   By specifying this build requirement, you ensure that the scldevel subpackage is in the build root and that the default values are not in use. Omitting this package could result in broken requires at the subsequent packages' build time.
3. Ensure that the %package runtime part of the metapackage's spec file includes the following lines:

   %package runtime
   Summary: Package that handles %scl Software Collection.
   Requires: scl-utils
   Requires: %{scl_prefix_ruby}runtime

   Copy to Clipboard Toggle word wrap
4. Ensure that the %package build part of the metapackage's spec file includes the following lines:

   %package build
   Summary: Package shipping basic build configuration
   Requires: %{scl_prefix_ruby}scldevel

   Copy to Clipboard Toggle word wrap
   Specifying Requires: %{scl_prefix_ruby}scldevel ensures that macros are available in all packages of the Software Collection.