chore(libmain): license it under LGPL-2.1-only

Progress towards REUSE compliance.

Change-Id: I2991234cfd193773a377d2f1735b9974918b8138
Signed-off-by: Raito Bezarius <raito@lix.systems>

.envrc

@@ -1,9 +1,5 @@
 # shellcheck shell=bash
 source_env_if_exists .envrc.local
-# TODO: `use flake .#native-clangStdenvPackages` on macOS?
-use flake ".#${LIX_SHELL_VARIANT:-default}" "${LIX_SHELL_EXTRA_ARGS[@]}"
-export MAKEFLAGS="$MAKEFLAGS -e"
-if [[ -n "$NIX_BUILD_CORES" ]]; then
-    export MAKEFLAGS="$MAKEFLAGS -j $NIX_BUILD_CORES"
-fi
+# Use native-clangStdenvPackages to get clangd by default.
+use flake ".#${LIX_SHELL_VARIANT:-native-clangStdenvPackages}" "${LIX_SHELL_EXTRA_ARGS[@]}"
 export GTEST_BRIEF=1

.this-is-lix

@@ -0,0 +1 @@
+This is a file used by the dev shell shellHook in package.nix to check that this is actually a Lix repo before installing git hooks. Its contents have no meaning.

doc/manual/change-authors.yml

@@ -3,6 +3,10 @@
 #
 # It's used for crediting people accurately in release notes. The release notes
 # script will link to forgejo, then to GitHub if forgejo is not present.
+#
+# When adding someone from outside the Lix project, you generally want to simply link their GitHub profile without adding a display name unless they are well-known in the community by that display name.
+#
+# See doc/manual/src/contributing/hacking.md for more documentation on this file's format and typical usage.
 9999years:
   display_name: wiggles
   forgejo: rbt
@@ -40,6 +44,11 @@ cole-h:
   display_name: Cole Helbling
   github: cole-h
 
+delan:
+  display_name: delan
+  forgejo: delan
+  github: delan
+
 edolstra:
   display_name: Eelco Dolstra
   github: edolstra
@@ -60,6 +69,10 @@ jade:
   forgejo: jade
   github: lf-
 
+kloenk:
+  forgejo: kloenk
+  github: kloenk
+
 lovesegfault:
   github: lovesegfault
 
@@ -83,6 +96,10 @@ puck:
   forgejo: puck
   github: puckipedia
 
+quantumjump:
+  display_name: Quantum Jump
+  github: QuantumBJump
+
 r-vdp:
   github: r-vdp
 

doc/manual/meson.build

@@ -110,6 +110,7 @@ manual = custom_target(
     builtins_md,
     builtin_constants_md,
     rl_next_generated,
+    nix,
   ],
   output : [
     'manual',
@@ -186,6 +187,7 @@ foreach command : nix_nested_manpages
       ],
       input : [
         manual_md,
+        nix,
       ],
       output : command[0] + '-' + page + '.1',
       install : true,
@@ -298,6 +300,7 @@ foreach page : nix3_manpages
     input : [
       'render-manpage.sh',
       manual_md,
+      nix,
     ],
     output : page + '.1',
     install : true,
@@ -341,6 +344,7 @@ foreach entry : nix_manpages
       'render-manpage.sh',
       manual_md,
       entry.get(3, []),
+      nix,
     ],
     output : '@0@.@1@'.format(entry[0], entry[1]),
     install : true,

doc/manual/process-includes.sh

@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/usr/bin/env bash
 
 set -euo pipefail
 

doc/manual/render-manpage.sh

@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/usr/bin/env bash
 
 set -euo pipefail
 

doc/manual/rl-next/addDrvOutputDependencies.md

@@ -1,14 +0,0 @@
----
-synopsis: "Add a builtin `addDrvOutputDependencies`"
-prs: 9216
-issues: 7910
-credits: [ericson, horrors]
-category: Features
----
-
-This builtin allows taking a `drvPath`-like string and turning it into a string
-with context such that, when it lands in a derivation, it will create
-dependencies on *all the outputs* in its closure (!). Although `drvPath` does this
-today, this builtin starts forming a path to migrate to making `drvPath` have a
-more normal and less surprising string context behaviour (see linked issue and
-PR for more details).

doc/manual/rl-next/always-allow-substitutes.md

@@ -1,13 +0,0 @@
----
-synopsis: "Add an option `always-allow-substitutes` to ignore `allowSubstitutes` in derivations"
-prs: 8047
-credits: [lovesegfault, horrors]
-category: Improvements
----
-
-You can set this setting to force a system to always allow substituting even
-trivial derivations like `pkgs.writeText`. This is useful for
-[`nix-fast-build --skip-cached`][skip-cached] and similar to be able to also
-ignore trivial derivations.
-
-[skip-cached]: https://github.com/Mic92/nix-fast-build?tab=readme-ov-file#avoiding-redundant-package-downloads

doc/manual/rl-next/better-attrpath-errors.md

@@ -0,0 +1,90 @@
+---
+synopsis: "Trace which part of a `foo.bar.baz` expression errors"
+cls: 1505, 1506
+credits: Qyriad
+category: Improvements
+---
+
+Previously, if an attribute path selection expression like `linux_4_9.meta.description` it wouldn't show you which one of those parts in the attribute path, or even that that line of code is what caused evaluation of the failing expression.
+The previous error looks like this:
+
+```
+pkgs.linuxKernel.kernels.linux_4_9.meta.description
+
+error:
+       … while evaluating the attribute 'linuxKernel.kernels.linux_4_9.meta.description'
+         at /nix/store/dk2rpyb6ndvfbf19bkb2plcz5y3k8i5v-source/pkgs/top-level/linux-kernels.nix:278:5:
+          277|   } // lib.optionalAttrs config.allowAliases {
+          278|     linux_4_9 = throw "linux 4.9 was removed because it will reach its end of life within 22.11";
+             |     ^
+          279|     linux_4_14 = throw "linux 4.14 was removed because it will reach its end of life within 23.11";
+
+       … while calling the 'throw' builtin
+         at /nix/store/dk2rpyb6ndvfbf19bkb2plcz5y3k8i5v-source/pkgs/top-level/linux-kernels.nix:278:17:
+          277|   } // lib.optionalAttrs config.allowAliases {
+          278|     linux_4_9 = throw "linux 4.9 was removed because it will reach its end of life within 22.11";
+             |                 ^
+          279|     linux_4_14 = throw "linux 4.14 was removed because it will reach its end of life within 23.11";
+
+       error: linux 4.9 was removed because it will reach its end of life within 22.11
+```
+
+Now, the error will look like this:
+
+```
+pkgs.linuxKernel.kernels.linux_4_9.meta.description
+
+error:
+       … while evaluating the attribute 'linuxKernel.kernels.linux_4_9.meta.description'
+         at /nix/store/dk2rpyb6ndvfbf19bkb2plcz5y3k8i5v-source/pkgs/top-level/linux-kernels.nix:278:5:
+          277|   } // lib.optionalAttrs config.allowAliases {
+          278|     linux_4_9 = throw "linux 4.9 was removed because it will reach its end of life within 22.11";
+             |     ^
+          279|     linux_4_14 = throw "linux 4.14 was removed because it will reach its end of life within 23.11";
+
+       … while evaluating 'pkgs.linuxKernel.kernels.linux_4_9' to select 'meta' on it
+         at «string»:1:1:
+            1| pkgs.linuxKernel.kernels.linux_4_9.meta.description
+             | ^
+
+       … caused by explicit throw
+         at /nix/store/dk2rpyb6ndvfbf19bkb2plcz5y3k8i5v-source/pkgs/top-level/linux-kernels.nix:278:17:
+          277|   } // lib.optionalAttrs config.allowAliases {
+          278|     linux_4_9 = throw "linux 4.9 was removed because it will reach its end of life within 22.11";
+             |                 ^
+          279|     linux_4_14 = throw "linux 4.14 was removed because it will reach its end of life within 23.11";
+
+       error: linux 4.9 was removed because it will reach its end of life within 22.11
+```
+
+Not only does the line of code that referenced the failing attribute show up in the trace, it also tells you that it was specifically the `linux_4_9` part that failed.
+
+This includes if the failing part is a top-level binding:
+
+```
+let
+  inherit (pkgs.linuxKernel.kernels) linux_4_9;
+in linux_4_9.meta.description
+error:
+       … while evaluating 'linux_4_9' to select 'meta.description' on it
+         at «string»:3:4:
+            2|   inherit (pkgs.linuxKernel.kernels) linux_4_9;
+            3| in linux_4_9.meta.description
+             |    ^
+
+       … while evaluating the attribute 'linux_4_9'
+         at /nix/store/dk2rpyb6ndvfbf19bkb2plcz5y3k8i5v-source/pkgs/top-level/linux-kernels.nix:278:5:
+          277|   } // lib.optionalAttrs config.allowAliases {
+          278|     linux_4_9 = throw "linux 4.9 was removed because it will reach its end of life within 22.11";
+             |     ^
+          279|     linux_4_14 = throw "linux 4.14 was removed because it will reach its end of life within 23.11";
+
+       … caused by explicit throw
+         at /nix/store/dk2rpyb6ndvfbf19bkb2plcz5y3k8i5v-source/pkgs/top-level/linux-kernels.nix:278:17:
+          277|   } // lib.optionalAttrs config.allowAliases {
+          278|     linux_4_9 = throw "linux 4.9 was removed because it will reach its end of life within 22.11";
+             |                 ^
+          279|     linux_4_14 = throw "linux 4.14 was removed because it will reach its end of life within 23.11";
+
+       error: linux 4.9 was removed because it will reach its end of life within 22.11
+```

doc/manual/rl-next/better-errors-in-nix-repl.md

@@ -1,42 +0,0 @@
----
-synopsis: Concise error printing in `nix repl`
-prs: 9928
-cls: 811
-category: Improvements
-credits: 9999years
----
-
-Previously, if an element of a list or attribute set threw an error while
-evaluating, `nix repl` would print the entire error (including source location
-information) inline. This output was clumsy and difficult to parse:
-
-```
-nix-repl> { err = builtins.throw "uh oh!"; }
-{ err = «error:
-       … while calling the 'throw' builtin
-         at «string»:1:9:
-            1| { err = builtins.throw "uh oh!"; }
-             |         ^
-
-       error: uh oh!»; }
-```
-
-Now, only the error message is displayed, making the output much more readable.
-```
-nix-repl> { err = builtins.throw "uh oh!"; }
-{ err = «error: uh oh!»; }
-```
-
-However, if the whole expression being evaluated throws an error, source
-locations and (if applicable) a stack trace are printed, just like you'd expect:
-
-```
-nix-repl> builtins.throw "uh oh!"
-error:
-       … while calling the 'throw' builtin
-         at «string»:1:1:
-            1| builtins.throw "uh oh!"
-             | ^
-
-       error: uh oh!
-```

doc/manual/rl-next/build-dir.md

@@ -0,0 +1,12 @@
+---
+synopsis: "Add a `build-dir` setting to set the backing directory for builds"
+cls: 1514
+credits: [roberth, tomberek]
+category: Improvements
+---
+
+`build-dir` can now be set in the Nix configuration to choose the backing directory for the build sandbox.
+This can be useful on systems with `/tmp` on tmpfs, or simply to relocate large builds to another disk.
+
+Also, `XDG_RUNTIME_DIR` is no longer considered when selecting the default temporary directory,
+as it's not intended to be used for large amounts of data.

doc/manual/rl-next/build-timing-analysis.md

@@ -1,22 +0,0 @@
----
-synopsis: Clang build timing analysis
-cls: 587
-category: Development
----
-
-We now have Clang build profiling available, which generates Chrome
-tracing files for each compilation unit. To enable it, run `meson configure
-build -Dprofile-build=enabled` in a Clang stdenv (`nix develop
-.#native-clangStdenvPackages`) then rerun the compilation.
-
-If you want to make the build go faster, do a clang build with meson, then run
-`maintainers/buildtime_report.sh build`, then contemplate how to improve the
-build time.
-
-You can also look at individual object files' traces in
-<https://ui.perfetto.dev>.
-
-See [the wiki page][improving-build-times-wiki] for more details on how to do
-this.
-
-[improving-build-times-wiki]: https://wiki.lix.systems/link/8#bkmrk-page-title

doc/manual/rl-next/consistent-nix-build.md

@@ -1,9 +0,0 @@
----
-synopsis: Show all FOD errors with `nix build --keep-going`
-credits: [ma27]
-category: Improvements
-cls: [1108]
----
-
-`nix build --keep-going` now behaves consistently with `nix-build --keep-going`. This means
-that if e.g. multiple FODs fail to build, all hash mismatches are displayed.

doc/manual/rl-next/cve-fod-fix.md

@@ -1,21 +0,0 @@
----
-synopsis: "Fix CVE-2024-27297 (GHSA-2ffj-w4mj-pg37)"
-cls: 266
-credits: [puck, jade, thufschmitt, tomberek, valentin]
-category: Fixes
----
-
-Since Lix fixed-output derivations run in the host network namespace (which we
-wish to change in the future, see
-[lix#285](https://git.lix.systems/lix-project/lix/issues/285)), they may open
-abstract-namespace Unix sockets to each other and to programs on the host. Lix
-contained a now-fixed time-of-check/time-of-use vulnerability where one
-derivation could send writable handles to files in their final location in the
-store to another over an abstract-namespace Unix socket, exit, then the other
-derivation could wait for Lix to hash the paths and overwrite them.
-
-The impact of this vulnerability is that two malicious fixed-output derivations
-could create a poisoned path for the sources to Bash or similarly important
-software containing a backdoor, leading to local privilege execution.
-
-CppNix advisory: https://github.com/NixOS/nix/security/advisories/GHSA-2ffj-w4mj-pg37

doc/manual/rl-next/debugger-locals-for-let-expressions.md

@@ -1,11 +0,0 @@
----
-synopsis: "`--debugger` can now access bindings from `let` expressions"
-prs: 9918
-issues: 8827
-category: Fixes
-credits: 9999years
----
-
-Breakpoints and errors in the bindings of a `let` expression can now access
-those bindings in the debugger. Previously, only the body of `let` expressions
-could access those bindings.

doc/manual/rl-next/debugger-on-trace.md

@@ -1,11 +0,0 @@
----
-synopsis: Enter the `--debugger` when `builtins.trace` is called if `debugger-on-trace` is set
-prs: 9914
-category: Features
-credits: 9999years
----
-
-If the `debugger-on-trace` option is set and `--debugger` is given,
-`builtins.trace` calls will behave similarly to `builtins.break` and will enter
-the debug REPL. This is useful for determining where warnings are being emitted
-from.

doc/manual/rl-next/deprecate-online-flake-registry.md

@@ -1,16 +0,0 @@
----
-synopsis: "Deprecate the online flake registries and vendor the default registry"
-cls: 1127
-credits: midnightveil
-issues: [fj#183, fj#110, fj#116, 8953, 9087]
-category: Breaking Changes
----
-
-The online flake registry [https://channels.nixos.org/flake-registry.json](https://channels.nixos.org/flake-registry.json) is not pinned in any way,
-and the targets of the indirections can both update or change entirely at any
-point. Furthermore, it is refetched on every use of a flake reference, even if
-there is a local flake reference, and even if you are offline (which breaks).
-
-For now, we deprecate the (any) online flake registry, and vendor a copy of the
-current online flake registry. This makes it work offline, and ensures that
-it won't change in the future.

doc/manual/rl-next/distinguish-throw-errors.md

@@ -0,0 +1,70 @@
+---
+synopsis: "Distinguish between explicit throws and errors that happened while evaluating a throw"
+cls: 1511
+credits: Qyriad
+category: Improvements
+---
+
+Previously, errors caused by an expression like `throw "invalid argument"` were treated like an error that happened simply while some builtin function was being called:
+
+```
+let
+  throwMsg = p: throw "${p} isn't the right package";
+in throwMsg "linuz"
+
+error:
+       … while calling the 'throw' builtin
+         at «string»:2:17:
+            1| let
+            2|   throwMsg = p: throw "${p} isn't the right package";
+             |                 ^
+            3| in throwMsg "linuz"
+
+       error: linuz isn't the right package
+```
+
+But the error didn't just happen "while" calling the `throw` builtin — it's a throw error!
+Now it looks like this:
+
+```
+let
+  throwMsg = p: throw "${p} isn't the right package";
+in throwMsg "linuz"
+
+error:
+       … caused by explicit throw
+         at «string»:2:17:
+            1| let
+            2|   throwMsg = p: throw "${p} isn't the right package";
+             |                 ^
+            3| in throwMsg "linuz"
+
+       error: linuz isn't the right package
+```
+
+This also means that incorrect usage of `throw` or errors evaluating its arguments are easily distinguishable from explicit throws:
+
+```
+let
+  throwMsg = p: throw "${p} isn't the right package";
+in throwMsg { attrs = "error when coerced in string interpolation"; }
+
+error:
+       … while calling the 'throw' builtin
+         at «string»:2:17:
+            1| let
+            2|   throwMsg = p: throw "${p} isn't the right package";
+             |                 ^
+            3| in throwMsg { attrs = "error when coerced in string interpolation"; }
+
+       … while evaluating a path segment
+         at «string»:2:24:
+            1| let
+            2|   throwMsg = p: throw "${p} isn't the right package";
+             |                        ^
+            3| in throwMsg { attrs = "error when coerced in string interpolation"; }
+
+       error: cannot coerce a set to a string: { attrs = "error when coerced in string interpolation"; }
+```
+
+Here, instead of an actual thrown error, a type error happens first (trying to coerce an attribute set to a string), but that type error happened *while* calling `throw`.

doc/manual/rl-next/drop-vendored-toml11.md

@@ -1,9 +0,0 @@
----
-synopsis: Stop vendoring toml11
-cls: 675
-category: Packaging
-credits: winter
----
-
-We don't apply any patches to it, and vendoring it locks users into
-bugs (it hasn't been updated since its introduction in late 2021).

doc/manual/rl-next/drv-string-parse-hang.md

@@ -1,8 +0,0 @@
----
-synopsis: Fix handling of truncated `.drv` files.
-prs: 9673
-category: Fixes
-credits: horrors
----
-
-Previously a `.drv` that was truncated in the middle of a string would case nix to enter an infinite loop, eventually exhausting all memory and crashing.

doc/manual/rl-next/dup-attr-errors.md

@@ -1,24 +0,0 @@
----
-synopsis: Duplicate attribute reports are more accurate
-cls: 557
-credits: horrors
-category: Improvements
----
-
-Duplicate attribute errors are now more accurate, showing the path at which an error was detected rather than the full, possibly longer, path that caused the error.
-Error reports are now
-```ShellSession
-$ nix eval --expr '{ a.b = 1; a.b.c.d = 1; }'
-error: attribute 'a.b' already defined at «string»:1:3
-       at «string»:1:12:
-            1| { a.b = 1; a.b.c.d = 1;
-             |            ^
-```
-instead of
-```ShellSession
-$ nix eval --expr '{ a.b = 1; a.b.c.d = 1; }'
-error: attribute 'a.b.c.d' already defined at «string»:1:3
-       at «string»:1:12:
-            1| { a.b = 1; a.b.c.d = 1;
-             |            ^
-```

doc/manual/rl-next/empty-search-regex.md

@@ -1,8 +0,0 @@
----
-synopsis: Disallow empty search regex in `nix search`
-prs: 9481
-credits: [iFreilicht, horrors]
-category: Miscellany
----
-
-[`nix search`](@docroot@/command-ref/new-cli/nix3-search.md) now requires a search regex to be passed. To show all packages, use `^`.

doc/manual/rl-next/enable-coredumps.md

@@ -1,13 +0,0 @@
----
-synopsis: "Add an option `enable-core-dumps` that enables core dumps from builds"
-cls: 1088
-credits: midnightveil
-category: Features
----
-
-In the past, Lix disabled core dumps by setting the soft `RLIMIT_CORE` to 0
-unconditionally. Although this rlimit could be altered from the builder since
-it is just the soft limit, this was kind of annoying to do. By passing
-`--option enable-core-dumps true` to an offending build, one can now cause the
-core dumps to be handled by the system in the normal way (winding up in
-`coredumpctl`, say, on Linux).

doc/manual/rl-next/enter-debugger-more-reliably-in-let-and-calls.md

@@ -1,27 +0,0 @@
----
-synopsis: The `--debugger` will start more reliably in `let` expressions and function calls
-prs: 9917
-issues: 6649
-credits: [9999years, horrors]
-category: Fixes
----
-
-Previously, if you attempted to evaluate this file with the debugger:
-
-```nix
-let
-  a = builtins.trace "before inner break" (
-    builtins.break "hello"
-  );
-  b = builtins.trace "before outer break" (
-    builtins.break a
-  );
-in
-  b
-```
-
-Lix would correctly enter the debugger at `builtins.break a`, but if you asked
-it to `:continue`, it would skip over the `builtins.break "hello"` expression
-entirely.
-
-Now, Lix will correctly enter the debugger at both breakpoints.

doc/manual/rl-next/env-size-reduction.md

@@ -1,10 +0,0 @@
----
-synopsis: Reduce eval memory usage and wall time
-prs: 9658
-cls: 207
-credits: horrors
-category: Improvements
----
-
-Reduce the size of the `Env` struct used in the evaluator by a pointer, or 8 bytes on most modern machines.
-This reduces memory usage during eval by around 2% and wall time by around 3%.

doc/manual/rl-next/eval-system.md

@@ -1,14 +0,0 @@
----
-synopsis: Add new `eval-system` setting
-prs: 4093
-credits: [matthewbauer, horrors]
-category: Features
----
-
-Add a new `eval-system` option.
-Unlike `system`, it just overrides the value of `builtins.currentSystem`.
-This is more useful than overriding `system`, because you can build these derivations on remote builders which can work on the given system.
-In contrast, `system` also effects scheduling which will cause Lix to build those derivations locally even if that doesn't make sense.
-
-`eval-system` only takes effect if it is non-empty.
-If empty (the default) `system` is used as before, so there is no breakage.

doc/manual/rl-next/fchmodat2-sandbox.md

@@ -1,10 +0,0 @@
----
-synopsis: Creating setuid/setgid binaries with fchmodat2 is now prohibited by the build sandbox
-prs: 10501
-credits: ma27
-category: Fixes
----
-
-The build sandbox blocks any attempt to create setuid/setgid binaries, but didn't check
-for the use of the `fchmodat2` syscall which was introduced in Linux 6.6 and is used by
-glibc >=2.39. This is fixed now.

doc/manual/rl-next/fix-gc-dry-run.md

@@ -0,0 +1,29 @@
+---
+synopsis: Fix nix-collect-garbage --dry-run
+issues: [fj#432]
+cls: [1566]
+category: Fixes
+credits: [quantumjump]
+---
+
+`nix-collect-garbage --dry-run` did not previously give any output - it simply
+exited without even checking to see what paths would be deleted.
+
+```
+$ nix-collect-garbage --dry-run
+$
+```
+
+We updated the behaviour of the flag such that instead it prints out how many
+paths it *would* delete, but doesn't actually delete them.
+
+```
+$ nix-collect-garbage --dry-run
+finding garbage collector roots...
+determining live/dead paths...
+...
+<nix store paths>
+...
+2670 store paths deleted, 0.00MiB freed
+$
+```

doc/manual/rl-next/fix-nested-follows.md

@@ -1,24 +0,0 @@
----
-synopsis: Fix nested flake input `follows`
-prs: 6621
-cls: 994
-credits: [Kha, ma27]
-category: Fixes
-significance: significant
----
-
-Previously nested-input overrides were ignored; that is, the following did not
-override anything, in spite of the `nix3-flake` manual documenting it working:
-
-```
-{
-  inputs = {
-    foo.url = "github:bar/foo";
-    foo.inputs.bar.inputs.nixpkgs = "nixpkgs";
-  };
-}
-```
-
-This is useful to avoid the 1000 instances of nixpkgs problem without having
-each flake in the dependency tree to expose all of its transitive dependencies
-for modification.

doc/manual/rl-next/fix-silent-unknown-options.md

@@ -1,30 +0,0 @@
----
-synopsis: Warn on unknown settings anywhere in the command line
-prs: 10701
-credits: [cole-h]
-category: Improvements
----
-
-All `nix` commands will now properly warn when an unknown option is specified anywhere in the command line.
-
-Before:
-
-```console
-$ nix-instantiate --option foobar baz --expr '{}'
-warning: unknown setting 'foobar'
-$ nix-instantiate '{}' --option foobar baz --expr
-$ nix eval --expr '{}' --option foobar baz
-{ }
-```
-
-After:
-
-```console
-$ nix-instantiate --option foobar baz --expr '{}'
-warning: unknown setting 'foobar'
-$ nix-instantiate '{}' --option foobar baz --expr
-warning: unknown setting 'foobar'
-$ nix eval --expr '{}' --option foobar baz
-warning: unknown setting 'foobar'
-{ }
-```

doc/manual/rl-next/fod-failure-includes-url.md

@@ -0,0 +1,16 @@
+---
+synopsis: "Hash mismatch diagnostics for fixed-output derivations include the URL"
+cls: [1536]
+credits: [jade]
+category: Improvements
+---
+
+Now, when building fixed-output derivations, Lix will guess the URL that was used in the derivation using the `url` or `urls` properties in the derivation environment.
+This is a layering violation but making these diagnostics tractable when there are multiple instances of the `AAAA` hash is too significant of an improvement to pass it up.
+
+```
+error: hash mismatch in fixed-output derivation '/nix/store/sjfw324j4533lwnpmr5z4icpb85r63ai-x1.drv':
+        likely URL: https://meow.puppy.forge/puppy.tar.gz
+         specified: sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
+            got:    sha256-a1Qvp3FOOkWpL9kFHgugU1ok5UtRPSu+NwCZKbbaEro=
+```

doc/manual/rl-next/forbid-nested-debuggers.md

@@ -1,34 +0,0 @@
----
-synopsis: Nested debuggers are no longer supported
-prs: 9920
-credits: 9999years
-category: Improvements
----
-
-Previously, evaluating an expression that throws an error in the debugger would
-enter a second, nested debugger:
-
-```
-nix-repl> builtins.throw "what"
-error: what
-
-
-Starting REPL to allow you to inspect the current state of the evaluator.
-
-Welcome to Nix 2.18.1. Type :? for help.
-
-nix-repl>
-```
-
-Now, it just prints the error message like `nix repl`:
-
-```
-nix-repl> builtins.throw "what"
-error:
-       … while calling the 'throw' builtin
-         at «string»:1:1:
-            1| builtins.throw "what"
-             | ^
-
-       error: what
-```

doc/manual/rl-next/formal-order.md

@@ -1,9 +0,0 @@
----
-synopsis: consistent order of lambda formals in printed expressions
-prs: 9874
-credits: horrors
-category: Fixes
----
-
-Always print lambda formals in lexicographic order rather than the internal, creation-time based symbol order.
-This makes printed formals independent of the context they appear in.

doc/manual/rl-next/gc-roots-darwin.md

@@ -1,8 +0,0 @@
----
-synopsis: Find GC roots using libproc on Darwin
-cls: 723
-credits: artemist
-category: Improvements
----
-
-Previously, the garbage collector found runtime roots on Darwin by shelling out to `lsof -n -w -F n` then parsing the result. The version of `lsof` packaged in Nixpkgs is very slow on Darwin, so Lix now uses `libproc` directly to speed up GC root discovery, in some tests taking 250ms now instead of 40s.

doc/manual/rl-next/inherit-error-positions.md

@@ -1,8 +0,0 @@
----
-synopsis: fix duplicate attribute error positions for `inherit`
-prs: 9874
-credits: horrors
-category: Fixes
----
-
-When an inherit caused a duplicate attribute error, the position of the error was not reported correctly, placing the error with the inherit itself or at the start of the bindings block instead of the offending attribute name.

doc/manual/rl-next/inherit-from-by-need.md

@@ -1,9 +0,0 @@
----
-synopsis: "`inherit (x) ...` evaluates `x` only once"
-prs: 9847
-category: Fixes
-credits: horrors
----
-
-`inherit (x) a b ...` now evaluates the expression `x` only once for all inherited attributes rather than once for each inherited attribute.
-This does not usually have a measurable impact, but side-effects (such as `builtins.trace`) would be duplicated and expensive expressions (such as derivations) could cause a measurable slowdown.

doc/manual/rl-next/leading-period.md

@@ -1,12 +0,0 @@
----
-synopsis: Store paths are allowed to start with `.`
-issues: 912
-prs: [9867, 9091, 9095, 9120, 9121, 9122, 9130, 9219, 9224]
-credits: [roberth, horrors]
-category: Fixes
----
-
-Leading periods were allowed by accident in Nix 2.4. The Nix team has considered this to be a bug, but this behavior has since been relied on by users, leading to unnecessary difficulties.
-From now on, leading periods are officially, definitively supported. The names `.` and `..` are disallowed, as well as those starting with `.-` or `..-`.
-
-Nix versions that denied leading periods are documented [in the issue](https://github.com/NixOS/nix/issues/912#issuecomment-1919583286).

doc/manual/rl-next/linux-sandbox-consistency.md

@@ -1,12 +0,0 @@
----
-synopsis: Enforce syscall filtering and no-new-privileges on Linux
-cls: 1063
-category: Breaking Changes
-credits: alois31
----
-
-In order to improve consistency of the build environment, system call filtering and no-new-privileges are now unconditionally enabled on Linux.
-The `filter-syscalls` and `allow-new-privileges` options which could be used to disable these features under some circumstances have been removed.
-
-In order to support building on architectures without libseccomp support, the option to disable syscall filtering at build time remains.
-However, other uses of this option are heavily discouraged, since it would reduce the security of the sandbox substantially.

doc/manual/rl-next/macos-stack-size.md

@@ -1,9 +0,0 @@
----
-synopsis: Increase default stack size on macOS
-prs: 9860
-credits: 9999years
-category: Improvements
----
-
-Increase the default stack size on macOS to the same value as on Linux, subject to system restrictions to maximum stack size.
-This should reduce the number of stack overflow crashes on macOS when evaluating Nix code with deep call stacks.

doc/manual/rl-next/meson.md

@@ -1,15 +0,0 @@
----
-synopsis: Lix is built with meson
-# and many more
-cls: [580, 627, 628, 707, 711, 712, 719]
-credits: [Qyriad, horrors, jade, 9999years, winter]
-category: Packaging
----
-
-Lix is built exclusively with the meson build system thanks to a huge team-wide
-effort, and the legacy `make`/`autoconf` based build system has been removed
-altogether. This improves maintainability of Lix, enables things like saving
-20% of compile times with precompiled headers, and generally makes the build
-less able to produce obscure incremental compilation bugs.
-
-Non-Nix-based downstream packaging needs rewriting accordingly.

doc/manual/rl-next/more-logs.md

@@ -1,9 +0,0 @@
----
-synopsis: Show more log context for failed builds
-prs: 9670
-credits: DavHau
-category: Improvements
----
-
-Show 25 lines of log tail instead of 10 for failed builds.
-This increases the chances of having useful information in the shown logs.

doc/manual/rl-next/multiline-log-format.md

@@ -0,0 +1,14 @@
+---
+synopsis: Add log formats `multiline` and `multiline-with-logs`
+cls: [1369]
+credits: [kloenk]
+category: Improvements
+---
+
+Added two new log formats (`multiline` and `multiline-with-logs`) that display
+current activities below each other for better visibility.
+
+These formats attempt to use the maximum available lines
+(defaulting to 25 if unable to determine) and print up to that many lines.
+The status bar is displayed as the first line, with each subsequent
+activity on its own line.

doc/manual/rl-next/new-assertions.md

@@ -1,26 +0,0 @@
----
-synopsis: Lix turns more internal bugs into crashes
-cls: [797, 626]
-credits: jade
-category: Packaging
-significance: significant
----
-
-Lix now enables build options such as trapping on signed overflow and enabling
-libstdc++ assertions by default. These may find new bugs in Lix, which will
-present themselves as Lix processes aborting, potentially without an error
-message.
-
-If Lix processes abort on your machine, this is a bug. Please file a bug,
-ideally with the core dump (or information from it).
-
-On Linux, run `coredumpctl list`, find the crashed process's PID at
-the bottom of the list, then run `coredumpctl info THE-PID`. You can then paste
-the output into a bug report.
-
-On macOS, open the Console app from Applications/Utilities, select Crash
-Reports, select the crash report in question. Right click on it, select Open In
-Finder, then include that file in your bug report. [See the Apple
-documentation][apple-crashreport] for more details.
-
-[apple-crashreport]: https://developer.apple.com/documentation/xcode/acquiring-crash-reports-and-diagnostic-logs#Locate-crash-reports-and-memory-logs-on-the-device

doc/manual/rl-next/nix-config-show.md

@@ -1,12 +0,0 @@
----
-synopsis: rename 'nix show-config' to 'nix config show'
-issues: 7672
-prs: 9477
-cls: 993
-credits: [thufschmitt, ma27]
-category: Improvements
----
-
-`nix show-config` was renamed to `nix config show` to be more consistent with the rest of the command-line interface.
-
-Running `nix show-config` will now print a deprecation warning saying to use `nix config show` instead.

doc/manual/rl-next/nix-copy-is-fast.md

@@ -0,0 +1,12 @@
+---
+synopsis: "`nix copy` is now several times faster at `querying info about /nix/store/...`"
+cls: [1462]
+issues: [fj#366]
+credits: [jade]
+category: Fixes
+---
+
+We fixed a locking bug that serialized `querying info about /nix/store/...`
+onto just one thread such that it was eating `O(paths to copy * latency)` time
+while setting up to copy paths to s3 and other stores. It is now `nproc` times
+faster.

doc/manual/rl-next/nix-env-json-drv-path.md

@@ -1,8 +0,0 @@
----
-synopsis: Fix `nix-env --query --drv-path --json`
-prs: 9257
-credits: [Artturin, horrors]
-category: Fixes
----
-
-Fixed a bug where `nix-env --query` ignored `--drv-path` when `--json` was set.

doc/manual/rl-next/nix-eval-derivations.md

@@ -1,9 +0,0 @@
----
-synopsis: Print derivation paths in `nix eval`
-cls: 446
-credits: 9999years
-category: Improvements
----
-
-`nix eval` previously printed derivations as attribute sets, so commands that print derivations (e.g. `nix eval nixpkgs#bash`) would infinitely loop and segfault.
-It now prints the `.drv` path the derivation generates instead.

doc/manual/rl-next/nix-flake-check-logs-actions.md

@@ -1,37 +0,0 @@
----
-synopsis: "`nix flake check` logs the checks"
-issues: 8882
-prs: 8893
-cls: [259, 260, 261, 262]
-credits: [9999years, raito, horrors]
-category: Improvements
-significance: significant
----
-
-`nix flake check` now logs the checks it runs and the derivations it evaluates:
-
-```
-$ nix flake check -v
-evaluating flake...
-checking flake output 'checks'...
-checking derivation 'checks.aarch64-darwin.ghciwatch-tests'...
-derivation evaluated to /nix/store/nh7dlvsrhds4cxl91mvgj4h5cbq6skmq-ghciwatch-test-0.3.0.drv
-checking derivation 'checks.aarch64-darwin.ghciwatch-clippy'...
-derivation evaluated to /nix/store/9cb5a6wmp6kf6hidqw9wphidvb8bshym-ghciwatch-clippy-0.3.0.drv
-checking derivation 'checks.aarch64-darwin.ghciwatch-doc'...
-derivation evaluated to /nix/store/8brdd3jbawfszpbs7vdpsrhy80as1il8-ghciwatch-doc-0.3.0.drv
-checking derivation 'checks.aarch64-darwin.ghciwatch-fmt'...
-derivation evaluated to /nix/store/wjhs0l1njl5pyji53xlmfjrlya0wmz8p-ghciwatch-fmt-0.3.0.drv
-checking derivation 'checks.aarch64-darwin.ghciwatch-audit'...
-derivation evaluated to /nix/store/z0mps8dyj2ds7c0fn0819y5h5611033z-ghciwatch-audit-0.3.0.drv
-checking flake output 'packages'...
-checking derivation 'packages.aarch64-darwin.default'...
-derivation evaluated to /nix/store/41abbdyglw5x9vcsvd89xan3ydjf8d7r-ghciwatch-0.3.0.drv
-checking flake output 'apps'...
-checking flake output 'devShells'...
-checking derivation 'devShells.aarch64-darwin.default'...
-derivation evaluated to /nix/store/bc935gz7dylzmcpdb5cczr8gngv8pmdb-nix-shell.drv
-running 5 flake checks...
-warning: The check omitted these incompatible systems: aarch64-linux, x86_64-darwin, x86_64-linux
-Use '--all-systems' to check all.
-```

doc/manual/rl-next/nix-flake-update-ux.md

@@ -1,19 +0,0 @@
----
-synopsis: "Overhaul `nix flake update` and `nix flake lock` UX"
-prs: 8817
-credits: [iFreilicht, Lunaphied, thufschmitt]
-category: Breaking Changes
----
-
-The interface for creating and updating lock files has been overhauled:
-
-- [`nix flake lock`](@docroot@/command-ref/new-cli/nix3-flake-lock.md) only creates lock files and adds missing inputs now.
-It will *never* update existing inputs.
-
-- [`nix flake update`](@docroot@/command-ref/new-cli/nix3-flake-update.md) does the same, but *will* update inputs.
-- Passing no arguments will update all inputs of the current flake, just like it already did.
-- Passing input names as arguments will ensure only those are updated. This replaces the functionality of `nix flake lock --update-input`
-- To operate on a flake outside the current directory, you must now pass `--flake path/to/flake`.
-
-- The flake-specific flags `--recreate-lock-file` and `--update-input` have been removed from all commands operating on installables.
-They are superceded by `nix flake update`.

doc/manual/rl-next/nix-profile-names.md

@@ -1,11 +0,0 @@
----
-synopsis: "`nix profile` now allows referring to elements by human-readable name, and no longer accepts indices"
-prs: 8678
-cls: [978, 980]
-category: Breaking Changes
-credits: [iFreilicht, Qyriad, edolstra]
----
-
-[`nix profile`](@docroot@/command-ref/new-cli/nix3-profile.md) now uses names to refer to installed packages when running [`list`](@docroot@/command-ref/new-cli/nix3-profile-list.md), [`remove`](@docroot@/command-ref/new-cli/nix3-profile-remove.md) or [`upgrade`](@docroot@/command-ref/new-cli/nix3-profile-upgrade.md) as opposed to indices. Indices have been removed. Profile element names are generated when a package is installed and remain the same until the package is removed.
-
-**Warning**: The `manifest.nix` file used to record the contents of profiles has changed. Lix will automatically upgrade profiles to the new version when you modify the profile. After that, the profile can no longer be used by older versions of Lix.

doc/manual/rl-next/nix-store-prefetch-unpack.md

@@ -1,18 +0,0 @@
----
-synopsis: "Add an option `--unpack` to unpack archives in `nix store prefetch-file`"
-prs: 9805
-cls: 224
-credits: [yshui, horrors]
-category: Improvements
----
-
-It is now possible to fetch an archive then NAR-hash it (as in, hash it in the
-same manner as `builtins.fetchTarball` or fixed-output derivations with
-recursive hash type) in one command.
-
-Example:
-
-```
-~ » nix store prefetch-file --name source --unpack https://git.lix.systems/lix-project/lix/archive/2.90-beta.1.tar.gz
-Downloaded 'https://git.lix.systems/lix-project/lix/archive/2.90-beta.1.tar.gz' to '/nix/store/yvfqnq52ryjc3janw02ziv7kr6gd0cs1-source' (hash 'sha256-REWlo2RYHfJkxnmZTEJu3Cd/2VM+wjjpPy7Xi4BdDTQ=').
-```

doc/manual/rl-next/nixversion-fake.md

@@ -1,17 +0,0 @@
----
-synopsis: "`builtins.nixVersion` and `builtins.langVersion` return fixed values"
-cls: [558, 1144]
-credits: jade
-category: Breaking Changes
----
-
-`builtins.nixVersion` now returns a fixed value `"2.18.3-lix"`.
-
-`builtins.langVersion` returns a fixed value `6`, matching CppNix 2.18.
-
-This prevents feature detection assuming that features that exist in Nix
-post-Lix-branch-off might exist, even though the Lix version is greater than
-the Nix version.
-
-In the future, check for builtins for feature detection. If a feature cannot be
-detected by *those* means, please file a Lix bug.

doc/manual/rl-next/no-cache-eval-errors.md

@@ -1,10 +0,0 @@
----
-synopsis: re-evaluate cached evaluation errors
-cls: 771
-credits: Qyriad
-category: Fixes
----
-
-"cached failure of [expr]" errors have been removed: expressions already in the
-eval cache as a failure will now simply be re-evaluated, removing the need to
-set `--no-eval-cache` or similar to see the error.

doc/manual/rl-next/old-protocol-removal.md

@@ -0,0 +1,21 @@
+---
+synopsis: "Lix no longer speaks the Nix remote-build worker protocol to clients or servers older than CppNix 2.3"
+cls: [1207, 1208, 1206, 1205, 1204, 1203, 1479]
+issues: [fj#325]
+credits: [jade]
+category: Breaking Changes
+---
+
+CppNix 2.3 was released in 2019, and is the new oldest supported version. We
+will increase our support baseline in the future up to a final version of CppNix
+2.18 (which may happen soon given that it is the only still-packaged and thus
+still-tested >2.3 version), but this step already removes a significant amount
+of dead, untested, code paths.
+
+Lix speaks the same version of the protocol as CppNix 2.18 and that fact will
+never change in the future; the Lix plans to replace the protocol for evolution
+will entail a complete incompatible replacement that will be supported in
+parallel with the old protocol. Lix will thus retain remote build compatibility
+with CppNix as long as CppNix maintains protocol compatibility with 2.18, and
+as long as Lix retains legacy protocol support (which will likely be a long
+time given that we plan to convert it to a frozen-in-time shim).

doc/manual/rl-next/print-in-repl.md

@@ -1,55 +0,0 @@
----
-synopsis: "REPL printing improvements"
-prs: [9931, 10208]
-cls: [375, 492]
-credits: [9999years, horrors]
-category: Improvements
----
-
-The REPL printer has been improved to do the following:
-- If a string is passed to `:print`, it is printed literally to the screen
-- Structures will be printed as multiple lines when necessary
-
-Before:
-
-```
-nix-repl> { attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
-{ attrs = { ... }; list = [ ... ]; list' = [ ... ]; }
-
-nix-repl> :p { attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
-{ attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
-
-nix-repl> :p "meow"
-"meow"
-```
-
-After:
-
-```
-nix-repl> { attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
-{
-  attrs = { ... };
-  list = [ ... ];
-  list' = [ ... ];
-}
-
-nix-repl> :p { attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
-{
-  attrs = {
-    a = {
-      b = {
-        c = { };
-      };
-    };
-  };
-  list = [ 1 ];
-  list' = [
-    1
-    2
-    3
-  ];
-}
-
-nix-repl> :p "meow"
-meow
-```

doc/manual/rl-next/print-value-in-coercion-error.md

@@ -1,26 +0,0 @@
----
-synopsis: Coercion errors include the failing value
-issues: 561
-prs: 9754
-credits: [9999years, horrors]
-category: Improvements
----
-
-The `error: cannot coerce a <TYPE> to a string` message now includes the value
-which caused the error.
-
-Before:
-
-```
-       error: cannot coerce a set to a string
-```
-
-After:
-
-```
-       error: cannot coerce a set to a string: { aesSupport = «thunk»;
-       avx2Support = «thunk»; avx512Support = «thunk»; avxSupport = «thunk»;
-       canExecute = «thunk»; config = «thunk»; darwinArch = «thunk»; darwinMinVersion
-       = «thunk»; darwinMinVersionVariable = «thunk»; darwinPlatform = «thunk»; «84
-       attributes elided»}
-```

doc/manual/rl-next/print-value-in-installable-flake-error.md

@@ -1,20 +0,0 @@
----
-synopsis: New-cli flake commands that expect derivations now print the failing value and its type
-credits: Qyriad
-category: Improvements
-cls: 1177
----
-
-In errors like `flake output attribute 'legacyPackages.x86_64-linux.lib' is not a derivation or path`, the message now includes the failing value and type.
-
-Before:
-
-```
-    error: flake output attribute 'nixosConfigurations.yuki.config' is not a derivation or path
-````
-
-After:
-
-```
-    error: expected flake output attribute 'nixosConfigurations.yuki.config' to be a derivation or path but found a set: { appstream = «thunk»; assertions = «thunk»; boot = { bcache = «thunk»; binfmt = «thunk»; binfmtMiscRegistrations = «thunk»; blacklistedKernelModules = «thunk»; bootMount = «thunk»; bootspec = «thunk»; cleanTmpDir = «thunk»; consoleLogLevel = «thunk»; «43 attributes elided» }; «48 attributes elided» }
-```

doc/manual/rl-next/print-value-in-type-error.md

@@ -1,25 +0,0 @@
----
-synopsis: Type errors include the failing value
-issues: 561
-prs: 9753
-credits: [9999years, horrors]
-category: Improvements
----
-
-In errors like `value is an integer while a list was expected`, the message now
-includes the failing value.
-
-Before:
-
-```
-       error: value is a set while a string was expected
-```
-
-After:
-
-```
-       error: expected a string but found a set: { ghc810 = «thunk»;
-       ghc8102Binary = «thunk»; ghc8107 = «thunk»; ghc8107Binary = «thunk»;
-       ghc865Binary = «thunk»; ghc90 = «thunk»; ghc902 = «thunk»; ghc92 = «thunk»;
-       ghc924Binary = «thunk»; ghc925 = «thunk»;  «17 attributes elided»}
-```

doc/manual/rl-next/reduce-debugger-clutter.md

@@ -1,39 +0,0 @@
----
-synopsis: "Visual clutter in `--debugger` is reduced"
-prs: 9919
-category: Improvements
-credits: [9999years, horrors]
----
-
-Before:
-```
-info: breakpoint reached
-
-
-Starting REPL to allow you to inspect the current state of the evaluator.
-
-Welcome to Nix 2.20.0pre20231222_dirty. Type :? for help.
-
-nix-repl> :continue
-error: uh oh
-
-
-Starting REPL to allow you to inspect the current state of the evaluator.
-
-Welcome to Nix 2.20.0pre20231222_dirty. Type :? for help.
-
-nix-repl>
-```
-
-After:
-
-```
-info: breakpoint reached
-
-Nix 2.20.0pre20231222_dirty debugger
-Type :? for help.
-nix-repl> :continue
-error: uh oh
-
-nix-repl>
-```

doc/manual/rl-next/registry-add-shorthand-only.md

@@ -0,0 +1,10 @@
+---
+synopsis: "`nix registry add` now requires a shorthand flakeref on the 'from' side"
+cls: 1494
+credits: delan
+category: Improvements
+---
+
+The 'from' argument must now be a shorthand flakeref like `nixpkgs` or `nixpkgs/nixos-20.03`, making it harder to accidentally swap the 'from' and 'to' arguments.
+
+Registry entries that map from other flake URLs can still be specified in registry.json, the `nix.registry` option in NixOS, or the `--override-flake` option in the CLI, but they are not guaranteed to work correctly.

doc/manual/rl-next/reject-flake-config.md

@@ -0,0 +1,9 @@
+---
+synopsis: Allow automatic rejection of configuration options from flakes
+cls: [1541]
+credits: [alois31]
+category: Improvements
+---
+
+Setting `accept-flake-config` to `false` now respects user choice by automatically rejecting configuration options set by flakes.
+The old behaviour of asking each time is still available (and default) by setting it to the special value `ask`.

doc/manual/rl-next/rename-lixexpr.md

@@ -1,31 +0,0 @@
----
-synopsis: Rename all the libraries nixexpr, nixstore, etc to lixexpr, lixstore, etc
-credits: jade
-category: Breaking Changes
----
-
-The Lix C++ API libraries have had the following changes:
-- Includes moved from `include/nix/` to `include/lix/`
-- `pkg-config` files renamed from `nix-expr` to `lix-expr` and so on.
-- Libraries renamed from `libnixexpr.so` to `liblixexpr.so` and so on.
-
-There are other changes between Nix 2.18 and Lix, since these APIs are not
-stable. However, this change in particular is a deliberate compatibility break
-to force downstreams linking to Lix to specifically handle Lix and avoid Lix
-accidentally getting ensnared in compatibility code for newer CppNix.
-
-Migration path:
-
-- expr.hh      -> lix/libexpr/expr.hh
-- nix/config.h -> lix/config.h
-
-To apply this migration automatically, remove all `<nix/>` from includes, so `#include <nix/expr.hh>` -> `#include <expr.hh>`.
-Then, the correct paths will be resolved from the tangled mess, and the clang-tidy automated fix will work.
-
-Then run the following for out of tree projects (header filter is set to only fix instances in headers in `../src` relative to the compiler's working directory, as would be the case in nix-eval-jobs or other things built with meson, e.g.):
-
-```console
-lix_root=$HOME/lix
-(cd $lix_root/clang-tidy && nix develop -c 'meson setup build && ninja -C build')
-run-clang-tidy -checks='-*,lix-fixincludes' -load=$lix_root/clang-tidy/build/liblix-clang-tidy.so -p build/ -header-filter '\.\./src/.*\.h' -fix src
-```

doc/manual/rl-next/repl-complete-colon.md

@@ -0,0 +1,8 @@
+---
+synopsis: "`nix repl` now allows tab-completing the special repl :colon commands"
+cls: 1367
+credits: Qyriad
+category: Improvements
+---
+
+The REPL (`nix repl`) supports pressing `<TAB>` to complete a partial expression, but now also supports completing the special :colon commands as well (`:b`, `:edit`, `:doc`, etc), if the line starts with a colon.

doc/manual/rl-next/repl-doc-command.md

@@ -1,16 +0,0 @@
----
-synopsis: Experimental REPL support for documentation comments using `:doc`
-cls: 564
-category: Features
-credits: [Lunaphied, jade]
-significance: significant
----
-
-Using `:doc` in the REPL now supports showing documentation comments when defined on a function.
-
-Previously this was only able to document builtins, however it now will show comments defined on a lambda as well.
-
-This support is experimental and relies on an embedded version of [nix-doc](https://github.com/lf-/nix-doc).
-
-The logic also supports limited Markdown formatting of doccomments and should easily support any [RFC 145](https://github.com/NixOS/rfcs/blob/master/rfcs/0145-doc-strings.md)
-compatible documentation comments in addition to simple commented documentation.

doc/manual/rl-next/repl-fix-history.md

@@ -1,9 +0,0 @@
----
-synopsis: "`nix repl` history is saved more reliably"
-cls: 1164
-credits: puck
----
-
-`nix repl` now saves its history file after each line, rather than at the end
-of the session; ensuring that it will remember what you typed even after it
-crashes.

doc/manual/rl-next/repl-interrupt.md

@@ -1,10 +0,0 @@
----
-synopsis: Interrupting builds in the REPL works more than once
-cls: 1097
-category: Fixes
-credits: alois31
----
-
-Builds in the REPL can be interrupted by pressing Ctrl+C.
-Previously, this only worked once per REPL session; further attempts would be ignored.
-This issue is now fixed, so that builds can be canceled consistently.

doc/manual/rl-next/repl-overlays.md

@@ -1,39 +0,0 @@
----
-synopsis: Add `repl-overlays` option
-prs: 10203
-cls: 504
-credits: 9999years
-significance: significant
-category: Features
----
-
-A `repl-overlays` option has been added, which specifies files that can overlay
-and modify the top-level bindings in `nix repl`. For example, with the
-following contents in `~/.config/nix/repl.nix`:
-
-```nix
-info: final: prev: let
-  optionalAttrs = predicate: attrs:
-    if predicate
-    then attrs
-    else {};
-in
-  optionalAttrs (prev ? legacyPackages && prev.legacyPackages ? ${info.currentSystem})
-  {
-    pkgs = prev.legacyPackages.${info.currentSystem};
-  }
-```
-
-We can run `nix repl` and use `pkgs` to refer to `legacyPackages.${currentSystem}`:
-
-```ShellSession
-$ nix repl --repl-overlays ~/.config/nix/repl.nix nixpkgs
-Lix 2.90.0
-Type :? for help.
-Loading installable 'flake:nixpkgs#'...
-Added 5 variables.
-Loading 'repl-overlays'...
-Added 6 variables.
-nix-repl> pkgs.bash
-«derivation /nix/store/g08b5vkwwh0j8ic9rkmd8mpj878rk62z-bash-5.2p26.drv»
-```

doc/manual/rl-next/repl-tstp.md

@@ -1,7 +0,0 @@
----
-synopsis: "REPL now supports CTRL+Z to suspend"
-credits: [Qyriad]
-category: Improvements
----
-
-Editline is now built with SIGTSTP support, so now typing CTRL+Z in the REPL will suspend the REPL and allow it to be resumed later or backgrounded.

doc/manual/rl-next/sanitizers.md

@@ -0,0 +1,10 @@
+---
+synopsis: "Lix now supports building with UndefinedBehaviorSanitizer"
+cls: [1483]
+credits: [jade]
+category: Development
+---
+
+You can now build Lix with the configuration option `-Db_sanitize=undefined` and it will both work and pass tests. AddressSanitizer support is also coming soon.
+
+For a list of undefined behaviour fixed by sanitizer usage, see [the gerrit topic "undefined-behaviour"](https://gerrit.lix.systems/q/topic:%22undefined-behaviour%22).

doc/manual/rl-next/shebang-single-quotes.md

@@ -1,13 +0,0 @@
----
-synopsis: Allow single quotes in nix-shell shebangs
-prs: 8470
-credits: [ncfavier, horrors]
-category: Improvements
----
-
-Example:
-
-```bash
-#! /usr/bin/env nix-shell
-#! nix-shell -i bash --packages 'terraform.withPlugins (plugins: [ plugins.openstack ])'
-```

doc/manual/rl-next/short-expr-flag.md

@@ -1,16 +0,0 @@
----
-synopsis: reintroduce shortened `-E` form for `--expr` to new CLI
-cls: 605
-credits: Lunaphied
-category: Improvements
----
-
-In the old CLI, it was possible to supply a shorter `-E` flag instead of fully
-specifying `--expr` every time you wished to provide an expression that would
-be evaluated to produce the given command's input. This was retained for the
-`--file` flag when the new CLI utilities were written with `-f`, but `-E` was
-dropped.
-
-We now restore the `-E` short form for better UX. This is most useful for
-`nix eval` but most any command that takes an Installable argument should benefit
-from it as well.

doc/manual/rl-next/source-location-in-while-evaluating-attribute.md

@@ -1,25 +0,0 @@
----
-synopsis: "In the debugger, `while evaluating the attribute` errors now include position information"
-prs: 9915
-credits: 9999years
-category: Fixes
----
-
-Before:
-
-```
-0: while evaluating the attribute 'python311.pythonForBuild.pkgs'
-0x600001522598
-```
-
-After:
-
-```
-0: while evaluating the attribute 'python311.pythonForBuild.pkgs'
-/nix/store/hg65h51xnp74ikahns9hyf3py5mlbbqq-source/overrides/default.nix:132:27
-
-   131|
-   132|       bootstrappingBase = pkgs.${self.python.pythonAttr}.pythonForBuild.pkgs;
-      |                           ^
-   133|     in
-```

doc/manual/rl-next/source-positions-in-errors.md

@@ -1,44 +0,0 @@
----
-synopsis: Source locations are printed more consistently in errors
-issues: 561
-prs: 9555
-credits: [9999years, horrors]
-category: Improvements
----
-
-Source location information is now included in error messages more
-consistently. Given this code:
-
-```nix
-let
-  attr = {foo = "bar";};
-  key = {};
-in
-  attr.${key}
-```
-
-Previously, Nix would show this unhelpful message when attempting to evaluate
-it:
-
-```
-error:
-       … while evaluating an attribute name
-
-       error: value is a set while a string was expected
-```
-
-Now, the error message displays where the problematic value was found:
-
-```
-error:
-       … while evaluating an attribute name
-
-         at bad.nix:4:11:
-
-            3|   key = {};
-            4| in attr.${key}
-             |           ^
-            5|
-
-       error: expected a string but found a set: { }
-```

doc/manual/rl-next/ssh-ng-phase-reporting.md

@@ -1,8 +0,0 @@
----
-synopsis: Include phase reporting in log file for ssh-ng builds
-prs: 9280
-credits: r-vdp
-category: Fixes
----
-
-Store phase information of remote builds run via `ssh-ng` remotes in the local log file, matching logging behavior of local builds.

doc/manual/rl-next/ssh-ng-substitute.md

@@ -1,9 +0,0 @@
----
-synopsis: Fix `ssh-ng://` remotes not respecting `--substitute-on-destination`
-prs: 9600
-credits: SharzyL
-category: Fixes
----
-
-`nix copy ssh-ng://` now respects `--substitute-on-destination`, as does `nix-copy-closure` and other commands that operate on remote `ssh-ng` stores.
-Previously this was always set by `builders-use-substitutes` setting.

doc/manual/rl-next/stack-overflow-segfaults.md

@@ -1,35 +0,0 @@
----
-synopsis: Some stack overflow segfaults are fixed
-issues: 9616
-prs: 9617
-cls: 205
-category: Improvements
-credits: [9999years, horrors]
----
-
-The number of nested function calls has been restricted, to detect and report
-infinite function call recursions. The default maximum call depth is 10,000 and
-can be set with [the `max-call-depth`
-option](@docroot@/command-ref/conf-file.md#conf-max-call-depth).
-
-This fixes segfaults or the following unhelpful error message in many cases:
-
-    error: stack overflow (possible infinite recursion)
-
-Before:
-
-```
-$ nix-instantiate --eval --expr '(x: x x) (x: x x)'
-Segmentation fault: 11
-```
-
-After:
-
-```
-$ nix-instantiate --eval --expr '(x: x x) (x: x x)'
-error: stack overflow
-
-       at «string»:1:14:
-            1| (x: x x) (x: x x)
-             |              ^
-```

doc/manual/rl-next/upgrade-nix-override.md

@@ -1,8 +0,0 @@
----
-synopsis: add `--store-path` argument to `nix upgrade-nix`, to manually specify the Nix to upgrade to
-cls: 953
-credits: Qyriad
-category: Features
----
-
-`nix upgrade-nix` by default downloads a manifest to find the new Nix version to upgrade to, but now you can specify `--store-path` to upgrade Nix to an arbitrary version from the Nix store.

doc/manual/rl-next/upgrade-nix-profile-compat.md

@@ -1,10 +0,0 @@
----
-synopsis: using `nix profile` on `/nix/var/nix/profiles/default` no longer breaks `nix upgrade-nix`
-cls: 952
-credits: Qyriad
-category: Fixes
----
-
-On non-NixOS, Nix is conventionally installed into a `nix-env` style profile at /nix/var/nix/profiles/default.
-Like any `nix-env` profile, using `nix profile` on it automatically migrates it to a `nix profile` style profile, which is incompatible with `nix-env`.
-`nix upgrade-nix` previously relied solely on `nix-env` to do the upgrade, but now will work fine with either kind of profile.

doc/manual/rl-next/upstart-removal.md

@@ -1,10 +0,0 @@
----
-synopsis: Upstart scripts removed
-cls: 574
-category: Packaging
-credits: jade
----
-
-Upstart scripts have been removed from Lix, since Upstart is obsolete and has
-not been shipped by any major distributions for many years. If these are
-necessary to your use case, please back port them to your packaging.

doc/manual/rl-next/warn-ignored-client-settings.md

@@ -1,9 +0,0 @@
----
-synopsis: Warn about ignored client settings
-cls: 1026
-credits: jade
-category: Improvements
----
-
-Emit a warning for every client-provided setting the daemon ignores because the requesting client is not run by a trusted user.
-Previously this was only a debug message.

doc/manual/rl-next/with-error-reporting.md

@@ -1,34 +0,0 @@
----
-synopsis: Better error reporting for `with` expressions
-prs: 9658
-cls: 207
-credits: horrors
-category: Improvements
----
-
-`with` expressions using non-attrset values to resolve variables are now reported with proper positions.
-
-Previously an incorrect `with` expression would report no position at all, making it hard to determine where the error originated:
-
-```
-nix-repl> with 1; a
-error:
-       … <borked>
-
-         at «none»:0: (source not available)
-
-       error: value is an integer while a set was expected
-```
-
-Now position information is preserved and reported as with most other errors:
-
-```
-nix-repl> with 1; a
-error:
-       … while evaluating the first subexpression of a with expression
-         at «string»:1:1:
-            1| with 1; a
-             | ^
-
-       error: expected a set but found an integer: 1
-```

doc/manual/src/SUMMARY.md

@@ -196,53 +196,55 @@
   - [C++ style guide](contributing/cxx.md)
 - [Release Notes](release-notes/release-notes.md)
   - [Upcoming release](release-notes/rl-next.md)
-  - [Release 2.18 (2023-09-20)](release-notes/rl-2.18.md)
-  - [Release 2.17 (2023-07-24)](release-notes/rl-2.17.md)
-  - [Release 2.16 (2023-05-31)](release-notes/rl-2.16.md)
-  - [Release 2.15 (2023-04-11)](release-notes/rl-2.15.md)
-  - [Release 2.14 (2023-02-28)](release-notes/rl-2.14.md)
-  - [Release 2.13 (2023-01-17)](release-notes/rl-2.13.md)
-  - [Release 2.12 (2022-12-06)](release-notes/rl-2.12.md)
-  - [Release 2.11 (2022-08-25)](release-notes/rl-2.11.md)
-  - [Release 2.10 (2022-07-11)](release-notes/rl-2.10.md)
-  - [Release 2.9 (2022-05-30)](release-notes/rl-2.9.md)
-  - [Release 2.8 (2022-04-19)](release-notes/rl-2.8.md)
-  - [Release 2.7 (2022-03-07)](release-notes/rl-2.7.md)
-  - [Release 2.6 (2022-01-24)](release-notes/rl-2.6.md)
-  - [Release 2.5 (2021-12-13)](release-notes/rl-2.5.md)
-  - [Release 2.4 (2021-11-01)](release-notes/rl-2.4.md)
-  - [Release 2.3 (2019-09-04)](release-notes/rl-2.3.md)
-  - [Release 2.2 (2019-01-11)](release-notes/rl-2.2.md)
-  - [Release 2.1 (2018-09-02)](release-notes/rl-2.1.md)
-  - [Release 2.0 (2018-02-22)](release-notes/rl-2.0.md)
-  - [Release 1.11.10 (2017-06-12)](release-notes/rl-1.11.10.md)
-  - [Release 1.11 (2016-01-19)](release-notes/rl-1.11.md)
-  - [Release 1.10 (2015-09-03)](release-notes/rl-1.10.md)
-  - [Release 1.9 (2015-06-12)](release-notes/rl-1.9.md)
-  - [Release 1.8 (2014-12-14)](release-notes/rl-1.8.md)
-  - [Release 1.7 (2014-04-11)](release-notes/rl-1.7.md)
-  - [Release 1.6.1 (2013-10-28)](release-notes/rl-1.6.1.md)
-  - [Release 1.6 (2013-09-10)](release-notes/rl-1.6.md)
-  - [Release 1.5.2 (2013-05-13)](release-notes/rl-1.5.2.md)
-  - [Release 1.5 (2013-02-27)](release-notes/rl-1.5.md)
-  - [Release 1.4 (2013-02-26)](release-notes/rl-1.4.md)
-  - [Release 1.3 (2013-01-04)](release-notes/rl-1.3.md)
-  - [Release 1.2 (2012-12-06)](release-notes/rl-1.2.md)
-  - [Release 1.1 (2012-07-18)](release-notes/rl-1.1.md)
-  - [Release 1.0 (2012-05-11)](release-notes/rl-1.0.md)
-  - [Release 0.16 (2010-08-17)](release-notes/rl-0.16.md)
-  - [Release 0.15 (2010-03-17)](release-notes/rl-0.15.md)
-  - [Release 0.14 (2010-02-04)](release-notes/rl-0.14.md)
-  - [Release 0.13 (2009-11-05)](release-notes/rl-0.13.md)
-  - [Release 0.12 (2008-11-20)](release-notes/rl-0.12.md)
-  - [Release 0.11 (2007-12-31)](release-notes/rl-0.11.md)
-  - [Release 0.10.1 (2006-10-11)](release-notes/rl-0.10.1.md)
-  - [Release 0.10 (2006-10-06)](release-notes/rl-0.10.md)
-  - [Release 0.9.2 (2005-09-21)](release-notes/rl-0.9.2.md)
-  - [Release 0.9.1 (2005-09-20)](release-notes/rl-0.9.1.md)
-  - [Release 0.9 (2005-09-16)](release-notes/rl-0.9.md)
-  - [Release 0.8.1 (2005-04-13)](release-notes/rl-0.8.1.md)
-  - [Release 0.8 (2005-04-11)](release-notes/rl-0.8.md)
-  - [Release 0.7 (2005-01-12)](release-notes/rl-0.7.md)
-  - [Release 0.6 (2004-11-14)](release-notes/rl-0.6.md)
-  - [Release 0.5 and earlier](release-notes/rl-0.5.md)
+  <!-- RELENG-AUTO-INSERTION-MARKER (see releng/release_notes.py) -->
+  - [Lix 2.90 (FIXME date)](release-notes/rl-2.90.md)
+  - [Nix 2.18 (2023-09-20)](release-notes/rl-2.18.md)
+  - [Nix 2.17 (2023-07-24)](release-notes/rl-2.17.md)
+  - [Nix 2.16 (2023-05-31)](release-notes/rl-2.16.md)
+  - [Nix 2.15 (2023-04-11)](release-notes/rl-2.15.md)
+  - [Nix 2.14 (2023-02-28)](release-notes/rl-2.14.md)
+  - [Nix 2.13 (2023-01-17)](release-notes/rl-2.13.md)
+  - [Nix 2.12 (2022-12-06)](release-notes/rl-2.12.md)
+  - [Nix 2.11 (2022-08-25)](release-notes/rl-2.11.md)
+  - [Nix 2.10 (2022-07-11)](release-notes/rl-2.10.md)
+  - [Nix 2.9 (2022-05-30)](release-notes/rl-2.9.md)
+  - [Nix 2.8 (2022-04-19)](release-notes/rl-2.8.md)
+  - [Nix 2.7 (2022-03-07)](release-notes/rl-2.7.md)
+  - [Nix 2.6 (2022-01-24)](release-notes/rl-2.6.md)
+  - [Nix 2.5 (2021-12-13)](release-notes/rl-2.5.md)
+  - [Nix 2.4 (2021-11-01)](release-notes/rl-2.4.md)
+  - [Nix 2.3 (2019-09-04)](release-notes/rl-2.3.md)
+  - [Nix 2.2 (2019-01-11)](release-notes/rl-2.2.md)
+  - [Nix 2.1 (2018-09-02)](release-notes/rl-2.1.md)
+  - [Nix 2.0 (2018-02-22)](release-notes/rl-2.0.md)
+  - [Nix 1.11.10 (2017-06-12)](release-notes/rl-1.11.10.md)
+  - [Nix 1.11 (2016-01-19)](release-notes/rl-1.11.md)
+  - [Nix 1.10 (2015-09-03)](release-notes/rl-1.10.md)
+  - [Nix 1.9 (2015-06-12)](release-notes/rl-1.9.md)
+  - [Nix 1.8 (2014-12-14)](release-notes/rl-1.8.md)
+  - [Nix 1.7 (2014-04-11)](release-notes/rl-1.7.md)
+  - [Nix 1.6.1 (2013-10-28)](release-notes/rl-1.6.1.md)
+  - [Nix 1.6 (2013-09-10)](release-notes/rl-1.6.md)
+  - [Nix 1.5.2 (2013-05-13)](release-notes/rl-1.5.2.md)
+  - [Nix 1.5 (2013-02-27)](release-notes/rl-1.5.md)
+  - [Nix 1.4 (2013-02-26)](release-notes/rl-1.4.md)
+  - [Nix 1.3 (2013-01-04)](release-notes/rl-1.3.md)
+  - [Nix 1.2 (2012-12-06)](release-notes/rl-1.2.md)
+  - [Nix 1.1 (2012-07-18)](release-notes/rl-1.1.md)
+  - [Nix 1.0 (2012-05-11)](release-notes/rl-1.0.md)
+  - [Nix 0.16 (2010-08-17)](release-notes/rl-0.16.md)
+  - [Nix 0.15 (2010-03-17)](release-notes/rl-0.15.md)
+  - [Nix 0.14 (2010-02-04)](release-notes/rl-0.14.md)
+  - [Nix 0.13 (2009-11-05)](release-notes/rl-0.13.md)
+  - [Nix 0.12 (2008-11-20)](release-notes/rl-0.12.md)
+  - [Nix 0.11 (2007-12-31)](release-notes/rl-0.11.md)
+  - [Nix 0.10.1 (2006-10-11)](release-notes/rl-0.10.1.md)
+  - [Nix 0.10 (2006-10-06)](release-notes/rl-0.10.md)
+  - [Nix 0.9.2 (2005-09-21)](release-notes/rl-0.9.2.md)
+  - [Nix 0.9.1 (2005-09-20)](release-notes/rl-0.9.1.md)
+  - [Nix 0.9 (2005-09-16)](release-notes/rl-0.9.md)
+  - [Nix 0.8.1 (2005-04-13)](release-notes/rl-0.8.1.md)
+  - [Nix 0.8 (2005-04-11)](release-notes/rl-0.8.md)
+  - [Nix 0.7 (2005-01-12)](release-notes/rl-0.7.md)
+  - [Nix 0.6 (2004-11-14)](release-notes/rl-0.6.md)
+  - [Nix 0.5 and earlier](release-notes/rl-0.5.md)

doc/manual/src/command-ref/opt-common.md

@@ -78,6 +78,16 @@ Most commands in Lix accept the following command-line options:
 
     Display the raw logs, with the progress bar at the bottom.
 
+  - `multiline`
+
+    Display a progress bar during the builds and in the lines below that one line per activity.
+
+
+  - `multiline-with-logs`
+
+    Displayes the raw logs, with a progress bar and activities each in a new line at the bottom.
+
+
 - <span id="opt-no-build-output">[`--no-build-output`](#opt-no-build-output)</span> / `-Q`
 
   By default, output written by builders to standard output and standard error is echoed to the Lix command's standard error.

doc/manual/src/contributing/hacking.md

@@ -39,17 +39,19 @@ $ nix-shell -A native-clangStdenvPackages
 
 ### Building from the development shell
 
-As always you may run [stdenv's phases by name](https://nixos.org/manual/nixpkgs/unstable/#sec-building-stdenv-package-in-nix-shell), e.g.:
+You can build and test Lix with just:
 
 ```bash
-$ configurePhase
-$ buildPhase
-$ checkPhase
-$ installPhase
-$ installCheckPhase
+$ just setup
+$ just build
+$ just test --suite=check
+$ just install
+$ just test --suite=installcheck
 ```
 
-To build manually, however, use the following:
+(Check and installcheck may both be done after install, allowing you to omit the --suite argument entirely, but this is the order package.nix runs them in.)
+
+You can also build Lix manually:
 
 ```bash
 $ meson setup ./build "--prefix=$out" $mesonFlags
@@ -64,9 +66,7 @@ $ meson install -C build
 $ meson test -C build --suite=installcheck
 ```
 
-(Check and installcheck may both be done after install, allowing you to omit the --suite argument entirely, but this is the order package.nix runs them in.)
-
-This will install Lix to `$PWD/outputs`, the `/bin` of which is prepended to PATH in the development shells.
+In both cases, Lix will be installed to `$PWD/outputs`, the `/bin` of which is prepended to PATH in the development shells.
 
 If the tests fail and Meson helpfully has no output for why, use the `--print-error-logs` option to `meson test`.
 
@@ -168,8 +168,26 @@ or for Nix with the [`flakes`] and [`nix-command`] experimental features enabled
 $ nix build .#packages.aarch64-linux.default
 ```
 
-Cross-compiled builds are available for ARMv6 (`armv6l-linux`) and ARMv7 (`armv7l-linux`).
-Add more [system types](#system-type) to `crossSystems` in `flake.nix` to bootstrap Nix on unsupported platforms.
+### Cross compiling using the Lix flake
+
+Lix can also be easily cross compiled to the following arbitrarily-chosen system doubles, which can be useful for bootstrapping Lix on new platforms.
+These are specified in `crossSystems` in `flake.nix`; feel free to submit changes to add new ones if they are useful to you.
+
+- `armv6l-linux`
+- `armv7l-linux`
+- `riscv64-linux`
+
+For example, to cross-compile Lix for `armv6l-linux` from another Linux, use the following:
+
+```console
+$ nix build .#nix-armv6l-linux
+```
+
+It's also possible to cross-compile a tarball of binaries suitable for the Lix installer, for example, for `riscv64-linux`:
+
+```console
+$ nix build .#nix-riscv64-linux.passthru.binaryTarball
+```
 
 ### Building for multiple platforms at once
 
@@ -282,9 +300,8 @@ Regular markdown files used for the manual have a base path of their own and the
 
 ## API documentation
 
-Doxygen API documentation is [available
-online](https://hydra.nixos.org/job/nix/master/internal-api-docs/latest/download-by-type/doc/internal-api-docs). You
-can also build and view it yourself:
+Doxygen API documentation will be available online in the future ([tracking issue](https://git.lix.systems/lix-project/lix/issues/422)).
+You can also build and view it yourself:
 
 ```console
 # nix build .#hydraJobs.internal-api-docs
@@ -294,44 +311,50 @@ can also build and view it yourself:
 or inside a `nix develop` shell by running:
 
 ```bash
+$ meson configure build -Dinternal-api-docs=enabled
 $ meson compile -C build internal-api-docs
 $ xdg-open ./outputs/doc/share/doc/nix/internal-api/html/index.html
 ```
 
 ## Coverage analysis
 
-A coverage analysis report is [available
-online](https://hydra.nixos.org/job/nix/master/coverage/latest/download-by-type/report/coverage). You
-can build it yourself:
+A coverage analysis report will be available online in the future (FIXME(lix-hydra)).
+You can build it yourself:
 
 ```
 # nix build .#hydraJobs.coverage
 # xdg-open ./result/coverage/index.html
 ```
 
-Metrics about the change in line/function coverage over time are also
-[available](https://hydra.nixos.org/job/nix/master/coverage#tabs-charts).
+Metrics about the change in line/function coverage over time will be available in the future (FIXME(lix-hydra)).
 
 ## Add a release note
 
 `doc/manual/rl-next` contains release notes entries for all unreleased changes.
 
 User-visible changes should come with a release note.
+Developer-facing changes should have a release note in the Development category if they are significant and if developers should know about them.
 
 ### Add an entry
 
-Here's what a complete entry looks like. The file name is not incorporated in the document.
+Here's what a complete entry looks like.
+The file name is not incorporated in the final document, and is generally a super brief summary of the change synopsis.
 
-```
+```markdown
 ---
 synopsis: Basically a title
 # 1234 or gh#1234 will refer to CppNix GitHub, fj#1234 will refer to a Lix forgejo issue.
 issues: [1234, fj#1234]
-# Use this *only* if there is a CppNix pull request associated with this change
+# Use this *only* if there is a CppNix pull request associated with this change.
 prs: 1238
-# List of Lix Gerrit changelist numbers; if there is an associated Lix GitHub
-# PR, just put in the Gerrit CL number.
+# List of Lix Gerrit changelist numbers.
+# If there is an associated Lix GitHub PR, just put in the Gerrit CL number.
 cls: [123]
+# Heading that this release note will appear under.
+category: Breaking Changes
+# Add a credit mention in the bottom of the release note.
+# your-name is used as a key into doc/manual/change-authors.yml for metadata
+credits: [your-name]
 ---
 
 Here's one or more paragraphs that describe the change.
@@ -346,6 +369,31 @@ Significant changes should add the following header, which moves them to the top
 significance: significant
 ```
 
+The following categories of release notes are supported (see `maintainers/build-release-notes.py`):
+- Breaking Changes
+- Features
+- Improvements
+- Fixes
+- Packaging
+- Development
+- Miscellany
+
+The `credits` field, if present, gives credit to the author of the patch in the release notes with a message like "Many thanks to (your-name) for this" and linking to GitHub or Forgejo profiles if listed.
+
+If you are forward-porting a change from CppNix, please credit the original author, and optionally credit yourself.
+When adding credits metadata for people external to the project and deciding whether to put in a `display_name`, consider what they are generally known as in the community; even if you know their full name (e.g. from their GitHub profile), we suggest only adding it as a display name if that is what they go by in the community.
+There are multiple reasons we follow this practice, but it boils down to privacy and consent: we would rather not capture full names that are not widely used in the community without the consent of the parties involved, even if they are publicly available.
+As of this writing, the entries with full names as `display_name` are either members of the CppNix team or people who added them themselves.
+
+The names specified in `credits` are used as keys to look up the authorship info in `doc/manual/change-authors.yml`.
+The only mandatory part is that every key appearing in `credits` has an entry present in `change-authors.yml`.
+All of the following properties are optional; you can specify `{}` as the metadata if you want a simple non-hyperlinked mention.
+The following properties are supported:
+
+- `display_name`: display name used in place of the key when showing names, if present.
+- `forgejo`: Forgejo username. The name in the release notes will be a link to this, if present.
+- `github`: GitHub username, used if `forgejo` is not set, again making a link.
+
 ### Build process
 
 Releases have a precomputed `rl-MAJOR.MINOR.md`, and no `rl-next.md`.

doc/manual/src/contributing/testing.md

@@ -433,9 +433,6 @@ I grepped `src/` for `get[eE]nv\("` to find the mentions in Lix code.
 - `NIX_PROFILE` - Selects which profile `nix-env` will operate on. Documented elsewhere.
 - `NIX_SSHOPTS` - Options passed to `ssh(1)` when using a ssh remote store.
   Incorrectly documented on `nix-copy-closure` which is *surely* not the only place they are used??
-- `_NIX_TEST_NO_LSOF` - Used on non-Linux, non-macOS platforms to disable using `lsof` when finding gc roots.
-
-  Since https://git.lix.systems/lix-project/lix/issues/156 was fixed, this should probably just be removed as it was a bad workaround for a macOS issue.
 - `_NIX_TEST_GC_SYNC_1` - Path to a pipe that is used to block the GC briefly to validate invariants from the test suite.
 - `_NIX_TEST_GC_SYNC_2` - Path to a pipe that is used to block the GC briefly to validate invariants from the test suite.
 - `_NIX_TEST_FREE_SPACE_FILE` - Path to a file containing a decimal number with the free space that the GC is to believe it has.

doc/manual/src/release-notes/rl-2.90.md

@@ -0,0 +1,929 @@
+# Lix 2.90 "Vanilla Ice Cream" (FIXME date)
+
+
+# Lix 2.90.0 (FIXME date)
+
+## Breaking Changes
+- Deprecate the online flake registries and vendor the default registry [fj#183](https://git.lix.systems/lix-project/lix/issues/183) [fj#110](https://git.lix.systems/lix-project/lix/issues/110) [fj#116](https://git.lix.systems/lix-project/lix/issues/116) [#8953](https://github.com/NixOS/nix/issues/8953) [#9087](https://github.com/NixOS/nix/issues/9087) [cl/1127](https://gerrit.lix.systems/c/lix/+/1127)
+
+  The online flake registry [https://channels.nixos.org/flake-registry.json](https://channels.nixos.org/flake-registry.json) is not pinned in any way,
+  and the targets of the indirections can both update or change entirely at any
+  point. Furthermore, it is refetched on every use of a flake reference, even if
+  there is a local flake reference, and even if you are offline (which breaks).
+
+  For now, we deprecate the (any) online flake registry, and vendor a copy of the
+  current online flake registry. This makes it work offline, and ensures that
+  it won't change in the future.
+
+  Many thanks to [julia](https://git.lix.systems/midnightveil) for this.
+- Enforce syscall filtering and no-new-privileges on Linux [cl/1063](https://gerrit.lix.systems/c/lix/+/1063)
+
+  In order to improve consistency of the build environment, system call filtering and no-new-privileges are now unconditionally enabled on Linux.
+  The `filter-syscalls` and `allow-new-privileges` options which could be used to disable these features under some circumstances have been removed.
+
+  In order to support building on architectures without libseccomp support, the option to disable syscall filtering at build time remains.
+  However, other uses of this option are heavily discouraged, since it would reduce the security of the sandbox substantially.
+
+  Many thanks to [alois31](https://git.lix.systems/alois31) for this.
+- Overhaul `nix flake update` and `nix flake lock` UX [#8817](https://github.com/NixOS/nix/pull/8817)
+
+  The interface for creating and updating lock files has been overhauled:
+
+  - [`nix flake lock`](@docroot@/command-ref/new-cli/nix3-flake-lock.md) only creates lock files and adds missing inputs now.
+  It will *never* update existing inputs.
+
+  - [`nix flake update`](@docroot@/command-ref/new-cli/nix3-flake-update.md) does the same, but *will* update inputs.
+  - Passing no arguments will update all inputs of the current flake, just like it already did.
+  - Passing input names as arguments will ensure only those are updated. This replaces the functionality of `nix flake lock --update-input`
+  - To operate on a flake outside the current directory, you must now pass `--flake path/to/flake`.
+
+  - The flake-specific flags `--recreate-lock-file` and `--update-input` have been removed from all commands operating on installables.
+  They are superceded by `nix flake update`.
+
+  Many thanks to [iFreilicht](https://github.com/iFreilicht), [Lunaphied](https://git.lix.systems/Lunaphied), and [Théophane Hufschmitt](https://github.com/thufschmitt) for this.
+- `nix profile` now allows referring to elements by human-readable name, and no longer accepts indices [#8678](https://github.com/NixOS/nix/pull/8678) [cl/978](https://gerrit.lix.systems/c/lix/+/978) [cl/980](https://gerrit.lix.systems/c/lix/+/980)
+
+  [`nix profile`](@docroot@/command-ref/new-cli/nix3-profile.md) now uses names to refer to installed packages when running [`list`](@docroot@/command-ref/new-cli/nix3-profile-list.md), [`remove`](@docroot@/command-ref/new-cli/nix3-profile-remove.md) or [`upgrade`](@docroot@/command-ref/new-cli/nix3-profile-upgrade.md) as opposed to indices. Indices have been removed. Profile element names are generated when a package is installed and remain the same until the package is removed.
+
+  **Warning**: The `manifest.nix` file used to record the contents of profiles has changed. Lix will automatically upgrade profiles to the new version when you modify the profile. After that, the profile can no longer be used by older versions of Lix.
+
+  Many thanks to [iFreilicht](https://github.com/iFreilicht), [Qyriad](https://git.lix.systems/Qyriad), and [Eelco Dolstra](https://github.com/edolstra) for this.
+- `builtins.nixVersion` and `builtins.langVersion` return fixed values [cl/558](https://gerrit.lix.systems/c/lix/+/558) [cl/1144](https://gerrit.lix.systems/c/lix/+/1144)
+
+  `builtins.nixVersion` now returns a fixed value `"2.18.3-lix"`.
+
+  `builtins.langVersion` returns a fixed value `6`, matching CppNix 2.18.
+
+  This prevents feature detection assuming that features that exist in Nix
+  post-Lix-branch-off might exist, even though the Lix version is greater than
+  the Nix version.
+
+  In the future, check for builtins for feature detection. If a feature cannot be
+  detected by *those* means, please file a Lix bug.
+
+  Many thanks to [jade](https://git.lix.systems/jade) for this.
+- Rename all the libraries nixexpr, nixstore, etc to lixexpr, lixstore, etc
+
+  The Lix C++ API libraries have had the following changes:
+  - Includes moved from `include/nix/` to `include/lix/`
+  - `pkg-config` files renamed from `nix-expr` to `lix-expr` and so on.
+  - Libraries renamed from `libnixexpr.so` to `liblixexpr.so` and so on.
+
+  There are other changes between Nix 2.18 and Lix, since these APIs are not
+  stable. However, this change in particular is a deliberate compatibility break
+  to force downstreams linking to Lix to specifically handle Lix and avoid Lix
+  accidentally getting ensnared in compatibility code for newer CppNix.
+
+  Migration path:
+
+  - expr.hh      -> lix/libexpr/expr.hh
+  - nix/config.h -> lix/config.h
+
+  To apply this migration automatically, remove all `<nix/>` from includes, so `#include <nix/expr.hh>` -> `#include <expr.hh>`.
+  Then, the correct paths will be resolved from the tangled mess, and the clang-tidy automated fix will work.
+
+  Then run the following for out of tree projects (header filter is set to only fix instances in headers in `../src` relative to the compiler's working directory, as would be the case in nix-eval-jobs or other things built with meson, e.g.):
+
+  ```console
+  lix_root=$HOME/lix
+  (cd $lix_root/clang-tidy && nix develop -c 'meson setup build && ninja -C build')
+  run-clang-tidy -checks='-*,lix-fixincludes' -load=$lix_root/clang-tidy/build/liblix-clang-tidy.so -p build/ -header-filter '\.\./src/.*\.h' -fix src
+  ```
+
+  Many thanks to [jade](https://git.lix.systems/jade) for this.
+
+## Features
+- Experimental REPL support for documentation comments using `:doc` [cl/564](https://gerrit.lix.systems/c/lix/+/564)
+
+  Using `:doc` in the REPL now supports showing documentation comments when defined on a function.
+
+  Previously this was only able to document builtins, however it now will show comments defined on a lambda as well.
+
+  This support is experimental and relies on an embedded version of [nix-doc](https://github.com/lf-/nix-doc).
+
+  The logic also supports limited Markdown formatting of doccomments and should easily support any [RFC 145](https://github.com/NixOS/rfcs/blob/master/rfcs/0145-doc-strings.md)
+  compatible documentation comments in addition to simple commented documentation.
+
+  Many thanks to [Lunaphied](https://git.lix.systems/Lunaphied) and [jade](https://git.lix.systems/jade) for this.
+- Add `repl-overlays` option [#10203](https://github.com/NixOS/nix/pull/10203) [cl/504](https://gerrit.lix.systems/c/lix/+/504)
+
+  A `repl-overlays` option has been added, which specifies files that can overlay
+  and modify the top-level bindings in `nix repl`. For example, with the
+  following contents in `~/.config/nix/repl.nix`:
+
+  ```nix
+  info: final: prev: let
+    optionalAttrs = predicate: attrs:
+      if predicate
+      then attrs
+      else {};
+  in
+    optionalAttrs (prev ? legacyPackages && prev.legacyPackages ? ${info.currentSystem})
+    {
+      pkgs = prev.legacyPackages.${info.currentSystem};
+    }
+  ```
+
+  We can run `nix repl` and use `pkgs` to refer to `legacyPackages.${currentSystem}`:
+
+  ```ShellSession
+  $ nix repl --repl-overlays ~/.config/nix/repl.nix nixpkgs
+  Lix 2.90.0
+  Type :? for help.
+  Loading installable 'flake:nixpkgs#'...
+  Added 5 variables.
+  Loading 'repl-overlays'...
+  Added 6 variables.
+  nix-repl> pkgs.bash
+  «derivation /nix/store/g08b5vkwwh0j8ic9rkmd8mpj878rk62z-bash-5.2p26.drv»
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) for this.
+- Add a builtin `addDrvOutputDependencies` [#7910](https://github.com/NixOS/nix/issues/7910) [#9216](https://github.com/NixOS/nix/pull/9216)
+
+  This builtin allows taking a `drvPath`-like string and turning it into a string
+  with context such that, when it lands in a derivation, it will create
+  dependencies on *all the outputs* in its closure (!). Although `drvPath` does this
+  today, this builtin starts forming a path to migrate to making `drvPath` have a
+  more normal and less surprising string context behaviour (see linked issue and
+  PR for more details).
+
+  Many thanks to [John Ericson](https://github.com/ericson2314) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Enter the `--debugger` when `builtins.trace` is called if `debugger-on-trace` is set [#9914](https://github.com/NixOS/nix/pull/9914)
+
+  If the `debugger-on-trace` option is set and `--debugger` is given,
+  `builtins.trace` calls will behave similarly to `builtins.break` and will enter
+  the debug REPL. This is useful for determining where warnings are being emitted
+  from.
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) for this.
+- Add an option `enable-core-dumps` that enables core dumps from builds [cl/1088](https://gerrit.lix.systems/c/lix/+/1088)
+
+  In the past, Lix disabled core dumps by setting the soft `RLIMIT_CORE` to 0
+  unconditionally. Although this rlimit could be altered from the builder since
+  it is just the soft limit, this was kind of annoying to do. By passing
+  `--option enable-core-dumps true` to an offending build, one can now cause the
+  core dumps to be handled by the system in the normal way (winding up in
+  `coredumpctl`, say, on Linux).
+
+  Many thanks to [julia](https://git.lix.systems/midnightveil) for this.
+- Add new `eval-system` setting [#4093](https://github.com/NixOS/nix/pull/4093)
+
+  Add a new `eval-system` option.
+  Unlike `system`, it just overrides the value of `builtins.currentSystem`.
+  This is more useful than overriding `system`, because you can build these derivations on remote builders which can work on the given system.
+  In contrast, `system` also effects scheduling which will cause Lix to build those derivations locally even if that doesn't make sense.
+
+  `eval-system` only takes effect if it is non-empty.
+  If empty (the default) `system` is used as before, so there is no breakage.
+
+  Many thanks to [matthewbauer](https://github.com/matthewbauer) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- add `--store-path` argument to `nix upgrade-nix`, to manually specify the Nix to upgrade to [cl/953](https://gerrit.lix.systems/c/lix/+/953)
+
+  `nix upgrade-nix` by default downloads a manifest to find the new Nix version to upgrade to, but now you can specify `--store-path` to upgrade Nix to an arbitrary version from the Nix store.
+
+  Many thanks to [Qyriad](https://git.lix.systems/Qyriad) for this.
+
+## Improvements
+- `nix flake check` logs the checks [#8882](https://github.com/NixOS/nix/issues/8882) [#8893](https://github.com/NixOS/nix/pull/8893) [cl/259](https://gerrit.lix.systems/c/lix/+/259) [cl/260](https://gerrit.lix.systems/c/lix/+/260) [cl/261](https://gerrit.lix.systems/c/lix/+/261) [cl/262](https://gerrit.lix.systems/c/lix/+/262)
+
+  `nix flake check` now logs the checks it runs and the derivations it evaluates:
+
+  ```
+  $ nix flake check -v
+  evaluating flake...
+  checking flake output 'checks'...
+  checking derivation 'checks.aarch64-darwin.ghciwatch-tests'...
+  derivation evaluated to /nix/store/nh7dlvsrhds4cxl91mvgj4h5cbq6skmq-ghciwatch-test-0.3.0.drv
+  checking derivation 'checks.aarch64-darwin.ghciwatch-clippy'...
+  derivation evaluated to /nix/store/9cb5a6wmp6kf6hidqw9wphidvb8bshym-ghciwatch-clippy-0.3.0.drv
+  checking derivation 'checks.aarch64-darwin.ghciwatch-doc'...
+  derivation evaluated to /nix/store/8brdd3jbawfszpbs7vdpsrhy80as1il8-ghciwatch-doc-0.3.0.drv
+  checking derivation 'checks.aarch64-darwin.ghciwatch-fmt'...
+  derivation evaluated to /nix/store/wjhs0l1njl5pyji53xlmfjrlya0wmz8p-ghciwatch-fmt-0.3.0.drv
+  checking derivation 'checks.aarch64-darwin.ghciwatch-audit'...
+  derivation evaluated to /nix/store/z0mps8dyj2ds7c0fn0819y5h5611033z-ghciwatch-audit-0.3.0.drv
+  checking flake output 'packages'...
+  checking derivation 'packages.aarch64-darwin.default'...
+  derivation evaluated to /nix/store/41abbdyglw5x9vcsvd89xan3ydjf8d7r-ghciwatch-0.3.0.drv
+  checking flake output 'apps'...
+  checking flake output 'devShells'...
+  checking derivation 'devShells.aarch64-darwin.default'...
+  derivation evaluated to /nix/store/bc935gz7dylzmcpdb5cczr8gngv8pmdb-nix-shell.drv
+  running 5 flake checks...
+  warning: The check omitted these incompatible systems: aarch64-linux, x86_64-darwin, x86_64-linux
+  Use '--all-systems' to check all.
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt), [Raito Bezarius](https://git.lix.systems/raito), and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Add an option `always-allow-substitutes` to ignore `allowSubstitutes` in derivations [#8047](https://github.com/NixOS/nix/pull/8047)
+
+  You can set this setting to force a system to always allow substituting even
+  trivial derivations like `pkgs.writeText`. This is useful for
+  [`nix-fast-build --skip-cached`][skip-cached] and similar to be able to also
+  ignore trivial derivations.
+
+  [skip-cached]: https://github.com/Mic92/nix-fast-build?tab=readme-ov-file#avoiding-redundant-package-downloads
+
+  Many thanks to [lovesegfault](https://github.com/lovesegfault) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Concise error printing in `nix repl` [#9928](https://github.com/NixOS/nix/pull/9928) [cl/811](https://gerrit.lix.systems/c/lix/+/811)
+
+  Previously, if an element of a list or attribute set threw an error while
+  evaluating, `nix repl` would print the entire error (including source location
+  information) inline. This output was clumsy and difficult to parse:
+
+  ```
+  nix-repl> { err = builtins.throw "uh oh!"; }
+  { err = «error:
+         … while calling the 'throw' builtin
+           at «string»:1:9:
+              1| { err = builtins.throw "uh oh!"; }
+               |         ^
+
+         error: uh oh!»; }
+  ```
+
+  Now, only the error message is displayed, making the output much more readable.
+  ```
+  nix-repl> { err = builtins.throw "uh oh!"; }
+  { err = «error: uh oh!»; }
+  ```
+
+  However, if the whole expression being evaluated throws an error, source
+  locations and (if applicable) a stack trace are printed, just like you'd expect:
+
+  ```
+  nix-repl> builtins.throw "uh oh!"
+  error:
+         … while calling the 'throw' builtin
+           at «string»:1:1:
+              1| builtins.throw "uh oh!"
+               | ^
+
+         error: uh oh!
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) for this.
+- Show all FOD errors with `nix build --keep-going` [cl/1108](https://gerrit.lix.systems/c/lix/+/1108)
+
+  `nix build --keep-going` now behaves consistently with `nix-build --keep-going`. This means
+  that if e.g. multiple FODs fail to build, all hash mismatches are displayed.
+
+  Many thanks to [ma27](https://git.lix.systems/ma27) for this.
+- Duplicate attribute reports are more accurate [cl/557](https://gerrit.lix.systems/c/lix/+/557)
+
+  Duplicate attribute errors are now more accurate, showing the path at which an error was detected rather than the full, possibly longer, path that caused the error.
+  Error reports are now
+  ```ShellSession
+  $ nix eval --expr '{ a.b = 1; a.b.c.d = 1; }'
+  error: attribute 'a.b' already defined at «string»:1:3
+         at «string»:1:12:
+              1| { a.b = 1; a.b.c.d = 1;
+               |            ^
+  ```
+  instead of
+  ```ShellSession
+  $ nix eval --expr '{ a.b = 1; a.b.c.d = 1; }'
+  error: attribute 'a.b.c.d' already defined at «string»:1:3
+         at «string»:1:12:
+              1| { a.b = 1; a.b.c.d = 1;
+               |            ^
+  ```
+
+  Many thanks to [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Reduce eval memory usage and wall time [#9658](https://github.com/NixOS/nix/pull/9658) [cl/207](https://gerrit.lix.systems/c/lix/+/207)
+
+  Reduce the size of the `Env` struct used in the evaluator by a pointer, or 8 bytes on most modern machines.
+  This reduces memory usage during eval by around 2% and wall time by around 3%.
+
+  Many thanks to [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Warn on unknown settings anywhere in the command line [#10701](https://github.com/NixOS/nix/pull/10701)
+
+  All `nix` commands will now properly warn when an unknown option is specified anywhere in the command line.
+
+  Before:
+
+  ```console
+  $ nix-instantiate --option foobar baz --expr '{}'
+  warning: unknown setting 'foobar'
+  $ nix-instantiate '{}' --option foobar baz --expr
+  $ nix eval --expr '{}' --option foobar baz
+  { }
+  ```
+
+  After:
+
+  ```console
+  $ nix-instantiate --option foobar baz --expr '{}'
+  warning: unknown setting 'foobar'
+  $ nix-instantiate '{}' --option foobar baz --expr
+  warning: unknown setting 'foobar'
+  $ nix eval --expr '{}' --option foobar baz
+  warning: unknown setting 'foobar'
+  { }
+  ```
+
+  Many thanks to [Cole Helbling](https://github.com/cole-h) for this.
+- Nested debuggers are no longer supported [#9920](https://github.com/NixOS/nix/pull/9920)
+
+  Previously, evaluating an expression that throws an error in the debugger would
+  enter a second, nested debugger:
+
+  ```
+  nix-repl> builtins.throw "what"
+  error: what
+
+
+  Starting REPL to allow you to inspect the current state of the evaluator.
+
+  Welcome to Nix 2.18.1. Type :? for help.
+
+  nix-repl>
+  ```
+
+  Now, it just prints the error message like `nix repl`:
+
+  ```
+  nix-repl> builtins.throw "what"
+  error:
+         … while calling the 'throw' builtin
+           at «string»:1:1:
+              1| builtins.throw "what"
+               | ^
+
+         error: what
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) for this.
+- Find GC roots using libproc on Darwin [cl/723](https://gerrit.lix.systems/c/lix/+/723)
+
+  Previously, the garbage collector found runtime roots on Darwin by shelling out to `lsof -n -w -F n` then parsing the result. The version of `lsof` packaged in Nixpkgs is very slow on Darwin, so Lix now uses `libproc` directly to speed up GC root discovery, in some tests taking 250ms now instead of 40s.
+
+  Many thanks to [Artemis Tosini](https://git.lix.systems/artemist) for this.
+- Increase default stack size on macOS [#9860](https://github.com/NixOS/nix/pull/9860)
+
+  Increase the default stack size on macOS to the same value as on Linux, subject to system restrictions to maximum stack size.
+  This should reduce the number of stack overflow crashes on macOS when evaluating Nix code with deep call stacks.
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) for this.
+- Show more log context for failed builds [#9670](https://github.com/NixOS/nix/pull/9670)
+
+  Show 25 lines of log tail instead of 10 for failed builds.
+  This increases the chances of having useful information in the shown logs.
+
+  Many thanks to [DavHau](https://github.com/DavHau) for this.
+- rename 'nix show-config' to 'nix config show' [#7672](https://github.com/NixOS/nix/issues/7672) [#9477](https://github.com/NixOS/nix/pull/9477) [cl/993](https://gerrit.lix.systems/c/lix/+/993)
+
+  `nix show-config` was renamed to `nix config show` to be more consistent with the rest of the command-line interface.
+
+  Running `nix show-config` will now print a deprecation warning saying to use `nix config show` instead.
+
+  Many thanks to [Théophane Hufschmitt](https://github.com/thufschmitt) and [ma27](https://git.lix.systems/ma27) for this.
+- Print derivation paths in `nix eval` [cl/446](https://gerrit.lix.systems/c/lix/+/446)
+
+  `nix eval` previously printed derivations as attribute sets, so commands that print derivations (e.g. `nix eval nixpkgs#bash`) would infinitely loop and segfault.
+  It now prints the `.drv` path the derivation generates instead.
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) for this.
+- Add an option `--unpack` to unpack archives in `nix store prefetch-file` [#9805](https://github.com/NixOS/nix/pull/9805) [cl/224](https://gerrit.lix.systems/c/lix/+/224)
+
+  It is now possible to fetch an archive then NAR-hash it (as in, hash it in the
+  same manner as `builtins.fetchTarball` or fixed-output derivations with
+  recursive hash type) in one command.
+
+  Example:
+
+  ```
+  ~ » nix store prefetch-file --name source --unpack https://git.lix.systems/lix-project/lix/archive/2.90-beta.1.tar.gz
+  Downloaded 'https://git.lix.systems/lix-project/lix/archive/2.90-beta.1.tar.gz' to '/nix/store/yvfqnq52ryjc3janw02ziv7kr6gd0cs1-source' (hash 'sha256-REWlo2RYHfJkxnmZTEJu3Cd/2VM+wjjpPy7Xi4BdDTQ=').
+  ```
+
+  Many thanks to [yshui](https://github.com/yshui) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- REPL printing improvements [#9931](https://github.com/NixOS/nix/pull/9931) [#10208](https://github.com/NixOS/nix/pull/10208) [cl/375](https://gerrit.lix.systems/c/lix/+/375) [cl/492](https://gerrit.lix.systems/c/lix/+/492)
+
+  The REPL printer has been improved to do the following:
+  - If a string is passed to `:print`, it is printed literally to the screen
+  - Structures will be printed as multiple lines when necessary
+
+  Before:
+
+  ```
+  nix-repl> { attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
+  { attrs = { ... }; list = [ ... ]; list' = [ ... ]; }
+
+  nix-repl> :p { attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
+  { attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
+
+  nix-repl> :p "meow"
+  "meow"
+  ```
+
+  After:
+
+  ```
+  nix-repl> { attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
+  {
+    attrs = { ... };
+    list = [ ... ];
+    list' = [ ... ];
+  }
+
+  nix-repl> :p { attrs = { a = { b = { c = { }; }; }; }; list = [ 1 ]; list' = [ 1 2 3 ]; }
+  {
+    attrs = {
+      a = {
+        b = {
+          c = { };
+        };
+      };
+    };
+    list = [ 1 ];
+    list' = [
+      1
+      2
+      3
+    ];
+  }
+
+  nix-repl> :p "meow"
+  meow
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Coercion errors include the failing value [#561](https://github.com/NixOS/nix/issues/561) [#9754](https://github.com/NixOS/nix/pull/9754)
+
+  The `error: cannot coerce a <TYPE> to a string` message now includes the value
+  which caused the error.
+
+  Before:
+
+  ```
+         error: cannot coerce a set to a string
+  ```
+
+  After:
+
+  ```
+         error: cannot coerce a set to a string: { aesSupport = «thunk»;
+         avx2Support = «thunk»; avx512Support = «thunk»; avxSupport = «thunk»;
+         canExecute = «thunk»; config = «thunk»; darwinArch = «thunk»; darwinMinVersion
+         = «thunk»; darwinMinVersionVariable = «thunk»; darwinPlatform = «thunk»; «84
+         attributes elided»}
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- New-cli flake commands that expect derivations now print the failing value and its type [cl/1177](https://gerrit.lix.systems/c/lix/+/1177)
+
+  In errors like `flake output attribute 'legacyPackages.x86_64-linux.lib' is not a derivation or path`, the message now includes the failing value and type.
+
+  Before:
+
+  ```
+      error: flake output attribute 'nixosConfigurations.yuki.config' is not a derivation or path
+  ````
+
+  After:
+
+  ```
+      error: expected flake output attribute 'nixosConfigurations.yuki.config' to be a derivation or path but found a set: { appstream = «thunk»; assertions = «thunk»; boot = { bcache = «thunk»; binfmt = «thunk»; binfmtMiscRegistrations = «thunk»; blacklistedKernelModules = «thunk»; bootMount = «thunk»; bootspec = «thunk»; cleanTmpDir = «thunk»; consoleLogLevel = «thunk»; «43 attributes elided» }; «48 attributes elided» }
+  ```
+
+  Many thanks to [Qyriad](https://git.lix.systems/Qyriad) for this.
+- Type errors include the failing value [#561](https://github.com/NixOS/nix/issues/561) [#9753](https://github.com/NixOS/nix/pull/9753)
+
+  In errors like `value is an integer while a list was expected`, the message now
+  includes the failing value.
+
+  Before:
+
+  ```
+         error: value is a set while a string was expected
+  ```
+
+  After:
+
+  ```
+         error: expected a string but found a set: { ghc810 = «thunk»;
+         ghc8102Binary = «thunk»; ghc8107 = «thunk»; ghc8107Binary = «thunk»;
+         ghc865Binary = «thunk»; ghc90 = «thunk»; ghc902 = «thunk»; ghc92 = «thunk»;
+         ghc924Binary = «thunk»; ghc925 = «thunk»;  «17 attributes elided»}
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Visual clutter in `--debugger` is reduced [#9919](https://github.com/NixOS/nix/pull/9919)
+
+  Before:
+  ```
+  info: breakpoint reached
+
+
+  Starting REPL to allow you to inspect the current state of the evaluator.
+
+  Welcome to Nix 2.20.0pre20231222_dirty. Type :? for help.
+
+  nix-repl> :continue
+  error: uh oh
+
+
+  Starting REPL to allow you to inspect the current state of the evaluator.
+
+  Welcome to Nix 2.20.0pre20231222_dirty. Type :? for help.
+
+  nix-repl>
+  ```
+
+  After:
+
+  ```
+  info: breakpoint reached
+
+  Nix 2.20.0pre20231222_dirty debugger
+  Type :? for help.
+  nix-repl> :continue
+  error: uh oh
+
+  nix-repl>
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- REPL now supports CTRL+Z to suspend
+
+  Editline is now built with SIGTSTP support, so now typing CTRL+Z in the REPL will suspend the REPL and allow it to be resumed later or backgrounded.
+
+  Many thanks to [Qyriad](https://git.lix.systems/Qyriad) for this.
+- Allow single quotes in nix-shell shebangs [#8470](https://github.com/NixOS/nix/pull/8470)
+
+  Example:
+
+  ```bash
+  #! /usr/bin/env nix-shell
+  #! nix-shell -i bash --packages 'terraform.withPlugins (plugins: [ plugins.openstack ])'
+  ```
+
+  Many thanks to [ncfavier](https://github.com/ncfavier) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- reintroduce shortened `-E` form for `--expr` to new CLI [cl/605](https://gerrit.lix.systems/c/lix/+/605)
+
+  In the old CLI, it was possible to supply a shorter `-E` flag instead of fully
+  specifying `--expr` every time you wished to provide an expression that would
+  be evaluated to produce the given command's input. This was retained for the
+  `--file` flag when the new CLI utilities were written with `-f`, but `-E` was
+  dropped.
+
+  We now restore the `-E` short form for better UX. This is most useful for
+  `nix eval` but most any command that takes an Installable argument should benefit
+  from it as well.
+
+  Many thanks to [Lunaphied](https://git.lix.systems/Lunaphied) for this.
+- Source locations are printed more consistently in errors [#561](https://github.com/NixOS/nix/issues/561) [#9555](https://github.com/NixOS/nix/pull/9555)
+
+  Source location information is now included in error messages more
+  consistently. Given this code:
+
+  ```nix
+  let
+    attr = {foo = "bar";};
+    key = {};
+  in
+    attr.${key}
+  ```
+
+  Previously, Nix would show this unhelpful message when attempting to evaluate
+  it:
+
+  ```
+  error:
+         … while evaluating an attribute name
+
+         error: value is a set while a string was expected
+  ```
+
+  Now, the error message displays where the problematic value was found:
+
+  ```
+  error:
+         … while evaluating an attribute name
+
+           at bad.nix:4:11:
+
+              3|   key = {};
+              4| in attr.${key}
+               |           ^
+              5|
+
+         error: expected a string but found a set: { }
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Some stack overflow segfaults are fixed [#9616](https://github.com/NixOS/nix/issues/9616) [#9617](https://github.com/NixOS/nix/pull/9617) [cl/205](https://gerrit.lix.systems/c/lix/+/205)
+
+  The number of nested function calls has been restricted, to detect and report
+  infinite function call recursions. The default maximum call depth is 10,000 and
+  can be set with [the `max-call-depth`
+  option](@docroot@/command-ref/conf-file.md#conf-max-call-depth).
+
+  This fixes segfaults or the following unhelpful error message in many cases:
+
+      error: stack overflow (possible infinite recursion)
+
+  Before:
+
+  ```
+  $ nix-instantiate --eval --expr '(x: x x) (x: x x)'
+  Segmentation fault: 11
+  ```
+
+  After:
+
+  ```
+  $ nix-instantiate --eval --expr '(x: x x) (x: x x)'
+  error: stack overflow
+
+         at «string»:1:14:
+              1| (x: x x) (x: x x)
+               |              ^
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Warn about ignored client settings [cl/1026](https://gerrit.lix.systems/c/lix/+/1026)
+
+  Emit a warning for every client-provided setting the daemon ignores because the requesting client is not run by a trusted user.
+  Previously this was only a debug message.
+
+  Many thanks to [jade](https://git.lix.systems/jade) for this.
+- Better error reporting for `with` expressions [#9658](https://github.com/NixOS/nix/pull/9658) [cl/207](https://gerrit.lix.systems/c/lix/+/207)
+
+  `with` expressions using non-attrset values to resolve variables are now reported with proper positions.
+
+  Previously an incorrect `with` expression would report no position at all, making it hard to determine where the error originated:
+
+  ```
+  nix-repl> with 1; a
+  error:
+         … <borked>
+
+           at «none»:0: (source not available)
+
+         error: value is an integer while a set was expected
+  ```
+
+  Now position information is preserved and reported as with most other errors:
+
+  ```
+  nix-repl> with 1; a
+  error:
+         … while evaluating the first subexpression of a with expression
+           at «string»:1:1:
+              1| with 1; a
+               | ^
+
+         error: expected a set but found an integer: 1
+  ```
+
+  Many thanks to [eldritch horrors](https://git.lix.systems/pennae) for this.
+
+## Fixes
+- Fix nested flake input `follows` [#6621](https://github.com/NixOS/nix/pull/6621) [cl/994](https://gerrit.lix.systems/c/lix/+/994)
+
+  Previously nested-input overrides were ignored; that is, the following did not
+  override anything, in spite of the `nix3-flake` manual documenting it working:
+
+  ```
+  {
+    inputs = {
+      foo.url = "github:bar/foo";
+      foo.inputs.bar.inputs.nixpkgs = "nixpkgs";
+    };
+  }
+  ```
+
+  This is useful to avoid the 1000 instances of nixpkgs problem without having
+  each flake in the dependency tree to expose all of its transitive dependencies
+  for modification.
+
+  Many thanks to [Kha](https://github.com/Kha) and [ma27](https://git.lix.systems/ma27) for this.
+- Fix CVE-2024-27297 (GHSA-2ffj-w4mj-pg37) [cl/266](https://gerrit.lix.systems/c/lix/+/266)
+
+  Since Lix fixed-output derivations run in the host network namespace (which we
+  wish to change in the future, see
+  [lix#285](https://git.lix.systems/lix-project/lix/issues/285)), they may open
+  abstract-namespace Unix sockets to each other and to programs on the host. Lix
+  contained a now-fixed time-of-check/time-of-use vulnerability where one
+  derivation could send writable handles to files in their final location in the
+  store to another over an abstract-namespace Unix socket, exit, then the other
+  derivation could wait for Lix to hash the paths and overwrite them.
+
+  The impact of this vulnerability is that two malicious fixed-output derivations
+  could create a poisoned path for the sources to Bash or similarly important
+  software containing a backdoor, leading to local privilege execution.
+
+  CppNix advisory: https://github.com/NixOS/nix/security/advisories/GHSA-2ffj-w4mj-pg37
+
+  Many thanks to [puck](https://git.lix.systems/puck), [jade](https://git.lix.systems/jade), [Théophane Hufschmitt](https://github.com/thufschmitt), [Tom Bereknyei](https://github.com/tomberek), and [Valentin Gagarin](https://github.com/fricklerhandwerk) for this.
+- `--debugger` can now access bindings from `let` expressions [#8827](https://github.com/NixOS/nix/issues/8827) [#9918](https://github.com/NixOS/nix/pull/9918)
+
+  Breakpoints and errors in the bindings of a `let` expression can now access
+  those bindings in the debugger. Previously, only the body of `let` expressions
+  could access those bindings.
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) for this.
+- Fix handling of truncated `.drv` files. [#9673](https://github.com/NixOS/nix/pull/9673)
+
+  Previously a `.drv` that was truncated in the middle of a string would case nix to enter an infinite loop, eventually exhausting all memory and crashing.
+
+  Many thanks to [eldritch horrors](https://git.lix.systems/pennae) for this.
+- The `--debugger` will start more reliably in `let` expressions and function calls [#6649](https://github.com/NixOS/nix/issues/6649) [#9917](https://github.com/NixOS/nix/pull/9917)
+
+  Previously, if you attempted to evaluate this file with the debugger:
+
+  ```nix
+  let
+    a = builtins.trace "before inner break" (
+      builtins.break "hello"
+    );
+    b = builtins.trace "before outer break" (
+      builtins.break a
+    );
+  in
+    b
+  ```
+
+  Lix would correctly enter the debugger at `builtins.break a`, but if you asked
+  it to `:continue`, it would skip over the `builtins.break "hello"` expression
+  entirely.
+
+  Now, Lix will correctly enter the debugger at both breakpoints.
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Creating setuid/setgid binaries with fchmodat2 is now prohibited by the build sandbox [#10501](https://github.com/NixOS/nix/pull/10501)
+
+  The build sandbox blocks any attempt to create setuid/setgid binaries, but didn't check
+  for the use of the `fchmodat2` syscall which was introduced in Linux 6.6 and is used by
+  glibc >=2.39. This is fixed now.
+
+  Many thanks to [ma27](https://git.lix.systems/ma27) for this.
+- consistent order of lambda formals in printed expressions [#9874](https://github.com/NixOS/nix/pull/9874)
+
+  Always print lambda formals in lexicographic order rather than the internal, creation-time based symbol order.
+  This makes printed formals independent of the context they appear in.
+
+  Many thanks to [eldritch horrors](https://git.lix.systems/pennae) for this.
+- fix duplicate attribute error positions for `inherit` [#9874](https://github.com/NixOS/nix/pull/9874)
+
+  When an inherit caused a duplicate attribute error, the position of the error was not reported correctly, placing the error with the inherit itself or at the start of the bindings block instead of the offending attribute name.
+
+  Many thanks to [eldritch horrors](https://git.lix.systems/pennae) for this.
+- `inherit (x) ...` evaluates `x` only once [#9847](https://github.com/NixOS/nix/pull/9847)
+
+  `inherit (x) a b ...` now evaluates the expression `x` only once for all inherited attributes rather than once for each inherited attribute.
+  This does not usually have a measurable impact, but side-effects (such as `builtins.trace`) would be duplicated and expensive expressions (such as derivations) could cause a measurable slowdown.
+
+  Many thanks to [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Store paths are allowed to start with `.` [#912](https://github.com/NixOS/nix/issues/912) [#9867](https://github.com/NixOS/nix/pull/9867) [#9091](https://github.com/NixOS/nix/pull/9091) [#9095](https://github.com/NixOS/nix/pull/9095) [#9120](https://github.com/NixOS/nix/pull/9120) [#9121](https://github.com/NixOS/nix/pull/9121) [#9122](https://github.com/NixOS/nix/pull/9122) [#9130](https://github.com/NixOS/nix/pull/9130) [#9219](https://github.com/NixOS/nix/pull/9219) [#9224](https://github.com/NixOS/nix/pull/9224)
+
+  Leading periods were allowed by accident in Nix 2.4. The Nix team has considered this to be a bug, but this behavior has since been relied on by users, leading to unnecessary difficulties.
+  From now on, leading periods are officially, definitively supported. The names `.` and `..` are disallowed, as well as those starting with `.-` or `..-`.
+
+  Nix versions that denied leading periods are documented [in the issue](https://github.com/NixOS/nix/issues/912#issuecomment-1919583286).
+
+  Many thanks to [Robert Hensing](https://github.com/roberth) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- Fix `nix-env --query --drv-path --json` [#9257](https://github.com/NixOS/nix/pull/9257)
+
+  Fixed a bug where `nix-env --query` ignored `--drv-path` when `--json` was set.
+
+  Many thanks to [Artturin](https://github.com/Artturin) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- re-evaluate cached evaluation errors [cl/771](https://gerrit.lix.systems/c/lix/+/771)
+
+  "cached failure of [expr]" errors have been removed: expressions already in the
+  eval cache as a failure will now simply be re-evaluated, removing the need to
+  set `--no-eval-cache` or similar to see the error.
+
+  Many thanks to [Qyriad](https://git.lix.systems/Qyriad) for this.
+- Interrupting builds in the REPL works more than once [cl/1097](https://gerrit.lix.systems/c/lix/+/1097)
+
+  Builds in the REPL can be interrupted by pressing Ctrl+C.
+  Previously, this only worked once per REPL session; further attempts would be ignored.
+  This issue is now fixed, so that builds can be canceled consistently.
+
+  Many thanks to [alois31](https://git.lix.systems/alois31) for this.
+- In the debugger, `while evaluating the attribute` errors now include position information [#9915](https://github.com/NixOS/nix/pull/9915)
+
+  Before:
+
+  ```
+  0: while evaluating the attribute 'python311.pythonForBuild.pkgs'
+  0x600001522598
+  ```
+
+  After:
+
+  ```
+  0: while evaluating the attribute 'python311.pythonForBuild.pkgs'
+  /nix/store/hg65h51xnp74ikahns9hyf3py5mlbbqq-source/overrides/default.nix:132:27
+
+     131|
+     132|       bootstrappingBase = pkgs.${self.python.pythonAttr}.pythonForBuild.pkgs;
+        |                           ^
+     133|     in
+  ```
+
+  Many thanks to [wiggles](https://git.lix.systems/rbt) for this.
+- Include phase reporting in log file for ssh-ng builds [#9280](https://github.com/NixOS/nix/pull/9280)
+
+  Store phase information of remote builds run via `ssh-ng` remotes in the local log file, matching logging behavior of local builds.
+
+  Many thanks to [r-vdp](https://github.com/r-vdp) for this.
+- Fix `ssh-ng://` remotes not respecting `--substitute-on-destination` [#9600](https://github.com/NixOS/nix/pull/9600)
+
+  `nix copy ssh-ng://` now respects `--substitute-on-destination`, as does `nix-copy-closure` and other commands that operate on remote `ssh-ng` stores.
+  Previously this was always set by `builders-use-substitutes` setting.
+
+  Many thanks to [SharzyL](https://github.com/SharzyL) for this.
+- using `nix profile` on `/nix/var/nix/profiles/default` no longer breaks `nix upgrade-nix` [cl/952](https://gerrit.lix.systems/c/lix/+/952)
+
+  On non-NixOS, Nix is conventionally installed into a `nix-env` style profile at /nix/var/nix/profiles/default.
+  Like any `nix-env` profile, using `nix profile` on it automatically migrates it to a `nix profile` style profile, which is incompatible with `nix-env`.
+  `nix upgrade-nix` previously relied solely on `nix-env` to do the upgrade, but now will work fine with either kind of profile.
+
+  Many thanks to [Qyriad](https://git.lix.systems/Qyriad) for this.
+
+## Packaging
+- Lix turns more internal bugs into crashes [cl/797](https://gerrit.lix.systems/c/lix/+/797) [cl/626](https://gerrit.lix.systems/c/lix/+/626)
+
+  Lix now enables build options such as trapping on signed overflow and enabling
+  libstdc++ assertions by default. These may find new bugs in Lix, which will
+  present themselves as Lix processes aborting, potentially without an error
+  message.
+
+  If Lix processes abort on your machine, this is a bug. Please file a bug,
+  ideally with the core dump (or information from it).
+
+  On Linux, run `coredumpctl list`, find the crashed process's PID at
+  the bottom of the list, then run `coredumpctl info THE-PID`. You can then paste
+  the output into a bug report.
+
+  On macOS, open the Console app from Applications/Utilities, select Crash
+  Reports, select the crash report in question. Right click on it, select Open In
+  Finder, then include that file in your bug report. [See the Apple
+  documentation][apple-crashreport] for more details.
+
+  [apple-crashreport]: https://developer.apple.com/documentation/xcode/acquiring-crash-reports-and-diagnostic-logs#Locate-crash-reports-and-memory-logs-on-the-device
+
+  Many thanks to [jade](https://git.lix.systems/jade) for this.
+- Stop vendoring toml11 [cl/675](https://gerrit.lix.systems/c/lix/+/675)
+
+  We don't apply any patches to it, and vendoring it locks users into
+  bugs (it hasn't been updated since its introduction in late 2021).
+
+  Many thanks to [winter](https://git.lix.systems/winter) for this.
+- Lix is built with meson [cl/580](https://gerrit.lix.systems/c/lix/+/580) [cl/627](https://gerrit.lix.systems/c/lix/+/627) [cl/628](https://gerrit.lix.systems/c/lix/+/628) [cl/707](https://gerrit.lix.systems/c/lix/+/707) [cl/711](https://gerrit.lix.systems/c/lix/+/711) [cl/712](https://gerrit.lix.systems/c/lix/+/712) [cl/719](https://gerrit.lix.systems/c/lix/+/719)
+
+  Lix is built exclusively with the meson build system thanks to a huge team-wide
+  effort, and the legacy `make`/`autoconf` based build system has been removed
+  altogether. This improves maintainability of Lix, enables things like saving
+  20% of compile times with precompiled headers, and generally makes the build
+  less able to produce obscure incremental compilation bugs.
+
+  Non-Nix-based downstream packaging needs rewriting accordingly.
+
+  Many thanks to [Qyriad](https://git.lix.systems/Qyriad), [eldritch horrors](https://git.lix.systems/pennae), [jade](https://git.lix.systems/jade), [wiggles](https://git.lix.systems/rbt), and [winter](https://git.lix.systems/winter) for this.
+- Upstart scripts removed [cl/574](https://gerrit.lix.systems/c/lix/+/574)
+
+  Upstart scripts have been removed from Lix, since Upstart is obsolete and has
+  not been shipped by any major distributions for many years. If these are
+  necessary to your use case, please back port them to your packaging.
+
+  Many thanks to [jade](https://git.lix.systems/jade) for this.
+
+## Development
+- Clang build timing analysis [cl/587](https://gerrit.lix.systems/c/lix/+/587)
+
+  We now have Clang build profiling available, which generates Chrome
+  tracing files for each compilation unit. To enable it, run `meson configure
+  build -Dprofile-build=enabled` in a Clang stdenv (`nix develop
+  .#native-clangStdenvPackages`) then rerun the compilation.
+
+  If you want to make the build go faster, do a clang build with meson, then run
+  `maintainers/buildtime_report.sh build`, then contemplate how to improve the
+  build time.
+
+  You can also look at individual object files' traces in
+  <https://ui.perfetto.dev>.
+
+  See [the wiki page][improving-build-times-wiki] for more details on how to do
+  this.
+
+  [improving-build-times-wiki]: https://wiki.lix.systems/link/8#bkmrk-page-title
+
+## Miscellany
+- Disallow empty search regex in `nix search` [#9481](https://github.com/NixOS/nix/pull/9481)
+
+  [`nix search`](@docroot@/command-ref/new-cli/nix3-search.md) now requires a search regex to be passed. To show all packages, use `^`.
+
+  Many thanks to [iFreilicht](https://github.com/iFreilicht) and [eldritch horrors](https://git.lix.systems/pennae) for this.
+- `nix repl` history is saved more reliably [cl/1164](https://gerrit.lix.systems/c/lix/+/1164)
+
+  `nix repl` now saves its history file after each line, rather than at the end
+  of the session; ensuring that it will remember what you typed even after it
+  crashes.
+
+  Many thanks to [puck](https://git.lix.systems/puck) for this.

flake.nix

@@ -59,7 +59,7 @@
         (Run `touch .nocontribmsg` to hide this message.)
       '';
 
-      officialRelease = true;
+      officialRelease = false;
 
       # Set to true to build the release notes for the next release.
       buildUnreleasedNotes = true;
@@ -84,6 +84,8 @@
       ];
       systems = linuxSystems ++ darwinSystems;
 
+      # If you add something here, please update the list in doc/manual/src/contributing/hacking.md.
+      # Thanks~
       crossSystems = [
         "armv6l-linux"
         "armv7l-linux"
@@ -195,14 +197,19 @@
             busybox-sandbox-shell = final.busybox-sandbox-shell or final.default-busybox-sandbox-shell;
           };
 
+          pegtl = final.nix.passthru.pegtl;
+
           # Export the patched version of boehmgc that Lix uses into the overlay
           # for consumers of this flake.
-          boehmgc-nix = final.nix.boehmgc-nix;
+          boehmgc-nix = final.nix.passthru.boehmgc-nix;
           # And same thing for our build-release-notes package.
-          build-release-notes = final.nix.build-release-notes;
+          build-release-notes = final.nix.passthru.build-release-notes;
         };
     in
     {
+      # for repl debugging
+      inherit self;
+
       # A Nixpkgs overlay that overrides the 'nix' and
       # 'nix.perl-bindings' packages.
       overlays.default = overlayFor (p: p.stdenv);
@@ -233,6 +240,11 @@
           }
         );
 
+        # Completion tests for the Nix REPL.
+        repl-completion = forAllSystems (
+          system: nixpkgsFor.${system}.native.callPackage ./tests/repl-completion.nix { }
+        );
+
         # Perl bindings for various platforms.
         perlBindings = forAllSystems (system: nixpkgsFor.${system}.native.nix.passthru.perl-bindings);
 
@@ -330,6 +342,7 @@
           rl-next = self.hydraJobs.rl-next.${system}.user;
           # Will be empty attr set on i686-linux, and filtered out by forAvailableSystems.
           pre-commit = self.hydraJobs.pre-commit.${system};
+          repl-completion = self.hydraJobs.repl-completion.${system};
         }
         // (lib.optionalAttrs (builtins.elem system linux64BitSystems)) {
           dockerImage = self.hydraJobs.dockerImage.${system};
@@ -379,7 +392,7 @@
               nix = pkgs.callPackage ./package.nix {
                 inherit stdenv officialRelease versionSuffix;
                 busybox-sandbox-shell = pkgs.busybox-sandbox-shell or pkgs.default-busybox-sandbox;
-                internalApiDocs = true;
+                internalApiDocs = false;
               };
               pre-commit = self.hydraJobs.pre-commit.${pkgs.system} or { };
             in

justfile

@@ -9,8 +9,8 @@ clean:
     rm -rf build
 
 # Prepare meson for building
-setup:
-    meson setup build --prefix="$PWD/outputs/out"
+setup *OPTIONS:
+    meson setup build --prefix="$PWD/outputs/out" $mesonFlags {{ OPTIONS }}
 
 # Build lix
 build *OPTIONS:

maintainers/build-release-notes.py

@@ -20,6 +20,8 @@ SIGNIFICANCECES = {
 
 # This is just hardcoded for better validation. If you think there should be
 # more of them, feel free to add more.
+#
+# Please update doc/manual/src/contributing/hacking.md if you do. Thanks~
 CATEGORIES = [
     'Breaking Changes',
     'Features',

maintainers/buildtime_report.sh

@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/usr/bin/env bash
 
 # Generates a report of build time based on a meson build using -ftime-trace in
 # Clang.

maintainers/release-notes

@@ -1,179 +0,0 @@
-#!/usr/bin/env nix-shell
-#!nix-shell -i bash ../shell.nix -I nixpkgs=channel:nixos-unstable-small
-#                                   ^^^^^^^
-#                Only used for bash. shell.nix goes to the flake.
-
-# --- CONFIGURATION ---
-
-# This does double duty for
-# - including rl-next
-# - marking where to insert new links (right after)
-SUMMARY_MARKER_LINE='release-notes/rl-next.md'
-
-# --- LIB ---
-
-log() {
-  echo 1>&2 "release-notes:" "$@"
-}
-logcmd() {
-  local cmd="$1"
-  shift
-  logcmd2 "$cmd" "${*@Q}" "$cmd" "$@"
-}
-logcmd2() {
-  local fakecmd="$1"
-  local fakeargs="$2"
-  shift
-  shift
-  printf 1>&2 "release-notes: \033[34;1m$fakecmd\033[0m "
-  echo "$fakeargs" 1>&2
-  "$@"
-}
-die() {
-  # ANSI red
-  printf 1>&2 "release-notes: \033[31;1merror:\033[0m"
-  echo 1>&2 "" "$@"
-  exit 1
-}
-confirm() {
-  local answer
-  echo 1>&2 "$@" "[y/n]"
-  read -r answer
-  case "$answer" in
-    y|Y|yes|Yes|YES)
-      return 0
-      ;;
-    n|N|no|No|NO)
-      return 1
-      ;;
-    *)
-      echo 1>&2 "please answer y or n"
-      confirm "$@"
-      ;;
-  esac
-}
-report_done() {
-  logcmd2 "git" "show" git -c pager.show=false show
-  printf 1>&2 "release-notes: \033[32;1mdone\033[0m\n"
-}
-
-# --- PARSE ARGS ---
-
-if [[ $# -gt 0 ]]; then
-  die "Release notes takes no arguments, but make sure to set VERSION."
-fi
-
-# --- CHECKS ---
-
-if [[ ! -e flake.nix ]] || [[ ! -e .git ]]; then
-  die "must run in repo root"
-  exit 1
-fi
-
-# repo must be clean
-if ! git diff --quiet; then
-  die "repo is dirty, please commit or stash changes"
-fi
-
-if ! git diff --quiet --cached; then
-  die "repo has staged changes, please commit or stash them"
-fi
-
-if ! grep -F "$SUMMARY_MARKER_LINE" doc/manual/src/SUMMARY.md >/dev/null; then
-  # would have been nice to catch this early, but won't be worth the extra infra
-  die "SUMMARY.md is missing the marker line '$SUMMARY_MARKER_LINE', which would be used for inserting a new release notes page. Please fix the script."
-fi
-
-if [[ ! -n "${VERSION:-}" ]]; then
-  die "please set the VERSION environment variable before invoking this script"
-  exit 1
-fi
-
-# version_major_minor:      MAJOR.MINOR
-# version_full:             MAJOR.MINOR.PATCH
-# IS_PATCH:                 true if this is a patch release; append instead of create
-if grep -E '^[0-9]+\.[0-9]+$' <<< "$VERSION" >/dev/null; then
-  log 'is minor'
-  IS_PATCH=false
-  version_full="$VERSION.0"
-  version_major_minor="$VERSION"
-elif grep -E '^[0-9]+\.[0-9]+\.0$' <<< "$VERSION" >/dev/null; then
-  log 'is minor (.0)'
-  IS_PATCH=false
-  version_full="$VERSION"
-  version_major_minor="$(echo "$VERSION" | sed -e 's/\.0$//')"
-elif grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' <<< "$VERSION" >/dev/null; then
-  log 'is patch'
-  IS_PATCH=true
-  version_full="$VERSION"
-  version_major_minor="$(echo "$VERSION" | sed -e 's/\.[0-9]*$//')"
-else
-  die "VERSION must be MAJOR.MINOR[.PATCH], where each is a number, e.g. 2.20 or 2.20.1 (VERSION was set to $VERSION)"
-fi
-
-unset VERSION
-
-log "version_major_minor=$version_major_minor"
-log "version_full=$version_full"
-log "IS_PATCH=$IS_PATCH"
-
-basename=rl-${version_major_minor}.md
-file=doc/manual/src/release-notes/$basename
-
-if ! $IS_PATCH; then
-  if [[ -e $file ]]; then
-    die "release notes file $file already exists. If you'd like to make a minor release, pass a patch version, e.g. 2.20.1"
-  fi
-fi
-
-# --- DEFAULTS ---
-
-if [[ ! -n "${DATE:-}" ]]; then
-  DATE="$(date +%Y-%m-%d)"
-  log "DATE not set, using $DATE"
-fi
-
-case "$DATE" in
-  [0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9])
-    ;;
-  *)
-    die "DATE must be YYYY-MM-DD, e.g. 2021-12-31 (DATE was set to $DATE)"
-    ;;
-esac
-
-# --- DO THE WORK ---
-
-# menu
-title="Release $version_major_minor ($DATE)"
-# section on page
-section_title="Release $version_full ($DATE)"
-
-(
-  # TODO add minor number, and append?
-  echo "# $section_title"
-  echo
-  build-release-notes --change-authors doc/manual/change-authors.yml doc/manual/rl-next
-) | tee -a $file
-
-log "Wrote $file"
-
-if ! $IS_PATCH; then
-  NEW_SUMMARY_LINE="  - [$title](release-notes/$basename)"
-
-  # find the marker line, insert new link after it
-  escaped_marker="$(echo "$SUMMARY_MARKER_LINE" | sed -e 's/\//\\\//g' -e 's/ /\\ /g')"
-  escaped_line="$(echo "$NEW_SUMMARY_LINE" | sed -e 's/\//\\\//g' -e 's/ /\\ /g')"
-  logcmd sed -i -e "/$escaped_marker/a $escaped_line" doc/manual/src/SUMMARY.md
-fi
-
-for f in doc/manual/rl-next/*.md; do
-  if [[ config != "$(basename $f)" ]]; then
-    logcmd git rm $f
-  fi
-done
-
-logcmd git add $file doc/manual/src/SUMMARY.md
-logcmd git status
-logcmd git commit -m "release notes: $version_full"
-
-report_done

meson.build

@@ -142,6 +142,16 @@ else
   cpp_pch = []
 endif
 
+# gcc 12 is known to miscompile some coroutine-based code quite horribly,
+# causing (among other things) copies of move-only objects and the double
+# frees one would expect when the objects are unique_ptrs. these problems
+# often show up as memory corruption when nesting generators (since we do
+# treat generators like owned memory) and will cause inexplicable crashs.
+assert(
+  cxx.get_id() != 'gcc' or cxx.version().version_compare('>=13'),
+  'GCC 12 and earlier are known to miscompile lix coroutines, use GCC 13 or clang.'
+)
+
 
 # Translate some historical and Mesony CPU names to Lixy CPU names.
 # FIXME(Qyriad): the 32-bit x86 code is not tested right now, because cross compilation for Lix
@@ -167,6 +177,7 @@ message('canonical Nix system name:', host_system)
 
 is_linux = host_machine.system() == 'linux'
 is_darwin = host_machine.system() == 'darwin'
+is_freebsd = host_machine.system() == 'freebsd'
 is_x64 = host_machine.cpu_family() == 'x86_64'
 
 # Per-platform arguments that you should probably pass to shared_module() invocations.
@@ -222,7 +233,8 @@ brotli = [
 
 openssl = dependency('libcrypto', 'openssl', required : true)
 
-aws_sdk = dependency('aws-cpp-sdk-core', required : false)
+# FIXME: confirm we actually support such old versions of aws-sdk-cpp
+aws_sdk = dependency('aws-cpp-sdk-core', required : false, version : '>=1.8')
 aws_sdk_transfer = dependency('aws-cpp-sdk-transfer', required : aws_sdk.found(), fallback : ['aws_sdk', 'aws_cpp_sdk_transfer_dep'])
 if aws_sdk.found()
   # The AWS pkg-config adds -std=c++11.
@@ -234,12 +246,6 @@ if aws_sdk.found()
     links : true,
     sources : true,
   )
-  s = aws_sdk.version().split('.')
-  configdata += {
-    'AWS_VERSION_MAJOR': s[0].to_int(),
-    'AWS_VERSION_MINOR': s[1].to_int(),
-    'AWS_VERSION_PATCH': s[2].to_int(),
-  }
   aws_sdk_transfer = aws_sdk_transfer.partial_dependency(
     compile_args : false,
     includes : true,
@@ -291,6 +297,14 @@ gtest = [
 
 toml11 = dependency('toml11', version : '>=3.7.0', required : true, method : 'cmake')
 
+pegtl = dependency(
+  'pegtl',
+  version : '>=3.2.7',
+  required : true,
+  method : 'cmake',
+  modules : [ 'taocpp::pegtl' ],
+)
+
 nlohmann_json = dependency('nlohmann_json', required : true)
 
 # lix-doc is a Rust project provided via buildInputs and unfortunately doesn't have any way to be detected.
@@ -339,8 +353,6 @@ endif
 # that busybox sh won't run busybox applets as builtins (which would break our sandbox).
 
 lsof = find_program('lsof', native : true)
-bison = find_program('bison', native : true)
-flex = find_program('flex', native : true)
 
 # This is how Nix does generated headers...
 # other instances of header generation use a very similar command.
@@ -430,6 +442,7 @@ add_project_arguments(
   '-Wimplicit-fallthrough',
   '-Werror=switch',
   '-Werror=switch-enum',
+  '-Werror=unused-result',
   '-Wdeprecated-copy',
   '-Wignored-qualifiers',
   # Enable assertions in libstdc++ by default. Harmless on libc++. Benchmarked
@@ -441,7 +454,9 @@ add_project_arguments(
   language : 'cpp',
 )
 
-if cxx.get_id() in ['gcc', 'clang']
+# We turn off the production UBSan if the slower dev UBSan is requested, to
+# give better diagnostics.
+if cxx.get_id() in ['gcc', 'clang'] and 'undefined' not in get_option('b_sanitize')
   # 2024-03-24: jade benchmarked the default sanitize reporting in clang and got
   # a regression of about 10% on hackage-packages.nix with clang. So we are trapping instead.
   #
@@ -456,12 +471,23 @@ if cxx.get_id() in ['gcc', 'clang']
   add_project_arguments(sanitize_args, language: 'cpp')
   add_project_link_arguments(sanitize_args, language: 'cpp')
 endif
+# Clang's default of -no-shared-libsan on Linux causes link errors; on macOS it defaults to shared.
+# GCC defaults to shared libsan so is fine.
+if cxx.get_id() == 'clang' and get_option('b_sanitize') != ''
+  add_project_link_arguments('-shared-libsan', language : 'cpp')
+endif
 
 add_project_link_arguments('-pthread', language : 'cpp')
 if cxx.get_linker_id() in ['ld.bfd', 'ld.gold']
   add_project_link_arguments('-Wl,--no-copy-dt-needed-entries', language : 'cpp')
 endif
 
+if is_freebsd
+  # FreeBSD's `environ` is defined in `crt1.o`, not `libc.so`,
+  # so the linker thinks it's undefined
+  add_project_link_arguments('-Wl,-z,undefs', language: 'cpp')
+endif
+
 # Generate Chromium tracing files for each compiled file, which enables
 # maintainers/buildtime_report.sh BUILD-DIR to simply work in clang builds.
 #

meson/cleanup-install.bash

@@ -1,50 +0,0 @@
-#!/usr/bin/env bash
-# Meson will call this with an absolute path to Bash.
-# The shebang is just for convenience.
-
-# The parser and lexer tab are generated via custom Meson targets in src/libexpr/meson.build,
-# but Meson doesn't support marking only part of a target for install. The generation creates
-# both headers (parser-tab.hh, lexer-tab.hh) and source files (parser-tab.cc, lexer-tab.cc),
-# and we definitely want the former installed, but not the latter. This script is added to
-# Meson's install steps to correct this, as the logic for it is just complex enough to
-# warrant separate and careful handling, because both Meson's configured include directory
-# may or may not be an absolute path, and DESTDIR may or may not be set at all, but can't be
-# manipulated in Meson logic.
-
-set -euo pipefail
-
-echo "cleanup-install: removing Meson-placed C++ sources from dest includedir"
-
-if [[ "${1/--help/}" != "$1" ]]; then
-	echo "cleanup-install: this script should only be called from the Meson build system"
-	exit 1
-fi
-
-# Ensure the includedir was passed as the first argument
-# (set -u will make this fail otherwise).
-includedir="$1"
-# And then ensure that first argument is a directory that exists.
-if ! [[ -d "$1" ]]; then
-	echo "cleanup-install: this script should only be called from the Meson build system"
-	echo "argv[1] (${1@Q}) is not a directory"
-	exit 2
-fi
-
-# If DESTDIR environment variable is set, prepend it to the include dir.
-# Unfortunately, we cannot do this on the Meson side. We do have an environment variable
-# `MESON_INSTALL_DESTDIR_PREFIX`, but that will not refer to the include directory if
-# includedir has been set separately, which Lix's split-output derivation does.
-# We also cannot simply do an inline bash conditional like "${DESTDIR:=}" or similar,
-# because we need to specifically *join* DESTDIR and includedir with a slash, and *not*
-# have a slash if DESTDIR isn't set at all, since $includedir could be a relative directory.
-# Finally, DESTDIR is only available to us as an environment variable in these install scripts,
-# not in Meson logic.
-# Therefore, our best option is to have Meson pass this script the configured includedir,
-# and perform this dance with it and $DESTDIR.
-if [[ -n "${DESTDIR:-}" ]]; then
-	includedir="$DESTDIR/$includedir"
-fi
-
-# Intentionally not using -f.
-# If these files don't exist then our assumptions have been violated and we should fail.
-rm -v "$includedir/lix/libexpr/parser-tab.cc" "$includedir/lix/libexpr/lexer-tab.cc"

misc/pegtl.nix

@@ -0,0 +1,23 @@
+{
+  stdenv,
+  cmake,
+  ninja,
+  fetchFromGitHub,
+}:
+
+stdenv.mkDerivation {
+  pname = "pegtl";
+  version = "3.2.7";
+
+  src = fetchFromGitHub {
+    repo = "PEGTL";
+    owner = "taocpp";
+    rev = "refs/tags/3.2.7";
+    hash = "sha256-IV5YNGE4EWVrmg2Sia/rcU8jCuiBynQGJM6n3DCWTQU=";
+  };
+
+  nativeBuildInputs = [
+    cmake
+    ninja
+  ];
+}

package.nix

@@ -10,17 +10,16 @@
   boehmgc-nix ? __forDefaults.boehmgc-nix,
   boehmgc,
   nlohmann_json,
-  bison,
   build-release-notes ? __forDefaults.build-release-notes,
   boost,
   brotli,
   bzip2,
+  callPackage,
   cmake,
   curl,
   doxygen,
   editline-lix ? __forDefaults.editline-lix,
   editline,
-  flex,
   git,
   gtest,
   jq,
@@ -36,6 +35,7 @@
   meson,
   ninja,
   openssl,
+  pegtl ? __forDefaults.pegtl,
   pkg-config,
   python3,
   rapidcheck,
@@ -76,8 +76,10 @@
       configureFlags = prev.configureFlags or [ ] ++ [ (lib.enableFeature true "sigstop") ];
     });
 
-    lix-doc = pkgs.callPackage ./lix-doc/package.nix { };
-    build-release-notes = pkgs.callPackage ./maintainers/build-release-notes.nix { };
+    lix-doc = callPackage ./lix-doc/package.nix { };
+    build-release-notes = callPackage ./maintainers/build-release-notes.nix { };
+
+    pegtl = callPackage ./misc/pegtl.nix { };
   },
 }:
 let
@@ -210,8 +212,6 @@ stdenv.mkDerivation (finalAttrs: {
 
   nativeBuildInputs =
     [
-      bison
-      flex
       python3
       meson
       ninja
@@ -250,6 +250,7 @@ stdenv.mkDerivation (finalAttrs: {
       libsodium
       toml11
       lix-doc
+      pegtl
     ]
     ++ lib.optionals hostPlatform.isLinux [
       libseccomp
@@ -304,6 +305,9 @@ stdenv.mkDerivation (finalAttrs: {
       else
         appendToVar configureFlags "--disable-tests"
       fi
+
+      # Fix up /usr/bin/env shebangs relied on by the build
+      patchShebangs --build tests/ doc/manual/
     '';
 
   mesonBuildType = "debugoptimized";
@@ -379,7 +383,12 @@ stdenv.mkDerivation (finalAttrs: {
   # Export the patched version of boehmgc.
   # flake.nix exports that into its overlay.
   passthru = {
-    inherit (__forDefaults) boehmgc-nix editline-lix build-release-notes;
+    inherit (__forDefaults)
+      boehmgc-nix
+      editline-lix
+      build-release-notes
+      pegtl
+      ;
 
     inherit officialRelease;
 
@@ -392,6 +401,7 @@ stdenv.mkDerivation (finalAttrs: {
         bashInteractive,
         clang-tools,
         clangbuildanalyzer,
+        doxygen,
         glibcLocales,
         just,
         llvmPackages,
@@ -457,6 +467,10 @@ stdenv.mkDerivation (finalAttrs: {
               skopeo
               just
               nixfmt
+              # Included above when internalApiDocs is true, but we set that to
+              # false intentionally to save dev build time.
+              # To build them in a dev shell, you can set -Dinternal-api-docs=enabled when configuring.
+              doxygen
               # Load-bearing order. Must come before clang-unwrapped below, but after clang_tools above.
               stdenv.cc
             ]
@@ -476,7 +490,7 @@ stdenv.mkDerivation (finalAttrs: {
               # https://git.lix.systems/lix-project/lix/src/commit/7575db522e9008685c4009423398f6900a16bcce/src/nix/develop.cc#L240-L241
               # this is, of course, absurd.
               if [[ $name != lix-shell-env && $name != lix-shell-env-env ]]; then
-                return;
+                return
               fi
 
               PATH=$prefix/bin:$PATH
@@ -486,6 +500,11 @@ stdenv.mkDerivation (finalAttrs: {
               # Make bash completion work.
               XDG_DATA_DIRS+=:$out/share
 
+              if [[ ! -f ./.this-is-lix ]]; then
+                echo "Dev shell not started from inside a Lix repo, skipping repo setup" >&2
+                return
+              fi
+
               ${lib.optionalString (pre-commit-checks ? shellHook) pre-commit-checks.shellHook}
               # Allow `touch .nocontribmsg` to turn this notice off.
               if ! [[ -f .nocontribmsg ]]; then

perl/meson.build

@@ -65,5 +65,6 @@ if cxx.get_linker_id() in ['ld.bfd', 'ld.gold']
 endif
 
 libstore = dependency('lixstore', 'lix-store', required : true)
+libutil = dependency('lixutil', 'lix-util', required : true)
 
 subdir('lib/Nix')

releng/__init__.py

@@ -15,6 +15,7 @@ from . import version
 from . import cli
 from . import docker
 from . import docker_assemble
+from . import release_notes
 from . import gitutils
 
 
@@ -77,3 +78,4 @@ def reload():
     importlib.reload(docker)
     importlib.reload(docker_assemble)
     importlib.reload(gitutils)
+    importlib.reload(release_notes)

releng/create_release.xsh

@@ -6,12 +6,14 @@ from pathlib import Path
 import tempfile
 import hashlib
 import datetime
+
 from . import environment
 from .environment import RelengEnvironment
 from . import keys
 from . import docker
 from .version import VERSION, RELEASE_NAME, MAJOR
 from .gitutils import verify_are_on_tag, git_preconditions
+from . import release_notes
 
 $RAISE_SUBPROC_ERROR = True
 $XONSH_SHOW_TRACEBACK = True
@@ -104,17 +106,17 @@ def upload_drv_paths_and_outputs(env: RelengEnvironment, paths: list[str]):
         raise subprocess.CalledProcessError(rv, proc.args)
 
 
-def make_manifest(eval_result):
-    manifest = {vs['system']: vs['outputs']['out'] for vs in eval_result}
+def make_manifest(builds_by_system):
+
     def manifest_line(system, out):
         return f'  {system} = "{out}";'
 
     manifest_text = textwrap.dedent("""\
         # This file was generated by releng/create_release.xsh in Lix
         {{
-          {lines}
+        {lines}
         }}
-    """).format(lines='\n'.join(manifest_line(s, p) for (s, p) in manifest.items()))
+    """).format(lines='\n'.join(manifest_line(s, p) for (s, p) in builds_by_system.items()))
 
     return manifest_text
 
@@ -140,6 +142,18 @@ def sha256_file(f: Path):
     return hasher.hexdigest()
 
 
+def extract_builds_by_system(eval_result):
+    # This could be a dictionary comprehension, but we want to be absolutely
+    # sure we don't have duplicates.
+    ret = {}
+    for attr in eval_result:
+        if attr['attrPath'][0] != 'build':
+            continue
+        assert attr['system'] not in ret
+        ret[attr['system']] = attr['outputs']['out']
+    return ret
+
+
 def make_artifacts_dir(eval_result, d: Path):
     d.mkdir(exist_ok=True, parents=True)
     version_dir = d / 'lix' / f'lix-{VERSION}'
@@ -148,12 +162,14 @@ def make_artifacts_dir(eval_result, d: Path):
     tarballs_drv = next(p for p in eval_result if p['attr'] == 'tarballs')
     cp --no-preserve=mode -r @(tarballs_drv['outputs']['out'])/* @(version_dir)
 
+    builds_by_system = extract_builds_by_system(eval_result)
+
     # FIXME: upgrade-nix searches for manifest.nix at root, which is rather annoying
     with open(d / 'manifest.nix', 'w') as h:
-        h.write(make_manifest(eval_result))
+        h.write(make_manifest(builds_by_system))
 
     with open(version_dir / 'manifest.nix', 'w') as h:
-        h.write(make_manifest(eval_result))
+        h.write(make_manifest(builds_by_system))
 
     print('[+] Make sources tarball')
 
@@ -169,51 +185,7 @@ def make_artifacts_dir(eval_result, d: Path):
 
 
 def prepare_release_notes():
-    print('[+] Preparing release notes')
-    RELEASE_NOTES_PATH = Path('doc/manual/rl-next')
-
-    if RELEASE_NOTES_PATH.isdir():
-        notes_body = subprocess.check_output(['build-release-notes', '--change-authors', 'doc/manual/change-authors.yml', 'doc/manual/rl-next']).decode()
-    else:
-        # I guess nobody put release notes on their changes?
-        print('[-] Warning: seemingly missing any release notes, not worrying about it')
-        notes_body = ''
-
-    rl_path = Path(f'doc/manual/src/release-notes/rl-{MAJOR}.md')
-
-    existing_rl = ''
-    try:
-        with open(rl_path, 'r') as fh:
-            existing_rl = fh.read()
-    except FileNotFoundError:
-        pass
-
-    date = datetime.datetime.now().strftime('%Y-%m-%d')
-
-    minor_header = f'# Lix {VERSION} ({date})'
-
-    header = f'# Lix {MAJOR} "{RELEASE_NAME}"'
-    if existing_rl.startswith(header):
-        # strip the header off for minor releases
-        lines = existing_rl.splitlines()
-        header = lines[0]
-        existing_rl = '\n'.join(lines[1:])
-    else:
-        header += f' ({date})\n\n'
-
-    header += '\n' + minor_header + '\n'
-
-    notes = header
-    notes += notes_body
-    notes += "\n\n"
-    notes += existing_rl
-
-    # make pre-commit happy about one newline
-    notes = notes.rstrip()
-    notes += "\n"
-
-    with open(rl_path, 'w') as fh:
-        fh.write(notes)
+    rl_path = release_notes.build_release_notes_to_file()
 
     commit_msg = textwrap.dedent("""\
         release: release notes for {VERSION}
@@ -221,8 +193,8 @@ def prepare_release_notes():
         {RELENG_MSG}
     """).format(VERSION=VERSION, RELENG_MSG=RELENG_MSG)
 
-    git add @(rl_path)
-    git rm doc/manual/rl-next/*.md
+    git add @(rl_path) @(release_notes.SUMMARY)
+    git rm --ignore-unmatch 'doc/manual/rl-next/*.md'
 
     git commit -m @(commit_msg)
 

releng/release_notes.py

@@ -0,0 +1,81 @@
+from pathlib import Path
+import subprocess
+import datetime
+
+from .version import MAJOR, VERSION, RELEASE_NAME
+
+MANUAL = Path('doc/manual')
+RELEASE_NOTES_BASE = MANUAL / 'src/release-notes'
+VERSION_RL = RELEASE_NOTES_BASE / f'rl-{MAJOR}.md'
+SUMMARY = MANUAL / 'src/SUMMARY.md'
+
+def add_to_summary(date: str):
+    # N.B: This kind of duplicates gitutils.is_maintenance_branch, but it's a more clear
+    # check that allows potentially releasing a -rc without release notes being
+    # moved, then in .0 actually move the release notes in place.
+    if VERSION_RL.exists():
+        return
+
+    MARKER = '<!-- RELENG-AUTO-INSERTION-MARKER'
+
+    new_lines = []
+    for line in SUMMARY.read_text().splitlines():
+        new_lines.append(line)
+        if MARKER in line:
+            indent, _, _ = line.partition(MARKER)
+            new_lines.append(f'{indent}- [Lix {MAJOR} ({date})](release-notes/rl-{MAJOR}.md)')
+
+    # make pre-commit happy about one newline
+    text = '\n'.join(new_lines).rstrip()
+    text += '\n'
+    SUMMARY.write_text(text)
+
+def build_release_notes_to_file():
+    date = datetime.datetime.now().strftime('%Y-%m-%d')
+    add_to_summary(date)
+
+    print('[+] Preparing release notes')
+    RELEASE_NOTES_PATH = Path('doc/manual/rl-next')
+
+    if RELEASE_NOTES_PATH.is_dir():
+        notes_body = subprocess.check_output(['build-release-notes', '--change-authors', 'doc/manual/change-authors.yml', RELEASE_NOTES_PATH]).decode()
+    else:
+        # I guess nobody put release notes on their changes?
+        print('[-] Warning: seemingly missing any release notes, not worrying about it')
+        notes_body = ''
+
+    rl_path = Path(RELEASE_NOTES_BASE / f'rl-{MAJOR}.md')
+
+    existing_rl = ''
+    try:
+        with open(rl_path, 'r') as fh:
+            existing_rl = fh.read()
+    except FileNotFoundError:
+        pass
+
+    minor_header = f'# Lix {VERSION} ({date})'
+
+    header = f'# Lix {MAJOR} "{RELEASE_NAME}"'
+    if existing_rl.startswith(header):
+        # strip the header off for minor releases
+        lines = existing_rl.splitlines()
+        header = lines[0]
+        existing_rl = '\n'.join(lines[1:])
+    else:
+        header += f' ({date})\n\n'
+
+    header += '\n' + minor_header + '\n'
+
+    notes = header
+    notes += notes_body
+    notes += "\n\n"
+    notes += existing_rl
+
+    # make pre-commit happy about one newline
+    notes = notes.rstrip()
+    notes += "\n"
+
+    with open(rl_path, 'w') as fh:
+        fh.write(notes)
+
+    return rl_path