Add ability to prefer particular versions in packages. #261
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.
This is a stopgap until I can merge PR #120, which includes more robust concretization preferences. This allows any number of versions in a package to be marked
preferred=True
. Packages are now sorted by preference, then most recent in concretization. So you can mark directly in the package file what the preferred version is.PR #120 provides the infrastructure we need to express these types of preferences per-platform, per-compiler, etc. but this is a first step. This also allows Python 2.7.11 to remain the default while we get the Python stack working with 3.5.
@lee218llnl @alalazo @mplegendre: What do you think?
preferred=True
to a version directive will change its sortorder in concretization.
stable as new versions are added.
to specify default versions of things instead of always taking the
newest.