You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was curious to try out the new dune 1.10 feature where it autogenerates the opam file, so I made a branch in my project Leonidas-from-XIV/orewa#4
Unfortunately (but unsurprisingly) the build fails because the repo does not have an opam file anymore and the CI scripts don't know that they have to generate it first.
I'm opening this as an issue, since I don't really know how to tackle this at all, since the existence of an opam file was the underlying premise of this repo. With the new dune we'd need to check for a dune-project file, install dune and attempt to generate an opam file I assume.
If it were for another build system I'd say why bother but since we're talking about dune it would be good to support this usecase which I could imagine becoming popular in the near future.
The text was updated successfully, but these errors were encountered:
You do need to check in the autogenerated opam file at this stage, until ocaml/opam#3797 is addressed in opam (cc @AltGr@dra27@rjbou). It uses dune promotion so this should hopefully not be too bad.
We could build the opam file here for dev packages though... any opinion on this @rgrinberg?
You'll always need to check in an opam file, even when support is added for auto-generation - what will change is that with Dune you would never have change the opam file again.
Note, however, that once the feature does land, you'd still want to be updating the opam file in the repo for a while with fields to remain compatible with users on an earlier version of opam.
(note that you could have no opam file in your repo, but this would depend on the package being published in a repository and having the correct instructions for the repo, so it's not likely to be a recommended thing to do)
I was curious to try out the new dune 1.10 feature where it autogenerates the
opam
file, so I made a branch in my project Leonidas-from-XIV/orewa#4Unfortunately (but unsurprisingly) the build fails because the repo does not have an
opam
file anymore and the CI scripts don't know that they have to generate it first.I'm opening this as an issue, since I don't really know how to tackle this at all, since the existence of an
opam
file was the underlying premise of this repo. With the new dune we'd need to check for adune-project
file, install dune and attempt to generate anopam
file I assume.If it were for another build system I'd say why bother but since we're talking about dune it would be good to support this usecase which I could imagine becoming popular in the near future.
The text was updated successfully, but these errors were encountered: