Repository navigation
Layout: a pin may name its tag, and a download is pinned by version - #113
Merged
Merged
Conversation
micropython-pydevices' DEPENDENCIES.lock holds toolchains fetched by tag and six archives that are not git checkouts. The rule now says how each is written, as that file writes them.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 pin-file rule gave one line shape: name, clone URL, full commit. Two real cases didn't fit it. A toolchain such as ESP-IDF is fetched by tag, so its line pins the commit and names the tag in a trailing
# tag <tag>, and the build checks the checkout is that commit. An archive that isn't a git repository (SDL2's tarball, a registry component) is pinned by its URL and version in a section of its own.This is how micropython-pydevices'
DEPENDENCIES.lockwrites them; the reference page now says so. Docs only.