Olaf Hering

There is indeed a life outside of opam. If I were in charge, all and everything would be built with dune, simply because it gets everything right (AFAICT). Regarding unison...

The opam file needs dune `2.7` instead of `2.0.7`.

It was apparently fixed silently with PR #582 via 45fb6065bc3672608f7c697c524d47fb003178ed

Such change sneaked into release `3.13.0` (commit 21f904250f8bc27abbeafadf70682aceb198b1e3), without being mentioned in the NEWS file. As a result `dune.configurator` can not be used anymore.

A `dune-project` file, which has `(package (depends (dune.configurator) ) )` works with 3.12, but fails with 3.13. My workaround/fix: olafhering/ocaml-ocurl@55e7bd94ece067d9e13dd494813f6c8cb1a10591

Its right after startup. Perhaps the app relies on an API which the Pro+ cant provide.

Is the last type available only under certain conditions? Dont know enough about Android to debug it.

Not sure if an `opam` environment requires an additional dependency to some sort of `pkg-config`

I get mixed results with `vim *.opam` with ocaml/dune@c939c2b0f. Initially `dune-configurator.opam` and `dune.opam` are wrong, maybe due to that lone `"dune"` in the `description`? A second `vim *.opam` shows all...

This needs rebasing. `fact`, `fib` and `tak` do not exist anymore.