-
Notifications
You must be signed in to change notification settings - Fork 9
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
Support specifying system packages to install in Docker #41
Comments
The good practice in this case is to use opam depext fields. Then, the CI templates could simply run |
@Zimmi48 for this feature request, should we create a related issue in https://github.com/coq-community/docker-coq-action/issues as well? |
@erikmd I guess so. |
Hi @palmskog, do you believe this use case still needs some automation via a dedicated feature in docker-coq-action and/or in templates? FWIW, there is now:
But as mentioned earlier by @Zimmi48 − #41 (comment) −, some (not all) system-wide install can be triggered by |
@erikmd I still need this feature for some of my projects, but the non-depext workaround (your installation of Debian packages) is not a huge pain. But hasn't depext now been improved in opam 2.1 and later? I think we can keep this issue open until we figure out the "right" way to install depext'd stuff. |
Yes, |
Some extraction projects rely on OCaml libraries that require certain system packages to be installed. There should be a way in
meta.yml
to specify these system packages and have them be installed in Travis and other CIs that rely on Docker images.The text was updated successfully, but these errors were encountered: