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.

Sign up for GitHub

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

Jump to bottom

Check that foo.opam.locked is up-to-date #3654

Closed
AltGr opened this issue Nov 5, 2018 · 0 comments · Fixed by #3680
Closed

Check that foo.opam.locked is up-to-date #3654

AltGr opened this issue Nov 5, 2018 · 0 comments · Fixed by #3680
Milestone
2.0.2

Comments

@AltGr
Copy link
Member

AltGr commented Nov 5, 2018

With the option --locked, it would be useful to have a warning if the base opam file is newer and/or has dependencies that the opam.locked file doesn't have.

It's easy to make changes to the opam file and forget to update the opam.locked :)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.0.2
Development

Successfully merging a pull request may close this issue.

install --locked: check consistency with opam file rjbou/opam
2 participants
@AltGr @rjbou