-
Notifications
You must be signed in to change notification settings - Fork 22
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
Test with ocaml-system #327
Comments
Thanks! It would help us with prioritization if you could give a nut-shelled account of why we need this in the CI and how it would show up in the CI results. As it is, there are like 6 years worth of discussions across different PRs and issues to try comb through, and afaict none of them give a concise statement of how this work is meant to benefit opam repo's CI, at least not one that is clear to me given my limited context. Thanks in advance! Something that would really help with prioritization is a remark on the impact of NOT having this feature in place currently. |
ocaml-system is one of the default OCaml compiler that people will encounter in the wild. People that simply install ocaml and opam through their system package manager will get it. The limitations of ocaml-system (the installation of OCaml being split between /usr/... and the opamroot) are well known but not tested at all anywhere. So it seems reasonable to test it. The typical issues can in build-system themselves where they look at /usr/... for packages instead of the opamroot, or if the ocaml-system package itself if the substitute for the |
Related to this, I've recently hit that bug locally recently:
The ocamlfind installation runes used to be racy so the build/install steps were split at one point in the opam file of the projects that continues to use |
Reopening a separate issue after #43 (comment) was closed
this feature is still desirable
The text was updated successfully, but these errors were encountered: