Software Collections – when you need all the versions
summary
Software Collections provides parallel-installable, versioned runtimes by shipping modified RPMs with name prefixes and files under /opt/rh, activated at runtime with scl enable. Packaging uses the scl macros and the spec2scl helper to relocate files and create a meta package that sets PATH and LD_LIBRARY_PATH. Builds run in CBS with candidate/testing/release tags and optional CI checks; CentOS 8 appstreams replace many collections but critical stacks (for example tcc) remain supported.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:51What are Software Collections
- 3:23Key features and distinctions
- 4:48Technical perspective and paths
- 7:20How to use Software Collections
- 9:53Package structure and meta packages
- 12:24Updating and releasing collections
- 15:39Building and testing process
- 18:12Releasing and announcing collections
- 20:06Future of Software Collections
- 23:43Getting involved and Q&A
related talks
24mcontainerd Packaging: Who Should Ship and How?
30mHyperscalers SIG introduction
54mStill packaging like it's 1999?
16mTaming the Linux Distribution Sprawl: A Journey to Standardization and...
35mBuilding the Community Enterprise Operating System through CentOS Stream
26mLinux distributions, lifecycles, and containers
30mGetting Linux Distros to New Architectures
24mEveryone can contribute to RHEL now!