diff options
| author | github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> | 2024-02-23 00:12:05 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-23 00:12:05 +0000 |
| commit | c1d60ca8ac07faecb101ddd13bdec8cec6cd9964 (patch) | |
| tree | c7beb84a37435733a43acd2f39388b4e9eedae97 /doc | |
| parent | 3508418a671c4cdbea40e01ef676b548cfed9448 (diff) | |
| parent | 1288512729166dd4ad72ff9b73b61858ec6d787d (diff) | |
Merge master into haskell-updates
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/build-helpers/fetchers.chapter.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/build-helpers/fetchers.chapter.md b/doc/build-helpers/fetchers.chapter.md index 7bd1bbd6de029..ad2378fd0e742 100644 --- a/doc/build-helpers/fetchers.chapter.md +++ b/doc/build-helpers/fetchers.chapter.md @@ -80,6 +80,10 @@ stdenv.mkDerivation { The main difference between `fetchurl` and `fetchzip` is in how they store the contents. `fetchurl` will store the unaltered contents of the URL within the Nix store. `fetchzip` on the other hand, will decompress the archive for you, making files and directories directly accessible in the future. `fetchzip` can only be used with archives. Despite the name, `fetchzip` is not limited to .zip files and can also be used with any tarball. +Additional parameters to `fetchurl`: +- `downloadToTemp`: Defaults to `false`. If `true`, saves the source to `$downloadedFile`, to be used in conjunction with `postFetch` +- `postFetch`: Shell code executed after the file has been fetched successfully. Use it for postprocessing, to check or transform the file. + ## `fetchpatch` {#fetchpatch} `fetchpatch` works very similarly to `fetchurl` with the same arguments expected. It expects patch files as a source and performs normalization on them before computing the checksum. For example, it will remove comments or other unstable parts that are sometimes added by version control systems and can change over time. |