Some words from your Tweag Nix Team since the last update:
Despite a lot of conflicting stuff, @edolstra kept working on the source tree abstraction pull-request, helped by some testing by @layus and others. Amongst other things, this will fix some issues with subflakes and doesn’t break the evaluation cache anymore.
In addition, that branch also contains a new
builtins.patchprimop to apply patches independently.
nix-copy-closureused to parallelize the copy to make it faster, this optimization got removed in nix#5048 to allow batching the copy in the
There was however no real reason for not keeping both, so @thufschmitt and @ConnorBaker opened a pull-request to change this (nix#6612).
@mkaito started working towards fixing nix#5509, hopefully bringing back the possiblity of having fixed-output derivations with references – or at the very least having a nice message if Nix encounters one of these, with some pointer to a possible workaround.
@cole-h (from Determinate Systems) updated the
nixpkgsversion used by Nix. This accidentally broke the Darwin build because of a check that ensured that
boostwasn’t included in the runtime closure. @edolstra fixed it (nix#6630).
An annoying quirk of the remote build implementation is that it generally won’t work out-of-the-box with non-NixOS builders (nix#1078). @balsoft opened a pull request to fix most instances of this issue (nix#6628).
@fricklerhandwerk compiled detailed statistics on the 2022 community survey (extending the summary from 2022 Nix Survey Results) and continued his ongoing usability study to direct the planned efforts to improve documentation.
@YorikSar tried to make it easy to build and run a NixOS vm from MacOS.
After a bit of trial-and-error and some patching, he managed to do it with a custom
nixpkgsfrom here, bringing a fix for nixpkgs#108984.
@thufschmitt published a new
And that’s all, folks