This repository has been archived by the owner on May 5, 2022. It is now read-only.
Implement "minimal version selection" for dependencies #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The algorithm used here is based on my understanding of https://research.swtch.com/vgo-principles, which can be very roughly summarized as "providing repeatable builds by preferring the lowest possible specified version of any package". Complex dependency constraints are dropped completely. Each package specifies only a minimum acceptable version. If multiple packages depend on P then the maximum minimal version of P is used. If two packages require different major versions of P, it is an error. A set of "active" packages may be passed to resolve-deps. No version of an active package is ever included in the result. The idea being that the active packages are usually checked out on a branch in the user's workspace.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The algorithm used here is based on my understanding of
https://research.swtch.com/vgo-principles, which can be very roughly
summarized as "providing repeatable builds by preferring the lowest
possible specified version of any package".
Complex dependency constraints are dropped completely. Each package
specifies only a minimum acceptable version. If multiple packages
depend on P then the maximum minimal version of P is used. If two
packages require different major versions of P, it is an error.
A set of "active" packages may be passed to resolve-deps. No version
of an active package is ever included in the result. The idea being
that the active packages are usually checked out on a branch in the
user's workspace.