My personal project and infrastructure archive
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
|
|
# Release 22.05 (“Quokka”, 2022.05/??) {#sec-release-22.05}
|
|
|
|
|
|
|
|
|
|
In addition to numerous new and upgraded packages, this release has the following highlights:
|
|
|
|
|
|
|
|
|
|
- Support is planned until the end of December 2022, handing over to 22.11.
|
|
|
|
|
|
|
|
|
|
## Highlights {#sec-release-22.05-highlights}
|
|
|
|
|
|
|
|
|
|
## New Services {#sec-release-22.05-new-services}
|
|
|
|
|
|
|
|
|
|
## Backward Incompatibilities {#sec-release-22.05-incompatibilities}
|
|
|
|
|
|
|
|
|
|
* `pkgs.ghc` now refers to `pkgs.targetPackages.haskellPackages.ghc`.
|
|
|
|
|
This *only* makes a difference if you are cross-compiling and will
|
|
|
|
|
ensure that `pkgs.ghc` always runs on the host platform and compiles
|
|
|
|
|
for the target platform (similar to `pkgs.gcc` for example).
|
|
|
|
|
`haskellPackages.ghc` still behaves as before, running on the build
|
|
|
|
|
platform and compiling for the host platform (similar to `stdenv.cc`).
|
|
|
|
|
This means you don't have to adjust your derivations if you use
|
|
|
|
|
`haskellPackages.callPackage`, but when using `pkgs.callPackage` and
|
|
|
|
|
taking `ghc` as an input, you should now use `buildPackages.ghc`
|
|
|
|
|
instead to ensure cross compilation keeps working (or switch to
|
|
|
|
|
`haskellPackages.callPackage`).
|
|
|
|
|
|
|
|
|
|
## Other Notable Changes {#sec-release-22.05-notable-changes}
|
