-
Notifications
You must be signed in to change notification settings - Fork 372
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
Remove dependency on state
value for opam2nix use cases
#4147
Conversation
…_package_source without extra downloads or an explicit switch
…ifferent contexts
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.
A little refactor that is completely reasonable to integrate in opam. Just minor/nitpicking comments (naming).
Thanks for the pr!
src/state/opamSwitchState.mli
Outdated
@@ -54,6 +54,13 @@ val compute_available_packages: | |||
pinned:package_set -> opams:OpamFile.OPAM.t package_map -> | |||
package_set | |||
|
|||
(** Raw function to compute the conflicts for all packages, given | |||
the set of available packages and the corresponding opam files. | |||
the `u_conflicts` field when building a universe manually. *) |
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.
Is there a missing line in this ocamldoc comment? the u_conflicts field <...>
seems to be incomplete.
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.
Not sure where that went, fixed thanks.
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.
Oups, part of my review was missing.
The context free switch paths is not only advantageous for |
Thanks for the feedback, I've pushed updates to address them (as well as merge with master). The CI failures don't look related to my changes. |
Yes, CI was broken on master, but it's ok (all green on my launches). Thanks! |
Fixes #4030