summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
diff options
context:
space:
mode:
authorWolfgang Walther <walther@technowledgy.de>2025-09-01 19:23:56 +0200
committerWolfgang Walther <walther@technowledgy.de>2025-09-01 19:23:56 +0200
commitc4a5576f7bdd10916321d8d580881368f7fe9f85 (patch)
tree4cab9aa6b4028502317c219f07e03a268c430164 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
parente0b7b232b1ba63b515f9764e295fa2795d7861aa (diff)
haskellPackages.llvm-ffi: always use default LLVM version
The previous approach of selecting the highest possible LLVM version brought complications, especially when the latest LLVM release candidate was properly released and the llvm-ffi version on master didn't support this properly, yet. This would result in an eval failure that was impossible to properly solve on master. We only introduced the logic of selecting the latest LLVM version, because we didn't know about the cabal flags supporting lower LLVM versions at first. We then stuck with this approach. However, we can also just always use the default LLVM version that is present in `llvmPackages`. This is more in the spirit of a *default* version anyway. This will not result in any eval failures / warnings. There is only one failure mode: `haskellPackages.llvm-ffi` not supporting the new default LLVM version. In this case it's perfectly fine to wait for an update of llvm-ffi via `haskell-updates`.
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions