Stephen Sherratt

Thanks for the patch @tatchi. Apologies for the delay in getting to this. I agree that it's better to enable this test and accommodate for its flakiness than disabling it,...

@emillon I think this slipped through the cracks. Think it's good to merge?

I've added quotes in a few more places. I think the errors in this file are consistent now so I've removed the TODO.

This feels like a similar issue to https://github.com/ocaml/dune/issues/10291 in that it involves a generated file containing paths to files within the build sandbox.

I can't think of a way to fix this that doesn't involve modifying `ocamlbuild`. Any package that persists an opam variable containing a path during its build or install step...

Digging deeper, I'm hesitant to modify ocamlbuild to solve this problem. Ocamlbuild already has compile-time configuration for relocating its installation to a specific destination known at compile-time. The build commands...

@mseri in response to https://github.com/ocaml/opam-repository/issues/23694#issuecomment-1518106351, what's the current process for fixing version upper bounds on revdeps? Is it more involved than just setting them to the previous version of the...

I currently have a use case relevant to this issue. I'm working on a benchmark runner for ppxlib, and the runner has additional dependencies to ppxlib so I've made a...

Closing this in favour of maintaining a fork of ocamlbuild in Dune's [opam-overlays](https://github.com/ocaml-dune/opam-overlays/tree/main/packages/ocamlbuild) repo. The dune developers intend to maintain forks of a small number of widely used packages whose...

Ok fair enough! I'm happy to leave it open but I don't have a lot of time to commit to working on this in the near future.