Olaf Hering

This crash with bytecode-only is still happening today. [devel:languages:ocaml:bytecode_only/ocaml-camomile](https://build.opensuse.org/package/show/devel:languages:ocaml:bytecode_only/ocaml-camomile)

Unlikely, see `pkg-config --list-all | grep pix`

Hmm, so #588 is biting again, hopefully it makes no difference. The used source is avsm/ocaml-ctypes@bef7d50843868998f68eac2664a5a5f5dd996d39

However, looking at [ocaml-ctypes:testsuite](https://build.opensuse.org/package/show/devel:languages:ocaml/ocaml-ctypes:testsuite), the failures are apparently not specific to Tumbleweed...

The `dune-port` branch breaks consumers of ctypes because the `ctypes.cmxa` lacks the `-I $(ocamlc -where)/integers` include path for C stubs. See `ocamlobjinfo ctypes.cmxa|head` from a `dune` build and from a...

IMO opam files should not be generated by default. And generated files should not be in a SCM anyway. The commit message does not state why changing `generate_opam_files` to `true`...

`(version )` is supposed to carry the version of the project. This variable can be referenced in other dune files, if needed. I think changing it should be wired up...

I'm meanwhile ok with this PR. In the context of opam-repository, the current result of `opam build unison` is a binary with text UI. This will not change with this...

Making `dune-project` the primary is the stated goal.

I'm not sure if it was already discussed in the context of unison: why are the `build` rules added? I remember most other projects removed it in the recent past...