-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
got: 0.97 -> 0.98.2 #307538
Merged
Merged
got: 0.97 -> 0.98.2 #307538
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 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 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.
@AndersonTorres, is this change a proper and correct improvement? I have yet to fully understand
passthru
andtesters.testVersion
, but from my current understanding this should be good. I'd truly appreciate your feedback and expertise on this.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.
Yes, it is fine.
As I have explained before,
installCheckPhase
is meant to run checks provided by the upstream package developer. The difference betweencheckPhase
andinstallCheckPhase
is thatinstallCheckPhase
runs after installation whilecheckPhase
runs after build.Custom scripts are better suited to
passthru.tests
.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.
Thanks for the explanation, @AndersonTorres, that's helpful!
Yet for some odd reason my 🧠 refuses to understand
passthru
(might be something to do with the wording that seems odd to me—not that it is, just that it makes it harder for me to grok it). Seems I need to revisit and re-read the available documentation…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.
passthru
is similar tometa
in the sense that a modification inpassthru
does not trigger a mass rebuild.Usually we use
passthru
in order to collect some useful info from the derivation and expose it to the external world.E.G. suppose you have a parameter,
uiType
, that enables a fancy UI ingot
, and the end user wants to know which GUI type was used (say,cli, curses, gtk3, qt10
).Then you can write
This way, the end user can evaluate
got.uiType
to know what UI was enabled.Obviously the code above is a crude example. Usually we do cleaner and more useful stuff.
E.G. in
live555
we put a test:This way we can test this by calling
live555.tests.vlc
.The idea is that
vlc
depends onlive555
, and sometimes thevlc
team does not update its code whenlive555
introduces a breaking change. So we at Nixpkgs catch this by running this test.