Show Table of Contents
2.10.8. Making a Software Collection Depend on Another Software Collection
To make one Software Collection depend on a package from another Software Collection, you need to adjust the
BuildRequires and Requires tags in the dependent Software Collection's spec file so that these tags properly define the dependency.
For example, to define dependencies on two Software Collections named software_collection_1 and software_collection_2, add the following three lines to your application's spec file:
BuildRequires: scl-utils-build Requires: %scl_require software_collection_1 Requires: %scl_require software_collection_2
Ensure that the spec file also contains the
%scl_package macro in front of the spec file preamble, for example:
%{?scl:%scl_package less}
Note that the
%scl_package macro must be included in every spec file of your Software Collection.
You can also use the
%scl_require_package macro to define dependencies on a particular package from a specific Software Collection, as in the following example:
BuildRequires: scl-utils-build Requires: %scl_require_package software_collection_1 package_name
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.