Re: dune and opam issues: a summary of my fuzzy understanding

>   - Consider turning on generation, and removing unison.opam from the
>     repo, pending feedback, probably via a PR that does only that.
>
>   - See if there are things to be done other than the above 3.
>
>
> I would rather suggest to change the opam file so that it uses the Makefile. If make is the primary build system, then the dune files should be maintained by their users.  As a result, a user of the main build system can maintain the opam files without understanding dune, which is mainly orthogonal.

Another reason for keeping the OPAM file(s) is to utilize
[opam-publish] to streamline the publishing of the Unison package(s)
to the OPAM repository. Once a version is tagged, and its OPAM files
are up to date, then anyone may propose them to the OPAM repository by
running `opam publish`, rather than handwriting an OPAM file for each
version.

[opam-publish]: https://urldefense.com/v3/__https://github.com/ocaml-opam/opam-publish__;!!IBzWLUs!Ril1nRCkGTzQADHbu5sFg58lhGaVotbey6hxC3rYKd3_RYrVkHOX5u69B35lmvJFBsPWHjIAp0YBCBM_JM12syfNNLH1-D0M$ 

Yishuai