Javier Chávarri

I tried using `(switch)` in the `melange` context defined in the test so that public libraries get installed in separate switches, but the result is the same. 😕 I guess...

@rgrinberg is https://github.com/ocaml/dune/pull/10414/commits/63f17d133763693cfd77c048ae7aa960c136554a what you had in mind? I tried moving the `with-directory` annotation function to `User_message` to simplify things further, but this creates a cycle between `User_message` and `Path`....

> We're actually trying to get rid of contexts from the engine and make them strictly rule only, so this PR would make it more more difficult for us. Ftr:...

> I think you can just get rid of that annotation and just include `dir` inside `User_message`. I tried adding a new field `dir : Path.t option` to `User_message.t`, but...

> I think you can just use a string path though. Tried something in https://github.com/ocaml/dune/pull/10414/commits/550d20e5f33efdc58ff238cca727927ea30321db.

Tests are failing for unrelated reason, see https://github.com/ocaml/dune/pull/10484.

Sounds that there could be some display mode that outputs build data in JSON or some other format, so that it can be parsed by tooling more easily, and contains...

I talked to @andreypopp and he suggested to remove the `duneContexts` protocol command, and instead call `dune describe contexts` directly from the vscode extension. I applied these changes in https://github.com/ocamllabs/vscode-ocaml-platform/pull/1449/commits/9d348689874890487734bb20b02d1daeb282d7c2...

In the last commits, I removed the last usages of `copy_files` in the `url` library. For this, I had to change the base branch to the PR in #127 so...

Doesn't seem we'll be moving forward with multi-context: https://github.com/ocaml/dune/issues/10507#issuecomment-2189900682