Product SiteDocumentation Site

Chapter 2. Packaging Software Collections

2.1. Creating Your Own Software Collections
2.2. The File System Hierarchy
2.3. The Software Collection Root Directory
2.4. The Software Collection Prefix
2.5. Software Collection Package Names
2.6. Software Collection Scriptlets
2.7. Package Layout
2.7.1. Metapackage
2.7.2. Creating a Metapackage
2.8. Software Collection Macros
2.8.1. Macros Specific to a Software Collection
2.8.2. Macros Not Specific to a Software Collection
2.9. Converting a Conventional Spec File
2.10. Uninstalling All Software Collection Directories
2.11. Making a Software Collection Depend on Another Software Collection
2.12. Building a Software Collection
2.12.1. Rebuilding a Software Collection without build Subpackages
This chapter introduces you to packaging Software Collections.

2.1. Creating Your Own Software Collections

In general, you can use one of the following two approaches to deploy an application that depends on an existing Software Collection:
  • install all required Software Collections and packages manually and then deploy your application, or
  • create a new Software Collection for your application.
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.11, “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.9, “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”.