Stephen Sherratt

Trying this out on macos and it looks like it's trying to read the (non-existent) `/proc/self/exe`: ``` $ dune build ... ocamlc -c oneshot_webserver.mli ocamlfind ocamlopt -package unix -c oneshot_webserver.ml...

Since your latest changes I can now use this on macos and linux to build packages with dune's package management features. One issue I run into now is that using...

I tried using this to build the `topkg` package and ran into some issues which I describe here: https://github.com/ocaml/dune/issues/10271. In summary: - the generated "topfind" file currently contains paths inside...

I'm modifying the rpc-connector-common template fragment to sanity check this attribute. Addressing the greater issue of attributes not being type-checked will be more complicated, as it's up to the templates...

I question whether this is the most practical behaviour. It makes dune harder to use in places with spotty internet, and also when trying to get work done on planes...

What would be the harm in using the repo in ~/.cache/dune/git-repo if it exists?

Yep

But also I think we should allow users to do a solve without forcing an update. Imagine you're trying to add a new dependency to a project and you inadvertently...

> Because updating the repository could fail for multiple reasons. Some of them should not have a fallback like that, and we don't have a way to distinguish the different...

>> and you inadvertently introduce a problem caused by switching to a later version of a dependency that introduces a bug. (That's a different issue from the one we're currently...