@andir yes, indeed. However fetchpatch and fetchurl depends on curl, so using these will create a circular dependency. That's the reason I did add it manually in this case.

infinite recursion encountered, at undefined position

@andir yes, indeed. However fetchpatch and fetchurl depends on curl, so using these will create a circular dependency. That's the reason I did add it manually in this case.

infinite recursion encountered, at undefined position

fetchurl uses a "special" version of curl that transparently uses stdenv.fetchurlBoot as fetchurl so it should be fine.

See: https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/all-packages.nix#L264-L296

fetchurl uses a "special" version of curl that transparently uses stdenv.fetchurlBoot as fetchurl so it should be fine.

Ah, ok. I might be doing something wrong, see: https://gist.github.com/mmahut/5390f0e6ab1528274404b24a0337438c

I see. That might just be because something int he dependency chain of fetchpatch requires something that isn't handled in that override. fetchurl should be fine for the patch, no?

@andir you are right, fetchurl does the trick :)

Well, hopefully it will last long enough. The point of using fetchpatch is that from time to time the patches generated dynamically change in insignificant details. (When they upgrade git or something.)