On 07/12/15 17:40, Kevin Fenzi wrote:
FYI, this discussion might be better on the actual epel-devel list...
On Mon, 7 Dec 2015 15:17:54 +0000
Paul Howarth <paul@xxxxxxxxxxxx> wrote:
On 07/12/15 14:59, Pierre-Yves Chibon wrote:
...snip...
Could make a compat package in EPEL7 be an option?
This way you introduce back the version that was present without
conflicting with RHEL.
Only if it's a actual different so version. Is it?
If not, why can't you use the version RHEL is shipping?
Could probably do something like what happens with packages that RHEL
doesn't ship for all architectures: the RHEL SRPM is cloned into
EPEL, the release field has "0." prepended to it to ensure that the
RHEL version is preferred where available, and the resulting package
built and shipped.
I don't think thats allowed. The package is in rhel, you cannot ship it
in EPEL just to be a different version.
It's not a different version. It's an exact clone of the RHEL package
except with "0." in front of the release to make sure the RHEL package
"wins" where it is available. It is in fact the official EPEL
limited-arch package policy:
https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages
The problem this would fix is the broken deps in the window between RHEL
7.2 and CentoOS 7.2 releases, However, given the amount of time such a
package would take to get pushed to EPEL anyway, it's possible that
CentOS 7.2 would be released before the temporary fix, so it might not
be worth doing at all.
Paul.
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
