aboutsummaryrefslogtreecommitdiff
path: root/pkgs/build-support/fetchpatch (follow)
Commit message (Collapse)AuthorAgeFilesLines
* fetchpatch: Allow using base64-encoded hashJan Tojnar2020-03-021-1/+5
| | | | | | | | Nix now returns base64-encoded SRI hashes on hash mismatch. Usually, people copy the returned hashes in TOFU fashion but since base64-encoded strings can contain slashes, they often broke our use of them for temporary file name. Escaping them should prevent the failures.
* fetchpatch: explain why we use 0.3.3Vladimír Čunát2019-05-121-0/+1
|
* fetchpatch: explicitly use patchutils 0.3.3Bob van der Linden2019-04-131-4/+7
|
* fetchpatch: patchutils -> buildPackages.patchutilsvolth2018-08-211-5/+5
|
* fetchpatch: add option to revert a patchTimo Kaufmann2018-07-161-4/+7
|
* fetchpatch: fail on empty patchTimo Kaufmann2018-07-151-0/+18
| | | | | | | | | | Since this is probably never the desired case and has led to actual issues, see the comments at: https://github.com/NixOS/nixpkgs/commit/af1313e91552e42a4419b396b3026319c60fc17f This might also happen when pulling a patch from GitHub or a similar web interface without explicitly selecting the "raw" format.
* fetchpatch: escape excludes and includesTimo Kaufmann2018-07-151-2/+2
| | | | | | | | | Excludes and includes are implemented by passing the parameters to the respective flags of `filterdiff`. Those were passed unescaped until now. Since those flags expect patterns (similar to shell globs), something like `/some/path/*` might be used to exclude or include all files in some path. Without escaping the shell would expand the `*`, leading to unexpected behaviour.
* fetchpatch: Add includes to compliment excludes, and require that both not ↵John Ericson2018-07-151-2/+4
| | | | | | | | be non-empty. This commit was originally introduced as part of #41420 and then reverted with the rest of that PR. However there was no reason to revert his particular commit.
* Revert "haskell generic-builder: Use strictDeps always"Peter Simons2018-07-041-4/+2
|
* fetchpatch: Add includes to compliment excludes, and require that both not ↵John Ericson2018-07-021-2/+4
| | | | be non-empty.
* fetchpatch: Add support for an arbitrary extra prefixJohn Ericson2018-01-181-5/+5
| | | | | | We still ensure the old and new ones start, respectfully, with `a/` and `b/`. Use with `stripLen` to ensure tha the old `a/` and `/b` are gone if a new prefix is added.
* fetchpatch: allow callers to specify postFetch sensiblyDan Peebles2017-10-031-1/+1
| | | | | Before this fix, it seemed to be trying to merge our postFetch with the patch normalization logic, but accidentally clobbering the whole thing with the passed-in value.
* fetchpatch: add excludes parameterRobin Gloster2017-07-261-3/+6
|
* fetchpatch: add addPrefixes argumentFranz Pletz2016-07-291-3/+7
| | | | | | | | | | | Sometimes patches start without a leading prefix. We default to strip one prefix or path component from patches (-p1) in the patchPhase in stdenv. As all patches should therefore be in this format, fetchpatch should have an option to normalize patch paths. This commit introduces a new argument to fetchpatch called addPrefixes that adds one patch prefix to the old and new paths in a patch before putting it into the store.
* fetchpatch: Allow to pass a postFetch attribute.aszlig2015-06-231-0/+1
| | | | | | | | | | Comes in handy if we want to make additional modificiations to the output file. While I wasn't sure whether to invoke the passed postFetch directly before the patch or afterwards, I thought it would be better afterwards because "postFetch of fetchpatch" at least to my intuition would sound that after whatever "fetchpatch" does - it comes afterwards. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
* Patches for a lot of packages for GHC 7.10Joel Taylor2015-02-221-1/+1
|
* Merge #2630: add and use fetchpatchVladimír Čunát2014-05-171-0/+22
fetchpatch is fetchurl that determinizes the patch. Some parts of generated patches change from time to time, e.g. see #1983 and http://comments.gmane.org/gmane.linux.distributions.nixos/12815 Using fetchpatch should prevent the hash from changing. Conflicts (auto-solved): pkgs/development/libraries/haskell/gitit/default.nix