-
Notifications
You must be signed in to change notification settings - Fork 412
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
Package management should Ignore unused opam files when pinning #11276
Comments
Thanks. Dune can infer projects from one of two sources:
The project file doesn't define any packages so dune goes for 2. AFAIK, an opam file with the version incantation is invalid. So I don't think there's anything we can do here. |
Can you post your pins stanza? Maybe we can make the loading a little lazier. |
I deleted that branch but I think it was simply
Yeah, I kind of understand that, ideally, all opam files should be correct. But empty opam files exist in many places because people don't generate them from dune-projects and dune refuses to build public modules without a corresponding opam file. One or both of the following could be done:
I do understand if option 2 is not desirable, and I can see that it doesn't appear, but on the issue now, but I clicked "Feature request" and not "Bug report" when I created this issue. I don't believe this is a bug, the current behaviour is acceptable, but it is worth flagging |
Yes, that's true. The shortest valid OPAM file is
|
This is feedback on the dune package management preview.
I have a file a project that pins another project, but it fails to build with
Error: unexpected version
because of some empty but unused opam files in the project.It works after just adding one line to the relevant opam files. See rems-project/cerberus#817
The text was updated successfully, but these errors were encountered: