Re: A plan regarding SCLs in EPEL 8

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Oct 07, 2019 at 01:16:47PM -0500, Merlin Mathesius wrote:
> I was asked to draft a plan stating what EPEL 8 should do regarding
> Software Collections. The draft I came up with is included below.

Looks good to me. +1 here. 

> EPEL Steering Committee: Please ratify this plan or provide feedback as
> necessary. When it's ready, and I will prepare a PR for this to land in
> https://pagure.io/epel/blob/master/f/docs/source

That would be great... 

kevin
--
> 
> Regards,
> 
> Merlin
> 
> ------------------------------
> 
> 
> *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.
> 
> ------------------------------

> _______________________________________________
> epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx

Attachment: signature.asc
Description: PGP signature

_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux