Repository navigation
Simplify lazy dependency handling #45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+43
−74
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.0.7 has no functional changes yet, so you could use it for this stuff.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now the build system ignores these version numbers, but in the future we'd like to use them to make decisions in situations where multiple versions of a package are present simultaneously. However, this doesn't work if multiple PRs are merged into master without bumping the version number, since this means two users who fetch latest master could have different commits with the same version number, and the build system has no way of knowing which is newer.
My plan is to follow this pattern until we have these features nailed down (likely in the 0.18 release cycle) at which point I can reevaluate whether this pattern makes sense given how the features end up being implemented.
To save some busy work though, I don't think we need to make a new tag for each patch release. Tags are a useful way to find old releases quickly, but I don't think there are many use cases for intentionally fetching an old patch release. Most users will just want whatever is latest on master, the users looking for an old release are probably looking for a particular Zig or SDL version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been tagging when I want to pull a new version into SDL_image or SDL_ttf. (I know I could just use commit too, but it's nice when there's a tag attached.)
I do fear the upcoming package manager changes are going to create a lot of problems or busy work if every commit effectively has to have a unique version. It'd be nice if the package manager could support version templating or something when used in conjunction with version control tags.
.version = "1.0.8-dev.{n}+upstream.3.4.18.git.{id}". Obviously that wouldn't work with archives, but most distributions will only be producing archives for tagged, concrete versions anyway.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha, that makes sense.
I think there's still room to explore how exactly this works in the build system (just saw your comment on the respective issue.)
FWIW I don't think every commit needs a unique version--just anything that
mainis going to point at for a substantial amount of time. For example, there's no reason to bump the version multiple times within the same PR since on mergemainwill jump to the last commit. Similarly, if merging two PRs in a row, it's probably fine to do the version bump after the sequence of merges.An alternative strategy would be to not treat
mainas stable, and instead tag any release that's intended to be depended on. There are definitely advantages to this, but I'm experimenting with the former approach first since it requires less clicks.