-
Notifications
You must be signed in to change notification settings - Fork 365
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
Adjust common flags passed to Cygwin setup #6046
Conversation
a67acf2
to
c9e71db
Compare
It turns out that this can be solved in setup-ocaml by ensuring that Cygwin's setup registry key is restored as part of the action. I'm therefore not certain that we have to do this for 2.2.0 |
Always pass --no-version-check and --no-write-registry: - Setup should have been updated, so the version check is an interactive risk - Running setup on a root shouldn't interfere with the user's most recent settings (although for most users this should make no difference)
--site
to Cygwin setup when --confirm-level is unsafe-yes
This is no longer required for 2.2.0 - the adjustments in it are probably worth including in 2.2.1, however. |
Given that the user may be prompted, ensure that the dialogs can be used!
Oh dear, I appear to need to U-turn! There is an issue with this which probably is worth addressing for 2.2.0 - if the user happens to end up even interactively with an external Cygwin which needs input, then we've turned the dialogues off, which is bad. I've added a commit to use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Fixes #6041 - an additional option might be to explicitly abort when run non-interactively as well, but it's getting a bit niche because if you're non-interactive and expecting depext to work with an external Cygwin then clearly you must have specified
--confirm-level unsafe-yes
.Backport into 2.2 in #6057