I agree that it makes sense to associate EPIC releases with EL "point"
or "y" releases.
Some orgs (like us) download new content on timers, and while it's not
wrong to say that people should read release notes and updates, there is
currently a *lot* of content in EPEL etc to keep track of, and I think
people find it really valuable to have a repo that makes the "don't
overwrite/upgrade core" promise. I like the differentiation that is
starting to develop in the CentOS ecosystem where there are some more
"experimental" repos (like YUM4) that *do* overwrite, and say so
explicitly. The ecosystem also has good tools to mix and match these
repositories with core content (pulp/Satellite). Generally, we sync all
of EPEL but only use the command-line bits; I'm unaware of any user
reporting problems due to a GTK rebase in an EL minor release.
IUS used to talk a bit about repo safety on their web page, does this
need to be something more explicit for repos in general? Or something
that might be reflected in metadata somehow?
Thanks,
Marty
On 5/17/2018 10:01 PM, heelsleeh@xxxxxxx wrote:
good idea,
EPIC release --> rhel release, centOS release
keep the old RPMS when EPIC package upgrade.
no compatibility issue any more.
_______________________________________________
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/QVRJ4RLWDSNZ3AQJMKJ2SIMNLEYSQPAR/
_______________________________________________
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/TP7JWI3CRGDI6WPKGBENU5MOWDWTD445/
