Skip to content

Commit e3506c9

Browse files
Remove constraints on package versions in conflicts, it's unsupported
After a debugging session with @kit-ty-kate as part of fixing tarides/opam-monorepo#349 and ocaml-opam/opam-0install-solver#46 we realized that OPAM doesn't support resolving package variables in `conflicts` fields (the linter complains about this in `depends` fileds but not in `conflicts` fields, but the solver never resolves these variables). So this constraint doesn't do anything in OPAM and it causes issues in the opam-0install-solver which attempts to resolve them.
1 parent 24ff26d commit e3506c9

File tree

1 file changed

+1
-6
lines changed
  • packages/ocaml-options-vanilla/ocaml-options-vanilla.1

1 file changed

+1
-6
lines changed

packages/ocaml-options-vanilla/ocaml-options-vanilla.1/opam

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,12 +8,7 @@ depends: [
88
conflicts: [
99
"ocaml-option-32bit"
1010
"ocaml-option-afl"
11-
"ocaml-option-bytecode-only"
12-
{ocaml-system:version < "5" |
13-
ocaml-base-compiler:version < "5" |
14-
ocaml-variants:version < "5" |
15-
arch = "arm64" |
16-
arch = "x86_64" }
11+
"ocaml-option-bytecode-only" {arch = "arm64" | arch = "x86_64" }
1712
"ocaml-option-default-unsafe-string"
1813
"ocaml-option-flambda"
1914
"ocaml-option-fp"

0 commit comments

Comments
 (0)