| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2023-03-05 | clarify definition of "installable" | Valentin Gagarin | |
| the term was hard to discover, as its definition and explanation were in a very long document lacking an overview section. search did not help because it occurs so often. - clarify wording in the definition - add an overview of installable types - add "installable" to glossary - link to definition from occurrences of the term - be more precise about where store derivation outputs are processed - installable Nix expressions must evaluate to a derivation Co-authored-by: Adam Joseph <54836058+amjoseph-nixpkgs@users.noreply.github.com> | |||
| 2022-09-22 | Dodge "trusted" vs "trustworthy" by being explicit | John Ericson | |
| Hopefully this is best! | |||
| 2022-09-22 | "valid signature" -> "trustworthy signature" | John Ericson | |
| I just had a colleague get confused by the previous phrase for good reason. "valid" sounds like an *objective* criterion, e.g. and *invalid signature* would be one that would be trusted by no one, e.g. because it misformatted or something. What is actually going is that there might be a signature which is perfectly valid to *someone else*, but not to the user, because they don't trust the corresponding public key. This is a *subjective* criterion, because it depends on the arbitrary and personal choice of which public keys to trust. I therefore think "trustworthy" is a better adjective to use. Whether something is worthy of trust is clearly subjective, and then "trust" within that word nicely evokes `trusted-public-keys` and friends. | |||
| 2022-03-24 | Rename 'nix store make-content-addressable' to 'nix store ↵ | Eelco Dolstra | |
| make-content-addressed' | |||
 |
index : lix | |
| User & |
| aboutsummaryrefslogtreecommitdiff |