Etienne Millon
Etienne Millon
interesting, I thought we did that for tests?
no, you're right, I think I'm mixing up things. that must be because the full path to failing tests is sometimes printed, and the context name is part of these.
Thanks. Can you add a changelog entry in `doc/changes/`?
Hi, Have you tried [the second approach in the howto guide](https://dune.readthedocs.io/en/stable/howto/rule-generation.html#using-dynamic-include)? It explains how to encode this kind of "rule scheme". You'll have to change the directory structure a bit...
That's not ideal, but a solution in that could work in the meantime is to change the test to `touch` the other side of the hardlink after unlinking it (with...
For a first release, I would consider the following strategy to select whether this feature is enabled: - attach these rules to `@ocaml-index` - if `ocaml-index` is available, and OCaml...
> I agree that these warnings are annoying but I am also not fond of modifying the vendored code, since it makes it harder and harder to resync with OPAM...
(in other words, our aim should be decreasing the diff with upstream, not removing code; but in that case that might be aligned)
I don't think this solve the issue. From a clean checkout of this branch: (build commands are taken from `dune.opam`; I'm not sure which ones `pkgsrc` uses) ``` $ ./configure...
I don't know what's the right solution TBH. the original command uses a relative path for mandir, does that mean it should be interpreted relative to prefix? it would be...