Closed hannesm closed 3 years ago
hmm, the "lint-opam" fails with (//cc @talex5):
x509.opam: changes needed:
"mirage-crypto-pk" [from lib] (remove {with-test})
The opam file contains:
"mirage-crypto-pk"
"mirage-crypto-pk" {with-test & >= "0.8.10"}
This is wrong -- the opam file has twice a mirage-crypto-pk dependency: for normal operations, any release is fine. To succeed the test suite, any version greater or equal 0.8.10 is needed. Is there a cleaner way to express this (//cc @kit-ty-kate who may have an answer)? Or could "lint-opam" be adapted to cope with such dependencies in an opam file?
Yes I've reported this issue in opam-dune-lint a few weeks ago: https://github.com/ocurrent/opam-dune-lint/issues/23 I'll have a look now if I can fix this issue myself quickly.
https://github.com/ocurrent/opam-dune-lint/pull/25 should fix that. I don't have commit rights on this repository but I'll ask around.
I've merged the fix now.
Thanks @talex5 @kit-ty-kate
This is to avoid warning 16 (defaults to be enabled with 4.12).