-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Special case for the epel-release
yum-package
#77
Conversation
epel-release
packageepel-release
yum-package
I don't mind special-casing epel, but isn't this patch doing so unconditionally? I was thinking that something like |
nice hack |
@avsm I did it like this because that's what seems to be already in use the
Cf. https://github.com/ocaml/opam-repository/search?utf8=%E2%9C%93&q=epel-release&type= To pass CI builds, there is this “run some script from the internet” solution also:
How do you think the depexp entry should look like?
or
|
I personaly like the centos:epel one |
@avsm any idea to move forward with this? |
I am not sure what to do with this with the current redifinition of depexts: ocaml/opam#3074 , and especially the replacement for the "tags" here: ocaml/opam#3058. The patch as is would still actually work still, and may be the simplest solution! |
This is ok by me; it just prioritises the epel package installation. A note in the README about how to specify the use of epel in centos depexts would be good. @AltGr says he'll merge this in the latest release. |
Fixes #70, (cf. also #76).
Tested with hdf5: