Upper range of constraints must be manually specified for top level project.

[jordwalke]

Upper range of constraints must be manually specified for top level project.

[aweis]

Thanks for writing this up!

[andreypopp]

I wonder if this is only a problem with unifying the ocaml compiler ranges - or has this happened with other packages?

ocaml compiler constraint of a root package is treated as a special case — it is solved first in isolation (usually means it takes the highest possible version) — and then given its version the other constraints are solved

This was done cause usually one wants to develop against a specific package version + to reduce the size of the package versions to consider (makes solver run faster)

But I agree it is confusing. I still think it's a good idea to require to specify OCaml toolchain version explicitly for the esy project but I think we'd want to have a different way to do that:

• introduce another key in package.json (maybe "esy.ocamlToolchain") to specify which ocaml version to use when the package is the root package in the esy workspace
• treat ocaml in "dependencies" as regular constraint