Chapter 2. Packaging Software Collections

When creating a new Software Collection for your application:

Create a Software Collection metapackage

Each Software Collection includes a metapackage, which installs a subset of the Software Collection's packages that are essential for the user to perform most common tasks with the Software Collection. See Section 2.7.1, “Metapackage” for more information on creating metapackages.

Consider specifying the location of the Software Collection root directory

You are advised to specify the location of the Software Collection root directory by setting the %_scl_prefix macro in the Software Collection spec file. For more information, see Section 2.3, “The Software Collection Root Directory”.

Consider prefixing the name of your Software Collection packages

You are advised to prefix the name of your Software Collection packages with the vendor and Software Collection's name. For more information, see Section 2.4, “The Software Collection Prefix”.

Specify all Software Collections and other packages required by your application as dependencies

Ensure that all Software Collections and other packages required by your application are specified as dependencies of your Software Collection. For more information, see Section 2.10.8, “Making a Software Collection Depend on Another Software Collection”.

Convert existing conventional packages or create new Software Collection packages

Ensure that all macros in your Software Collection package spec files use conditionals. See Section 2.10, “Converting a Conventional Spec File” for more information on how to convert an existing package spec file.

Build your Software Collection

After you create the Software Collection metapackage and convert or create packages for your Software Collection, you can build the Software Collection with the rpmbuild utility. For more information, see Section 2.12, “Building a Software Collection”.