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

documentation: improve the unsafe-yes documentation for confirm-level #5719

Open
hannesm opened this issue Nov 8, 2023 · 0 comments
Open

Comments

@hannesm
Copy link
Member

hannesm commented Nov 8, 2023

The documentation is rather sparse (opam 2.1.5 here):

       --confirm-level=LEVEL
           Confirmation level, LEVEL must be one of `ask', `no', `yes' or
           `unsafe-yes'. Can be specified more than once. If --yes or --no are
           also given, the value of the last --confirm-level is taken into
           account. This is equivalent to setting  $OPAMCONFIRMLEVEL`.

And then, --yes and --no are documented more clearly:

       --no
           Answer no to all opam yes/no questions without prompting. See also
           --confirm-level. This is equivalent to setting $OPAMNO to "true".

       -y, --yes
           Answer yes to all opam yes/no questions without prompting. See also
           --confirm-level. This is equivalent to setting $OPAMYES to "true".

But the unsafe-yes is not described much. What is the "unsafe" part in it? This issue has been opened due to investigation by @ben-grande in mirage/qubes-mirage-firewall#187

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants