When we set up a new dune project with its own local opam switch for sandboxed development, the workflow doesn’t seem right. Unless they know exactly what to do here, I feel like the developer would get stuck. Here’s an example:
$ dune init project my_proj
$ cd my_proj
$ opam switch create .
$ eval $(opam env)
$ dune build
command not found: dune
It’s a chicken-and-egg problem.
I’ve heard rumblings of tooling to solve this problem, and wanted to check in–is there any movement on this? Or at the very least, shouldn’t a new switch install dune by default so that we can kick off an initial build, add new dependencies to the dune-project file, and update the my_proj.opam file?
If you are thinking, well why not run a dune build before creating and activating the new switch? Obvious problem–the compiled artifacts could end up being for a different version of OCaml.
2 posts - 2 participants