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.
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
Document Derivations and Deriving Paths #12290
base: master
Are you sure you want to change the base?
Document Derivations and Deriving Paths #12290
Changes from 9 commits
a654cc2
5eeae83
1926161
a8b1e3f
16bd5a4
97977b7
4b29ca8
4b9fb54
87c559e
96a46f9
6246901
80e6942
e77338d
fb7fc6a
0cd1e78
05a38b8
e409ea7
3d3a86d
f3fa9cf
f2d5be9
86f23c2
3a3f6ad
b027e22
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
On second thought, I don't think this term is precise enough.
The only expressions that produce derivations are those that evaluate to
builtins.derivation{,Strict} x
for some attrsetx
at some point during their evaluation, returning a[package attribute set]
or output path string referencing the instantiated derivation.The current definition describes a high-level goal that a human might have, but not an accurate term for the technical process, and not a common term that actual humans use; it'd just be "derivation" or even "package".
I guess we can't just refer to
builtins.derivation
, because we also havederivationStrict
, so I guess we could define it more reasonably as:Glossaries are all about relating the terminology to the outside world, so the link to Nixpkgs is ok.
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 this text was mostly moved around? Could be misremembering that , however.
I don't really want to have a "derivation expression" concept at all (if we make a new, improved, derivation primop, that would make for 3 primops, each with different interfaces, that make derivations. Best to just dispense with the notion and embrace #6507.) But I don't really want to shave that yak in this PR either.