A suggestion:
For qcheck we've been bitten in the past by trying to support cross-versions as it quickly becomes messy.
Scenario: "Will ortac-runtime.0.5.0 require ortac-core.0.3.0 or only ortac-core.0.2.0"?
This will largely be wasted effort trying to debug lower bound failures! :grimacing:
A qcheck example of this happening in practice: https://github.com/ocaml/opam-repository/pull/24703
For this reason, I suggest using
"ortac-core" {= version}
etc. so that ortac-runtime.0.2.0 requires precisely ortac-core.0.2.0 (and so on)
in the interest of saving you from additional pain later :slightly_smiling_face:
A suggestion: For qcheck we've been bitten in the past by trying to support cross-versions as it quickly becomes messy. Scenario: "Will ortac-runtime.0.5.0 require ortac-core.0.3.0 or only ortac-core.0.2.0"? This will largely be wasted effort trying to debug lower bound failures! :grimacing: A qcheck example of this happening in practice: https://github.com/ocaml/opam-repository/pull/24703
For this reason, I suggest using
etc. so that ortac-runtime.0.2.0 requires precisely ortac-core.0.2.0 (and so on) in the interest of saving you from additional pain later :slightly_smiling_face: