Product SiteDocumentation Site

Chapter 3. Introducing Software Collections

3.1. What Are Software Collections
3.2. File System Hierarchy
3.3. Software Collection Scriptlets
3.4. Package Layout
3.4.1. Meta Package
3.4.2. Packages in the Software Collection Namespace
3.5. Enabling a Software Collection
This chapter introduces you to the packaging with Software Collections (SC) for short.

3.1. What Are Software Collections

Software Collections is a way to concurrently install multiple versions of specific software on the same system without affecting standard software packages that are installed on the system with the classic RPM package manager.
No conflicts or overwritten system files
Software Collections consist of several components, which are connected and distributed together in order to provide their full functionality without conflicting or overwriting system files.
No changes to the RPM package manager
You do not need to make any changes to the RPM package manager present on the host system.
Only minor changes to the spec file needed
To convert a conventional package to a single Software Collection, you only need to make minor changes to the package spec file.
Building an unmodified spec file as a conventional package
You can build an unmodified spec file as a conventional package.
Build an unmodified spec file into a different Software Collection
It is possible to build an unmodified spec file into a different Software Collection.
Unique name for every package in the Software Collection
With Software Collections namespace, unique name is provided for every package that is included in the Software Collection.
No software updates conflicts
Thanks to Software Collections namespace, there are no conflicting software updates.
Multiple levels of Software Collections
Because one Software Collection can depend on another, you can define multiple levels of Software Collections.