On 05/17/2012 02:07 AM, Bryan J Smith wrote:
And if they mirror EPEL into, say, a RHN Satellite Server channel,
how
do they know all of what to filter out from EPEL because it's
conflicting with RHN packages? Especially when the packages are newer
than the RHN ones.
Is it possible to create an "EPEL-extended" repo? That seem to be the
logical solution. Keep EPEL completely collision free and push packages
like GlusterFS into "EPEL-extended" that users can enable in the repo config.
That way RHEL customers wouldn't have to change a thing and just keep
running basic EPEL but they (and derivative distro users) can opt-in to get
the difficult stuff.
Regards,
Dennis