On 18 July 2018 at 14:19, Ken Dreyer <ktdreyer@xxxxxxxxxxxx> wrote: > On Wed, Jul 18, 2018 at 9:36 AM, Jason L Tibbitts III <tibbs@xxxxxxxxxxx> wrote: >>>>>>> "RI" == Roman Iuvshyn <riuvshyn@xxxxxxxxxx> writes: >> >> Maintainers are generally going to be very reluctant to update a package >> in EPEL without some pressing need. Not generally as reluctant as Red Hat would >> be for a package in RHEL7 proper but you would still need to ask. > > I've always thought it's the other way around, that EPEL moves faster > than RHEL, but you're making me think there's gotta be a story behind > this comment! :D > Originally EPEL was built to be lock step with RHEL. At the time of RHEL-4/5 this meant that you were to only put in what is now called Long Term Support software which would not get updated for the 4 to 5 year lifetime of the release. So various documentation is set up to say that you are going to generally not update items unless there is no other way to do so. Several things have changed since then. 1. RHEL releases are no longer around for just 5 years but 10-12. 2. RHEL rebases itself more often so that it is following upstreams for various components it kept 'stable' before. 3. Software that is used by most sites have completely different lifetimes and architectures than they did then. Where the idea behind EPEL was about compiled binaries which could sit steady.. most users are needing things from diverse ecosystems that consider 3 months to be too long to support at times. So EPEL ends up being a mixed bag.. there are parts which do not get updated and only move slowly and there are parts which move faster than RHEL.. and it is up to the maintainer of a package or set of to come up with what they feel works for them./ > - Ken > _______________________________________________ > epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/VDGTCBYPUTV6NII4Z4SZCKCEL4U4LUOQ/ -- Stephen J Smoogen. _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx/message/6LSYGSJKNLBFH5JFFE4CHWH6WL62VJCB/
