-
Notifications
You must be signed in to change notification settings - Fork 28
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
update dependencies and tools #87
Merged
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
0a880d7
update base image to Fedora 37
bcressey 54db7df
update Buildroot to 2022.11
bcressey 9a34807
switch to GCC 11
bcressey fc9b1e6
update LLVM to 15.0.6
bcressey 767ed59
update Rust to 1.66.1
bcressey eee45dd
update SPDX license data to 3.19
bcressey 4d2b88c
update cargo-deny to 0.13.5
bcressey 5d04e73
license-tool: update dependencies
bcressey e2e8b68
license-scan: update dependencies
bcressey 0bfb362
refactor package install stages
bcressey 8074a18
bump version to 0.29.0
bcressey 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 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
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.
Nit: these commands are reformatted here, but were added in the first commit of the series. Probably the diff will be smaller if the format doesn't change(?).
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 think they should have been this newer format originally, and the sooner we change it then the sooner it's in better shape for ongoing updates where the diff can show individual lines more clearly.
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, so probably keep this format in the first commit of the series
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.
This gets back to whether we treat our unit of change as individual commits or the pull request. I personally am not as concerned about individual commits in a PR unless there is a chance one of those commits may need to be reverted at some point.
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'm not sure it would be worth the hassle.
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.
Fair point - I'd tidy this up if there were another change, but I don't think it's worth the retesting burden just for commit history. Style-wise, that was consistent with the rest of
Dockerfile
at the time the change was made, so it's not indefensible. 😀