| |
@@ -0,0 +1,31 @@
|
| |
+ =======================================
|
| |
+ Regarding EPEL and Software Collections
|
| |
+ =======================================
|
| |
+
|
| |
+ Background
|
| |
+ ==========
|
| |
+
|
| |
+ For RHEL 8, Red Hat made the decision to provide multiple versions of software
|
| |
+ in the form of App Stream modules instead of Red Hat Software Collections
|
| |
+ (RHSCLs).
|
| |
+
|
| |
+ SCLs are maintained by the CentOS Software Collections SIG, not the EPEL SIG.
|
| |
+
|
| |
+ RHEL 8 comes with the ``scl-utils`` and ``scl-utils-build`` packages--which
|
| |
+ contain tools for using and building SCLs. These packages appear to function as
|
| |
+ expected with RHEL 8 and CentOS 8.
|
| |
+
|
| |
+ Recommendations
|
| |
+ ===============
|
| |
+
|
| |
+ EPEL will not provide SCL support, although it will not prohibit use of the SCL
|
| |
+ tools provided with RHEL 8.
|
| |
+
|
| |
+ EPEL will not provide any SCLs.
|
| |
+
|
| |
+ EPEL encourages the community to follow Red Hat’s lead and provide multiple
|
| |
+ versions of software for RHEL 8 and CentOS 8 in the form of modules rather than
|
| |
+ SCLs.
|
| |
+
|
| |
+ For use cases that require the parallel installation of multiple versions of
|
| |
+ the same component, EPEL recommends the same solution as RHEL 8: containers.
|
| |