Improve the way we pick the package-set to upgrade to #721
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As we prepare the 0.14 release of the compiler, it looks like we won't be able to put out a matching package set for some time - this means that people pulling in the toolchain for the first time will get the new compiler and try to use it with the 0.13.8-compatible set, which right now results in a confusing error.
I believe the "proper" fix would be #633, but that's a fairly complex change, while this PR implements a simpler, but smarter logic to pick the set version (see #657 for details) on
initandupgrade.This includes properly warning the user when they use a compiler for which we don't yet have a set out. This is the error message they'd get if trying to use the 0.13.8-compatible set with the newer purs 0.14:
Fix #687, fix #657, fix #666