Ali Caglayan

I think putting the solution in `_build/log` is a good idea.

I've also come across a similar situation for Frama-C which has many empty (?!) opam files to get around having to write package stanzas in dune-project. Maybe it's not too...

Here is the repo: https://git.frama-c.com/pub/frama-c Here is an example of an empty file https://git.frama-c.com/pub/frama-c/-/blob/master/src/libraries/qed/qed.opam?ref_type=heads In this repo alone there are around 20 empty files. Opam seems to work fine with...

I am not suggesting we support every quirky build. I'm just trying to understand how a user might recover from this situation. If I remove the empty opam file: ```...

I didn't use opam in the message above. That was just `dune pkg lock` followed by `dune build`. The `INSTALL.md` file details setting up the switch with opam for which...

`opam pin . -n --recursive` also seems to just ignore the empty files rather than fail on them. Maybe @kit-ty-kate can confirm if opam will ignore empty opam files or...

We use `git describe` to find the version so one way might be to tag `3.XX+alpha` on `main` itself, that way `git describe` can find it.

I think the idea of introducing a `DUNE_CACHE_HOME` variable, appropriately documented, is sound. Removing `DUNE_CACHE_ROOT` or changing its meaning will take some work unfortunately. Its probably best we don't touch...

I've also suggested a common point, but I think `Dune_util` is better than introducing another new library for this.

Let's summarise the cache's we have in dune for clarity and reference: `DUNE_CACHE_ROOT` is the location for the shared build cache. When dune builds something with `--cache enabled` (the default),...