From d84b2f136595de469e66ef5350af2409c65eee0d Mon Sep 17 00:00:00 2001 From: sternenseemann Date: Thu, 11 Sep 2025 15:39:31 +0200 Subject: [PATCH] doc/rl-2511: note removal of llvmPackages from haskell.packages.* This should be the only observable breakage from #441101 / 921f5db2989cb95dc5b24bb75fb74f7b7f54e535. --- doc/release-notes/rl-2511.section.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/release-notes/rl-2511.section.md b/doc/release-notes/rl-2511.section.md index 119baa4d1837..494193a145f3 100644 --- a/doc/release-notes/rl-2511.section.md +++ b/doc/release-notes/rl-2511.section.md @@ -34,6 +34,12 @@ The latter was probably broken anyway. If there is interest in restoring support for these architectures, it should be possible to cross‐compile a bootstrap GHC binary. +- `haskellPackages` and the package sets under `haskell.packages` no longer expose an `llvmPackages` attribute, + though it can still be accessed via `ghc.llvmPackages` (from the same package set). + Haskell packages usually only need to depend on an LLVM version matching GHC if they force the use the LLVM + backend even if NCG is available. In this case, it is best to use the `forceLlvmCodegenBackend` helper. + In all other cases, like linking against `libLLVM`, Haskell packages should use the appropriate version of `llvmPackages` from `pkgs`. + - `base16-builder` node package has been removed due to lack of upstream maintenance. - `python3Packages.bjoern` has been removed, as the upstream is unmaintained and it depends on a 14-year-old version of http-parser with numerous vulnerabilities.