-
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
source: add --no-checksums
& --require-checksums
flags
#5563
base: master
Are you sure you want to change the base?
Conversation
src/client/opamCommands.ml
Outdated
mk_flag ~cli (cli_from cli2_2) ["require-checksums"] | ||
"Enforce checksum verification befor downloading sources.\ | ||
This is equivalent to setting $(b,\\$OPAMREQUIRECHECKSUMS) to \"true\"." | ||
in |
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.
might be worth sharing the flags definitions with the ones used in OpamArg.build_options
? (maybe that was too tedious to be worth it, in that case it's alright)
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.
Appreciated, and this looks great to me. As @AltGr mentioned, it may be useful to share some code. Thanks a lot. |
…he counterpart of that is that we loose the fact that the newly effective options (in opam source for ex) are not flaggued as new in cli 2.2
…ption. The counterpart of that is that we loose the fact that the newly effective options (in opam source for ex) are not flaggued as new in cli 2.2" This reverts commit a2e7b21ccaad48ca11432e9fbd0a7a2c90377aee.
ef3b1e2
to
a5171aa
Compare
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.
I don't understand this feature request. What does this bring in terms of change for users?
I understand --require-checksums
, although i feel like this would have more usability as a global opam option
.
But --no-checksums
i really don't understand. If the goal is to allow packages without a checksum, then why not simply add a --allow-no-checksums
argument instead of ignoring the checksum altogether?
I'm also wondering what how opam source
is special compared to the other commands that might fetch packages.
let no_checksums = no_checksums cli (cli_from cli2_2) in | ||
let req_checksums = require_checksums cli (cli_from cli2_2) in |
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.
let no_checksums = no_checksums cli (cli_from cli2_2) in | |
let req_checksums = require_checksums cli (cli_from cli2_2) in | |
let no_checksums = no_checksums cli (cli_from cli2_4) in | |
let req_checksums = require_checksums cli (cli_from cli2_4) in |
/cc @hannesm @reynir