Resolve easily fails. KristopherC suggested to use update in these cases. But that does not help if you have a project with sub-projects and want to keep the same versions as much as possible. It also doesn't help if you have a manifest file created on Linux and want to use it on a Mac; it might fail because one or two dependencies are Linux-specific, while you want to keep all other dependencies the same.
Suggested behaviour of resolve:
It should try to stick to the versions in the manifest file as much as possible, but change the versions that block a successful resolve operation. This could be enabled via an optional parameter like "relaxed=true" or similar.
See also: https://discourse.julialang.org/t/how-to-achieve-consistency-when-using-workspaces-on-julia-1-11/135837
Resolve easily fails. KristopherC suggested to use update in these cases. But that does not help if you have a project with sub-projects and want to keep the same versions as much as possible. It also doesn't help if you have a manifest file created on Linux and want to use it on a Mac; it might fail because one or two dependencies are Linux-specific, while you want to keep all other dependencies the same.
Suggested behaviour of resolve:
It should try to stick to the versions in the manifest file as much as possible, but change the versions that block a successful resolve operation. This could be enabled via an optional parameter like "relaxed=true" or similar.
See also: https://discourse.julialang.org/t/how-to-achieve-consistency-when-using-workspaces-on-julia-1-11/135837