| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
doc: reword documentation conventions
|
|
* doc: improve documentation for trivial text writing functions
Co-authored-by: Brian Merchant <bzm3r@proton.me>
Co-authored-by: Robert Hensing <robert@roberthensing.nl>
Co-authored-by: Alexander Groleau <alex@proof.construction>
Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
|
|
|
|
|
|
|
|
multiple example sections, test first writeTextFile example (it was broken, heh) and fix, move prose out of code blocks
|
|
Co-authored-by: Alexander Groleau <alex@proof.construction>
|
|
Co-authored-by: Alexander Groleau <alex@proof.construction>
|
|
|
|
doc: extend Go documentation
|
|
nginx: change etags for statically compressed files served from store
|
|
|
|
Per RFC 9110, [section 8.8.1][1], different representations of the same
resource should have different Etags:
> A strong validator is unique across all versions of all
> representations associated with a particular resource over time.
> However, there is no implication of uniqueness across representations
> of different resources (i.e., the same strong validator might be in
> use for representations of multiple resources at the same time and
> does not imply that those representations are equivalent)
When serving statically compressed files (ie, when there is an existing
corresponding .gz/.br/etc. file on disk), Nginx sends the Etag marked
as strong. These tags should be different for each compressed format
(as shown in an explicit example in section [8.8.3.3][2] of the RFC).
Upstream Etags are composed of the file modification timestamp and
content length, and the latter generally changes between these
representations.
Previous implementation of Nix-specific Etags for things served from
store used the store hash. This is fine to share between different
files, but it becomes a problem for statically compressed versions of
the same file, as it means Nginx was serving different representations
of the same resource with the same Etag, marked as strong.
This patch addresses this by imitating the upstream Nginx behavior, and
appending the value of content length to the store hash.
[1]: https://www.rfc-editor.org/rfc/rfc9110.html#name-validator-fields
[2]:
https://www.rfc-editor.org/rfc/rfc9110.html#name-example-entity-tags-varying
|
|
|
|
|
|
|
|
https://github.com/NixOS/nixpkgs/pull/277534/files#r1450959283
|
|
https://github.com/NixOS/nixpkgs/pull/277534#discussion_r1450778530
|
|
Co-authored-by: Brian Merchant <bzm3r@proton.me>
|
|
|
|
|
|
doc-trivial-builders-writetext
|
|
lualatex assumes a writeable font cache relative to `$HOME`, for nix this has two implications.
First, the cache might diverge from the nix store if users use LuaLaTeX.
Second, `$HOME` needs to be set to a writable path in derivations.
|
|
|
|
|
|
... following suggestions from @phip1611 and @infinisil.
|
|
All other functions are in the form of `*{c,C}heckpointBuild*`, so we
deprecate the `mkCheckpointedBuild` function in favor of `mkCheckpointBuild`.
Also address some inconsistencies in the docs: some `buildOutput` should
actually be `incrementalBuildArtifacts`.
|
|
dart: Use Nix instead of Pub
|
|
|
|
|
|
|
|
It is fine to use `with` on the inputs, since that increases the
overall readability of the package.
Removes `wheel` from `nativeBuildInputs`, since it is a result of
cargo culting from an earlier setuptools example, that was wrong, and
it is not required, since it is provided by setuptools itself.
|
|
doc: update mkBinaryCache section with admonitions and conventions
|
|
|
|
The python-updates branch was formerly called python-unstable, but the
new branch name was never mentioned in the docs. This commit changes the
branch name in the docs to python-updates.
|
|
|
|
We get a dependency list with pub2nix now. We can no longer easily distinguish between development dependency dependencies and regular dependency dependencies, but we weren't doing this anyway.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The mkBinaryCache section now follows the convention of using one
line per sentence, as well as using admonitions for notes and
examples.
The example syntax was updated to define a fully-working nix package.
|
|
The following changes are made:
- Document how `wrapType2` and `wrapType1` are the same thing.
- Expand on how `wrapType2` works and additional arguments it uses.
- Document `extract` and show how it's used in combination with
`wrapType2`.
- Provide full working examples using the new admonition syntax.
|
|
Golang docs: remove "-s" and "-w" from the ldflags example
|
|
doc: diagram explaining what it means for a dependency to be propagated
|
|
|
|
|
