On 04/11/2018 03:13 PM, Nico Kadel-Garcia wrote: > EPEL is a default, critical requirement for many tools, including Chef > and mock. Many environments running RHEL or CentOS 6 could not be used > without EPEL's plethora of useful tools. RHEL channels can conflict > with each other because they are enabled on an individual host, case > by case basis. I think, from old experiences, that having *anything* > in EPEL that overlaps with any RHEL published channel is begging for > pain. There's a number of problems with EPEL saying they won't conflict with any channel RHEL "publishes". For one, I don't know of any such list of channels and all the rpms they contain. Additionally, that would mean likely removing things like Chef and mock, because I suspect there's some channels out there with those. > > It may cause pain to current RHEL ansible users, but I think that the > EPEL package needs to be renamed to something like "ansible25" to > avoid conflicts with the RHEL channel. I don't think thats practical / desirable. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
