Skip to content
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

OPAMCONFIRMLEVEL overrides --yes and --no, etc. #4683

Merged
merged 1 commit into from
Jun 2, 2021

Conversation

dra27
Copy link
Member

@dra27 dra27 commented May 27, 2021

Fixes #4582. It's possible that this can be done in a different order - I've had the global options record where the answer came from (to allow the environment to override it)

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Similarly, OPAMYES overrides --no
@dra27 dra27 added this to the 2.1.0~rc milestone May 27, 2021
@kit-ty-kate
Copy link
Member

I think --yes --confirm-level=unsafe-yes (via command line options) should also result in unsafe-yes. Does this patch also do that?

Could we also add tests for the combination of both? It's something that is quite wildly used in CI environment

@rjbou rjbou linked an issue May 27, 2021 that may be closed by this pull request
@dra27
Copy link
Member Author

dra27 commented May 27, 2021

@kit-ty-kate - that's already the case before this PR. The environment variables work together as you expect and the CLI flags work together as you expect - just not both at once!

@dra27 dra27 mentioned this pull request May 27, 2021
@rjbou rjbou merged commit 430dd95 into ocaml:master Jun 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

opam-2.1 install -y fails
3 participants