3.9 KiB
Release 22.05 (“Quokka”, 2022.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
New Services
-
aesmd, the Intel SGX Architectural Enclave Service Manager. Available as services.aesmd.
-
filebeat, a lightweight shipper for forwarding and centralizing log data. Available as services.filebeat.
Backward Incompatibilities
-
pkgs.ghcnow refers topkgs.targetPackages.haskellPackages.ghc. This only makes a difference if you are cross-compiling and will ensure thatpkgs.ghcalways runs on the host platform and compiles for the target platform (similar topkgs.gccfor example).haskellPackages.ghcstill behaves as before, running on the build platform and compiling for the host platform (similar tostdenv.cc). This means you don't have to adjust your derivations if you usehaskellPackages.callPackage, but when usingpkgs.callPackageand takingghcas an input, you should now usebuildPackages.ghcinstead to ensure cross compilation keeps working (or switch tohaskellPackages.callPackage). -
pkgs.emacsPackages.orgPackagesis removed because org elpa is deprecated. The packages in the top level ofpkgs.emacsPackages, such as org and org-contrib, refer to the ones inpkgs.emacsPackages.elpaPackagesandpkgs.emacsPackages.nongnuPackageswhere the new versions will release. -
The
wafHookhook now honorsNIX_BUILD_CORESwhenenableParallelBuildingis not set explicitly. Packages can restore the old behaviour by settingenableParallelBuilding=false. -
pkgs.claws-mail-gtk2, representing Claws Mail's older release version three, was removed in order to get rid of Python 2. Please switch toclaws-mail, which is Claws Mail's latest release based on GTK+3 and Python 3. -
The
writers.writePython2and correspondingwriters.writePython2Binconvenience functions to create executable Python 2 scripts in the store were removed in preparation of removal of the Python 2 interpreter. Scripts have to be converted to Python 3 for use withwriters.writePython3orwriters.writePyPy2needs to be used.
Other Notable Changes
-
The option services.redis.servers was added to support per-application
redis-serverwhich is more secure since Redis databases are only mere key prefixes without any configuration or ACL of their own. Backward-compatibility is preserved by mapping oldservices.redis.settingstoservices.redis.servers."".settings, but you are strongly encouraged to name eachredis-serverinstance after the application using it, instead of keeping that nameless one. Except for the namelessservices.redis.servers.""still accessible at127.0.0.1:6379, and to the members of the Unix groupredisthrough the Unix socket/run/redis/redis.sock, all otherservices.redis.servers.${serverName}are only accessible by default to the members of the Unix groupredis-${serverName}through the Unix socket/run/redis-${serverName}/redis.sock. -
The
writers.writePyPy2/writers.writePyPy3and correspondingwriters.writePyPy2Bin/writers.writePyPy3Binconvenience functions to create executable Python 2/3 scripts using the PyPy interpreter were added. -
The
influxdb2package was split intoinfluxdb2-serverandinfluxdb2-cli, matching the split that took place upstream. A combinedinfluxdb2package is still provided in this release for backwards compatibilty, but will be removed at a later date.