Keep or remove GlusterFS from EPEL-6?
Dennis Jacobfeuerborn
dennisml at conversis.de
Thu May 17 00:25:29 UTC 2012
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
More information about the epel-devel-list
mailing list