${name}${type'}
- ${name} ${listArgs args}
- !) since this allows re-using file names
-# - group related paths to ease readability
-# - always append new redirects to the end of the file
-# - redirects that should have been there but are missing can be inserted where they belong
-
-/expressions/expression-language /language/ 301!
-/expressions/language-values /language/values 301!
-/expressions/language-constructs /language/constructs 301!
-/expressions/language-operators /language/operators 301!
-/expressions/* /language/:splat 301!
-
-/package-management/basic-package-mgmt /command-ref/nix-env 301!
-
-/package-management/channels* /command-ref/nix-channel 301!
-
-/package-management/s3-substituter* /command-ref/new-cli/nix3-help-stores#s3-binary-cache-store 301!
diff --git a/doc/manual/src/advanced-topics/advanced-topics.md b/doc/manual/src/advanced-topics/advanced-topics.md
deleted file mode 100644
index 9a4d12a33..000000000
--- a/doc/manual/src/advanced-topics/advanced-topics.md
+++ /dev/null
@@ -1 +0,0 @@
-This section lists advanced topics related to builds and builds performance
diff --git a/doc/manual/src/advanced-topics/cores-vs-jobs.md b/doc/manual/src/advanced-topics/cores-vs-jobs.md
deleted file mode 100644
index 5a2e2ab0e..000000000
--- a/doc/manual/src/advanced-topics/cores-vs-jobs.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# Tuning Cores and Jobs
-
-Lix has two relevant settings with regards to how your CPU cores will
-be utilized: `cores` and `max-jobs`. This chapter will talk about what
-they are, how they interact, and their configuration trade-offs.
-
- - `max-jobs`\
- Dictates how many separate derivations will be built at the same
- time. If you set this to zero, the local machine will do no
- builds. Lix will still substitute from binary caches, and build
- remotely if remote builders are configured.
-
- - `cores`\
- Suggests how many cores each derivation should use. Similar to
- `make -j`.
-
-The `cores` setting determines the value of
-`NIX_BUILD_CORES`. `NIX_BUILD_CORES` is equal to `cores`, unless
-`cores` equals `0`, in which case `NIX_BUILD_CORES` will be the total
-number of cores in the system.
-
-The maximum number of consumed cores is a simple multiplication,
-`max-jobs` \* `NIX_BUILD_CORES`.
-
-The balance on how to set these two independent variables depends upon
-each builder's workload and hardware. Here are a few example scenarios
-on a machine with 24 cores:
-
-| `max-jobs` | `cores` | `NIX_BUILD_CORES` | Maximum Processes | Result |
-| --------------------- | ------------------ | ----------------- | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 1 | 24 | 24 | 24 | One derivation will be built at a time, each one can use 24 cores. Undersold if a job can’t use 24 cores. |
-| 4 | 6 | 6 | 24 | Four derivations will be built at once, each given access to six cores. |
-| 12 | 6 | 6 | 72 | 12 derivations will be built at once, each given access to six cores. This configuration is over-sold. If all 12 derivations being built simultaneously try to use all six cores, the machine's performance will be degraded due to extensive context switching between the 12 builds. |
-| 24 | 1 | 1 | 24 | 24 derivations can build at the same time, each using a single core. Never oversold, but derivations which require many cores will be very slow to compile. |
-| 24 | 0 | 24 | 576 | 24 derivations can build at the same time, each using all the available cores of the machine. Very likely to be oversold, and very likely to suffer context switches. |
-
-It is up to the derivations' build script to respect host's requested
-cores-per-build by following the value of the `NIX_BUILD_CORES`
-environment variable.
diff --git a/doc/manual/src/advanced-topics/diff-hook.md b/doc/manual/src/advanced-topics/diff-hook.md
deleted file mode 100644
index 367de6d6d..000000000
--- a/doc/manual/src/advanced-topics/diff-hook.md
+++ /dev/null
@@ -1,123 +0,0 @@
-# Verifying Build Reproducibility
-
-You can use Lix's `diff-hook` setting to compare build results. Note
-that this hook is only executed if the results differ; it is not used
-for determining if the results are the same.
-
-For purposes of demonstration, we'll use the following Nix file,
-`deterministic.nix` for testing:
-
-```nix
-let
- inherit (import {}) runCommand;
-in {
- stable = runCommand "stable" {} ''
- touch $out
- '';
-
- unstable = runCommand "unstable" {} ''
- echo $RANDOM > $out
- '';
-}
-```
-
-Additionally, `nix.conf` contains:
-
- diff-hook = /etc/nix/my-diff-hook
- run-diff-hook = true
-
-where `/etc/nix/my-diff-hook` is an executable file containing:
-
-```bash
-#!/bin/sh
-exec >&2
-echo "For derivation $3:"
-/run/current-system/sw/bin/diff -r "$1" "$2"
-```
-
-The diff hook is executed by the same user and group who ran the build.
-However, the diff hook does not have write access to the store path just
-built.
-
-# Spot-Checking Build Determinism
-
-Verify a path which already exists in the Nix store by passing `--check`
-to the build command.
-
-If the build passes and is deterministic, Lix will exit with a status
-code of 0:
-
-```console
-$ nix-build ./deterministic.nix --attr stable
-this derivation will be built:
- /nix/store/z98fasz2jqy9gs0xbvdj939p27jwda38-stable.drv
-building '/nix/store/z98fasz2jqy9gs0xbvdj939p27jwda38-stable.drv'...
-/nix/store/yyxlzw3vqaas7wfp04g0b1xg51f2czgq-stable
-
-$ nix-build ./deterministic.nix --attr stable --check
-checking outputs of '/nix/store/z98fasz2jqy9gs0xbvdj939p27jwda38-stable.drv'...
-/nix/store/yyxlzw3vqaas7wfp04g0b1xg51f2czgq-stable
-```
-
-If the build is not deterministic, Lix will exit with a status code of
-1:
-
-```console
-$ nix-build ./deterministic.nix --attr unstable
-this derivation will be built:
- /nix/store/cgl13lbj1w368r5z8gywipl1ifli7dhk-unstable.drv
-building '/nix/store/cgl13lbj1w368r5z8gywipl1ifli7dhk-unstable.drv'...
-/nix/store/krpqk0l9ib0ibi1d2w52z293zw455cap-unstable
-
-$ nix-build ./deterministic.nix --attr unstable --check
-checking outputs of '/nix/store/cgl13lbj1w368r5z8gywipl1ifli7dhk-unstable.drv'...
-error: derivation '/nix/store/cgl13lbj1w368r5z8gywipl1ifli7dhk-unstable.drv' may
-not be deterministic: output '/nix/store/krpqk0l9ib0ibi1d2w52z293zw455cap-unstable' differs
-```
-
-In the Lix daemon's log, we will now see:
-
-```
-For derivation /nix/store/cgl13lbj1w368r5z8gywipl1ifli7dhk-unstable.drv:
-1c1
-< 8108
----
-> 30204
-```
-
-Using `--check` with `--keep-failed` will cause Lix to keep the second
-build's output in a special, `.check` path:
-
-```console
-$ nix-build ./deterministic.nix --attr unstable --check --keep-failed
-checking outputs of '/nix/store/cgl13lbj1w368r5z8gywipl1ifli7dhk-unstable.drv'...
-note: keeping build directory '/tmp/nix-build-unstable.drv-0'
-error: derivation '/nix/store/cgl13lbj1w368r5z8gywipl1ifli7dhk-unstable.drv' may
-not be deterministic: output '/nix/store/krpqk0l9ib0ibi1d2w52z293zw455cap-unstable' differs
-from '/nix/store/krpqk0l9ib0ibi1d2w52z293zw455cap-unstable.check'
-```
-
-In particular, notice the
-`/nix/store/krpqk0l9ib0ibi1d2w52z293zw455cap-unstable.check` output. Lix
-has copied the build results to that directory where you can examine it.
-
-> []{#check-dirs-are-unregistered} **Note**
->
-> Check paths are not protected against garbage collection, and this
-> path will be deleted on the next garbage collection.
->
-> The path is guaranteed to be alive for the duration of
-> the `diff-hook`'s execution, but may be deleted any time after.
->
-> If the comparison is performed as part of automated tooling, please
-> use the diff-hook or author your tooling to handle the case where the
-> build was not deterministic and also a check path does not exist.
-
-`--check` is only usable if the derivation has been built on the system
-already. If the derivation has not been built Lix will fail with the
-error:
-
- error: some outputs of '/nix/store/hzi1h60z2qf0nb85iwnpvrai3j2w7rr6-unstable.drv'
- are not valid, so checking is not possible
-
-Run the build without `--check`, and then try with `--check` again.
diff --git a/doc/manual/src/advanced-topics/distributed-builds.md b/doc/manual/src/advanced-topics/distributed-builds.md
deleted file mode 100644
index 80443b53e..000000000
--- a/doc/manual/src/advanced-topics/distributed-builds.md
+++ /dev/null
@@ -1,159 +0,0 @@
-# Remote Builds
-
-Lix supports remote builds, where a local Lix installation can forward
-Nix builds to other machines. This allows multiple builds to be
-performed in parallel and allows Lix to perform multi-platform builds in
-a semi-transparent way. For instance, if you perform a build for a
-`x86_64-darwin` on an `i686-linux` machine, Lix can automatically
-forward the build to a `x86_64-darwin` machine, if available.
-
-To forward a build to a remote machine, it’s required that the remote
-machine is accessible via SSH and that it has Nix installed. You can
-test whether connecting to the remote Nix instance works, e.g.
-
-```console
-$ nix store ping --store ssh://mac
-```
-
-will try to connect to the machine named `mac`. It is possible to
-specify an SSH identity file as part of the remote store URI, e.g.
-
-```console
-$ nix store ping --store ssh://mac?ssh-key=/home/alice/my-key
-```
-
-Since builds should be non-interactive, the key should not have a
-passphrase. Alternatively, you can load identities ahead of time into
-`ssh-agent` or `gpg-agent`.
-
-If you get the error
-
-```console
-bash: nix-store: command not found
-error: cannot connect to 'mac'
-```
-
-then you need to ensure that the `PATH` of non-interactive login shells
-contains Nix.
-
-> **Warning**
->
-> If you are building via the Lix daemon (default on Linux and macOS), it is the Lix daemon user account (that is, `root`) that should have SSH access to a user (not necessarily `root`) on the remote machine.
->
-> Furthermore, `root` needs to have the public host keys for the remote system in its `.ssh/known_hosts`.
-> To add them to `known_hosts` for root, do `ssh-keyscan USER@HOST | sudo tee -a ~root/.ssh/known_hosts`.
->
-> If you can’t or don’t want to configure `root` to be able to access the remote machine, you can use a private Nix store instead by passing e.g. `--store ~/my-nix` when running a Nix command from the local machine.
-
-The list of remote machines can be specified on the command line or in
-the Lix configuration file. The former is convenient for testing. For
-example, the following command allows you to build a derivation for
-`x86_64-darwin` on a Linux machine:
-
-```console
-$ uname
-Linux
-
-$ nix build --impure \
- --expr '(with import { system = "x86_64-darwin"; }; runCommand "foo" {} "uname > $out")' \
- --builders 'ssh://mac x86_64-darwin'
-[1/0/1 built, 0.0 MiB DL] building foo on ssh://mac
-
-$ cat ./result
-Darwin
-```
-
-It is possible to specify multiple builders separated by a semicolon or
-a newline, e.g.
-
-```console
- --builders 'ssh://mac x86_64-darwin ; ssh://beastie x86_64-freebsd'
-```
-
-Each machine specification consists of the following elements, separated
-by spaces. Only the first element is required. To leave a field at its
-default, set it to `-`.
-
-1. The URI of the remote store in the format
- `ssh://[username@]hostname`, e.g. `ssh://nix@mac` or `ssh://mac`.
- For backward compatibility, `ssh://` may be omitted. The hostname
- may be an alias defined in your `~/.ssh/config`.
-
-2. A comma-separated list of Nix platform type identifiers, such as
- `x86_64-darwin`. It is possible for a machine to support multiple
- platform types, e.g., `i686-linux,x86_64-linux`. If omitted, this
- defaults to the local platform type.
-
-3. The SSH identity file to be used to log in to the remote machine. If
- omitted, SSH will use its regular identities.
-
-4. The maximum number of builds that Lix will execute in parallel on
- the machine. Typically this should be equal to the number of CPU
- cores. For instance, the machine `itchy` in the example will execute
- up to 8 builds in parallel.
-
-5. The “speed factor”, indicating the relative speed of the machine. If
- there are multiple machines of the right type, Lix will prefer the
- fastest, taking load into account.
-
-6. A comma-separated list of *supported features*. If a derivation has
- the `requiredSystemFeatures` attribute, then Lix will only perform
- the derivation on a machine that has the specified features. For
- instance, the attribute
-
- ```nix
- requiredSystemFeatures = [ "kvm" ];
- ```
-
- will cause the build to be performed on a machine that has the `kvm`
- feature.
-
-7. A comma-separated list of *mandatory features*. A machine will only
- be used to build a derivation if all of the machine’s mandatory
- features appear in the derivation’s `requiredSystemFeatures`
- attribute.
-
-8. The (base64-encoded) public host key of the remote machine. If omitted, SSH
- will use its regular known-hosts file. Specifically, the field is calculated
- via `base64 -w0 /etc/ssh/ssh_host_ed25519_key.pub`.
-
-For example, the machine specification
-
- nix@scratchy.labs.cs.uu.nl i686-linux /home/nix/.ssh/id_scratchy_auto 8 1 kvm
- nix@itchy.labs.cs.uu.nl i686-linux /home/nix/.ssh/id_scratchy_auto 8 2
- nix@poochie.labs.cs.uu.nl i686-linux /home/nix/.ssh/id_scratchy_auto 1 2 kvm benchmark
-
-specifies several machines that can perform `i686-linux` builds.
-However, `poochie` will only do builds that have the attribute
-
-```nix
-requiredSystemFeatures = [ "benchmark" ];
-```
-
-or
-
-```nix
-requiredSystemFeatures = [ "benchmark" "kvm" ];
-```
-
-`itchy` cannot do builds that require `kvm`, but `scratchy` does support
-such builds. For regular builds, `itchy` will be preferred over
-`scratchy` because it has a higher speed factor.
-
-Remote builders can also be configured in `nix.conf`, e.g.
-
- builders = ssh://mac x86_64-darwin ; ssh://beastie x86_64-freebsd
-
-Finally, remote builders can be configured in a separate configuration
-file included in `builders` via the syntax `@file`. For example,
-
- builders = @/etc/nix/machines
-
-causes the list of machines in `/etc/nix/machines` to be included. (This
-is the default.)
-
-If you want the builders to use caches, you likely want to set the
-option `builders-use-substitutes` in your local `nix.conf`.
-
-To build only on remote builders and disable building on the local
-machine, you can use the option `--max-jobs 0`.
diff --git a/doc/manual/src/advanced-topics/post-build-hook.md b/doc/manual/src/advanced-topics/post-build-hook.md
deleted file mode 100644
index 508d945ae..000000000
--- a/doc/manual/src/advanced-topics/post-build-hook.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# Using the `post-build-hook`
-
-# Implementation Caveats
-
-Here we use the post-build hook to upload to a binary cache. This is a
-simple and working example, but it is not suitable for all use cases.
-
-The post build hook program runs after each executed build, and blocks
-the build loop. The build loop exits if the hook program fails.
-
-Concretely, this implementation will make Lix slow or unusable when the
-internet is slow or unreliable.
-
-A more advanced implementation might pass the store paths to a
-user-supplied daemon or queue for processing the store paths outside of
-the build loop.
-
-# Prerequisites
-
-This tutorial assumes you have [configured an S3-compatible binary
-cache](../package-management/s3-substituter.md), and that the `root`
-user's default AWS profile can upload to the bucket.
-
-# Set up a Signing Key
-
-Use `nix-store --generate-binary-cache-key` to create our public and
-private signing keys. We will sign paths with the private key, and
-distribute the public key for verifying the authenticity of the paths.
-
-```console
-# nix-store --generate-binary-cache-key example-nix-cache-1 /etc/nix/key.private /etc/nix/key.public
-# cat /etc/nix/key.public
-example-nix-cache-1:1/cKDz3QCCOmwcztD2eV6Coggp6rqc9DGjWv7C0G+rM=
-```
-
-Then update [`nix.conf`](../command-ref/conf-file.md) on any machine that will access the cache.
-Add the cache URL to [`substituters`](../command-ref/conf-file.md#conf-substituters) and the public key to [`trusted-public-keys`](../command-ref/conf-file.md#conf-trusted-public-keys):
-
- substituters = https://cache.nixos.org/ s3://example-nix-cache
- trusted-public-keys = cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= example-nix-cache-1:1/cKDz3QCCOmwcztD2eV6Coggp6rqc9DGjWv7C0G+rM=
-
-Machines that build for the cache must sign derivations using the private key.
-On those machines, add the path to the key file to the [`secret-key-files`](../command-ref/conf-file.md#conf-secret-key-files) field in their [`nix.conf`](../command-ref/conf-file.md):
-
- secret-key-files = /etc/nix/key.private
-
-We will restart the Nix daemon in a later step.
-
-# Implementing the build hook
-
-Write the following script to `/etc/nix/upload-to-cache.sh`:
-
-```bash
-#!/bin/sh
-
-set -eu
-set -f # disable globbing
-export IFS=' '
-
-echo "Uploading paths" $OUT_PATHS
-exec nix copy --to "s3://example-nix-cache" $OUT_PATHS
-```
-
-> **Note**
->
-> The `$OUT_PATHS` variable is a space-separated list of Nix store
-> paths. In this case, we expect and want the shell to perform word
-> splitting to make each output path its own argument to `nix
-> store sign`. Nix guarantees the paths will not contain any spaces,
-> however a store path might contain glob characters. The `set -f`
-> disables globbing in the shell.
-
-Then make sure the hook program is executable by the `root` user:
-
-```console
-# chmod +x /etc/nix/upload-to-cache.sh
-```
-
-# Updating Lix Configuration
-
-Edit `/etc/nix/nix.conf` to run our hook, by adding the following
-configuration snippet at the end:
-
- post-build-hook = /etc/nix/upload-to-cache.sh
-
-Then, restart the `nix-daemon`.
-
-# Testing
-
-Build any derivation, for example:
-
-```console
-$ nix-build --expr '(import {}).writeText "example" (builtins.toString builtins.currentTime)'
-this derivation will be built:
- /nix/store/s4pnfbkalzy5qz57qs6yybna8wylkig6-example.drv
-building '/nix/store/s4pnfbkalzy5qz57qs6yybna8wylkig6-example.drv'...
-running post-build-hook '/home/grahamc/projects/github.com/NixOS/nix/post-hook.sh'...
-post-build-hook: Signing paths /nix/store/ibcyipq5gf91838ldx40mjsp0b8w9n18-example
-post-build-hook: Uploading paths /nix/store/ibcyipq5gf91838ldx40mjsp0b8w9n18-example
-/nix/store/ibcyipq5gf91838ldx40mjsp0b8w9n18-example
-```
-
-Then delete the path from the store, and try substituting it from the
-binary cache:
-
-```console
-$ rm ./result
-$ nix-store --delete /nix/store/ibcyipq5gf91838ldx40mjsp0b8w9n18-example
-```
-
-Now, copy the path back from the cache:
-
-```console
-$ nix-store --realise /nix/store/ibcyipq5gf91838ldx40mjsp0b8w9n18-example
-copying path '/nix/store/m8bmqwrch6l3h8s0k3d673xpmipcdpsa-example from 's3://example-nix-cache'...
-warning: you did not specify '--add-root'; the result might be removed by the garbage collector
-/nix/store/m8bmqwrch6l3h8s0k3d673xpmipcdpsa-example
-```
-
-# Conclusion
-
-We now have a Lix installation configured to automatically sign and
-upload every local build to a remote binary cache.
-
-Before deploying this to production, be sure to consider the
-[implementation caveats](#implementation-caveats).
diff --git a/doc/manual/src/architecture/architecture.md b/doc/manual/src/architecture/architecture.md
deleted file mode 100644
index 9fc232ea9..000000000
--- a/doc/manual/src/architecture/architecture.md
+++ /dev/null
@@ -1,114 +0,0 @@
-# Architecture
-
-This chapter describes how Nix works.
-It should help users understand why Lix behaves as it does, and it should help developers understand how to modify Lix and how to write similar tools.
-
-## Overview
-
-Nix consists of [hierarchical layers].
-
-[hierarchical layers]: https://en.wikipedia.org/wiki/Multitier_architecture#Layers
-
-The following [concept map] shows its main components (rectangles), the objects they operate on (rounded rectangles), and their interactions (connecting phrases):
-
-[concept map]: https://en.wikipedia.org/wiki/Concept_map
-
-```
-
- .----------------.
- | Nix expression |----------.
- '----------------' |
- | passed to
- | |
-+----------|-------------------|--------------------------------+
-| Nix impl.| V |
-| (Lix) | +-------------------------+ |
-| | | commmand line interface |------. |
-| | +-------------------------+ | |
-| | | | |
-| evaluated by calls manages |
-| | | | |
-| | V | |
-| | +--------------------+ | |
-| '-------->| language evaluator | | |
-| +--------------------+ | |
-| | | |
-| produces | |
-| | V |
-| +----------------------------|------------------------------+ |
-| | store | | |
-| | referenced by V builds | |
-| | .-------------. .------------. .--------------. | |
-| | | build input |----->| build plan |----->| build result | | |
-| | '-------------' '------------' '--------------' | |
-| +-------------------------------------------------|---------+ |
-+---------------------------------------------------|-----------+
- |
- represented as
- |
- V
- .---------------.
- | file |
- '---------------'
-```
-
-At the top is the [command line interface](../command-ref/command-ref.md) that drives the underlying layers.
-
-The [Nix language](../language/index.md) evaluator transforms Nix expressions into self-contained *build plans*, which are used to derive *build results* from referenced *build inputs*.
-
-The command line interface and Nix expressions are what users deal with most.
-
-> **Note**
-> The Nix language itself does not have a notion of *packages* or *configurations*.
-> As far as we are concerned here, the inputs and results of a build plan are just data.
-
-Underlying the command line interface and the Nix language evaluator is the [Nix store](../glossary.md#gloss-store), a mechanism to keep track of build plans, data, and references between them.
-It can also execute build plans to produce new data, which are made available to the operating system as files.
-
-A build plan itself is a series of *build tasks*, together with their build inputs.
-
-> **Important**
-> A build task in Nix is called [derivation](../glossary.md#gloss-derivation).
-
-Each build task has a special build input executed as *build instructions* in order to perform the build.
-The result of a build task can be input to another build task.
-
-The following [data flow diagram] shows a build plan for illustration.
-Build inputs used as instructions to a build task are marked accordingly:
-
-[data flow diagram]: https://en.wikipedia.org/wiki/Data-flow_diagram
-
-```
-+--------------------------------------------------------------------+
-| build plan |
-| |
-| .-------------. |
-| | build input |---------. |
-| '-------------' | |
-| instructions |
-| | |
-| v |
-| .-------------. .----------. |
-| | build input |-->( build task )-------. |
-| '-------------' '----------' | |
-| instructions |
-| | |
-| v |
-| .-------------. .----------. .--------------. |
-| | build input |---------. ( build task )--->| build result | |
-| '-------------' | '----------' '--------------' |
-| instructions ^ |
-| | | |
-| v | |
-| .-------------. .----------. | |
-| | build input |-->( build task )-------' |
-| '-------------' '----------' |
-| ^ |
-| | |
-| | |
-| .-------------. | |
-| | build input |---------' |
-| '-------------' |
-| |
-+--------------------------------------------------------------------+
-```
diff --git a/doc/manual/src/architecture/file-system-object.md b/doc/manual/src/architecture/file-system-object.md
deleted file mode 100644
index 8bc02de09..000000000
--- a/doc/manual/src/architecture/file-system-object.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# File System Object
-
-Nix implementations use a simplified model of the file system, which consists of file system objects.
-Every file system object is one of the following:
-
- - File
-
- - A possibly empty sequence of bytes for contents
- - A single boolean representing the [executable](https://en.m.wikipedia.org/wiki/File-system_permissions#Permissions) permission
-
- - Directory
-
- Mapping of names to child file system objects
-
- - [Symbolic link](https://en.m.wikipedia.org/wiki/Symbolic_link)
-
- An arbitrary string.
- Nix implementations do not assign any semantics to symbolic links.
-
-File system objects and their children form a tree.
-A bare file or symlink can be a root file system object.
-
-Nix does not encode any other file system notions such as [hard links](https://en.m.wikipedia.org/wiki/Hard_link), [permissions](https://en.m.wikipedia.org/wiki/File-system_permissions), timestamps, or other metadata.
-
-## Examples of file system objects
-
-A plain file:
-
-```
-50 B, executable: false
-```
-
-An executable file:
-
-```
-122 KB, executable: true
-```
-
-A symlink:
-
-```
--> /usr/bin/sh
-```
-
-A directory with contents:
-
-```
-├── bin
-│ └── hello: 35 KB, executable: true
-└── share
- ├── info
- │ └── hello.info: 36 KB, executable: false
- └── man
- └── man1
- └── hello.1.gz: 790 B, executable: false
-```
-
-A directory that contains a symlink and other directories:
-
-```
-├── bin -> share/go/bin
-├── nix-support/
-└── share/
-```
diff --git a/doc/manual/src/command-ref/command-ref.md b/doc/manual/src/command-ref/command-ref.md
deleted file mode 100644
index c79f8e0ba..000000000
--- a/doc/manual/src/command-ref/command-ref.md
+++ /dev/null
@@ -1,2 +0,0 @@
-This section lists commands and options that you can use when you work
-with Lix.
diff --git a/doc/manual/src/command-ref/conf-file.md b/doc/manual/src/command-ref/conf-file.md
deleted file mode 100644
index fda6ebde7..000000000
--- a/doc/manual/src/command-ref/conf-file.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# Name
-
-`nix.conf` - Lix configuration file
-
-# Description
-
-Lix supports a variety of configuration settings, which are read from configuration files or taken as command line flags.
-
-## Configuration file
-
-By default Lix reads settings from the following places, in that order:
-
-1. The system-wide configuration file `sysconfdir/nix/nix.conf` (i.e. `/etc/nix/nix.conf` on most systems), or `$NIX_CONF_DIR/nix.conf` if [`NIX_CONF_DIR`](./env-common.md#env-NIX_CONF_DIR) is set.
-
- Values loaded in this file are not forwarded to the Nix daemon.
- The client assumes that the daemon has already loaded them.
-
-1. If [`NIX_USER_CONF_FILES`](./env-common.md#env-NIX_USER_CONF_FILES) is set, then each path separated by `:` will be loaded in reverse order.
-
- Otherwise it will look for `nix/nix.conf` files in `XDG_CONFIG_DIRS` and `XDG_CONFIG_HOME`.
- If unset, `XDG_CONFIG_DIRS` defaults to `/etc/xdg`, and `XDG_CONFIG_HOME` defaults to `$HOME/.config` as per [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html).
-
-1. If [`NIX_CONFIG`](./env-common.md#env-NIX_CONFIG) is set, its contents are treated as the contents of a configuration file.
-
-### File format
-
-Configuration files consist of `name = value` pairs, one per line.
-Comments start with a `#` character.
-
-Example:
-
-```
-keep-outputs = true # Nice for developers
-keep-derivations = true # Idem
-```
-
-Other files can be included with a line like `include `, where `` is interpreted relative to the current configuration file.
-A missing file is an error unless `!include` is used instead.
-
-A configuration setting usually overrides any previous value.
-However, for settings that take a list of items, you can prefix the name of the setting by `extra-` to *append* to the previous value.
-
-For instance,
-
-```
-substituters = a b
-extra-substituters = c d
-```
-
-defines the `substituters` setting to be `a b c d`.
-
-Unknown option names are not an error, and are simply ignored with a warning.
-
-## Command line flags
-
-Configuration options can be set on the command line, overriding the values set in the [configuration file](#configuration-file):
-
-- Every configuration setting has corresponding command line flag (e.g. `--max-jobs 16`).
- Boolean settings do not need an argument, and can be explicitly disabled with the `no-` prefix (e.g. `--keep-failed` and `--no-keep-failed`).
-
- Unknown option names are invalid flags (unless there is already a flag with that name), and are rejected with an error.
-
-- The flag `--option ` is interpreted exactly like a ` = ` in a setting file.
-
- Unknown option names are ignored with a warning.
-
-The `extra-` prefix is supported for settings that take a list of items (e.g. `--extra-trusted users alice` or `--option extra-trusted-users alice`).
-
-# Available settings
-
-{{#include @generated@/command-ref/conf-file.md}}
diff --git a/doc/manual/src/command-ref/env-common.md b/doc/manual/src/command-ref/env-common.md
deleted file mode 100644
index ea8420c72..000000000
--- a/doc/manual/src/command-ref/env-common.md
+++ /dev/null
@@ -1,124 +0,0 @@
-# Common Environment Variables
-
-Most commands in Lix interpret the following environment variables:
-
- - [`IN_NIX_SHELL`](#env-IN_NIX_SHELL)\
- Indicator that tells if the current environment was set up by
- `nix-shell`. It can have the values `pure` or `impure`.
-
- - [`NIX_PATH`](#env-NIX_PATH)\
- A colon-separated list of directories used to look up the location of Nix
- expressions using [paths](@docroot@/language/values.md#type-path)
- enclosed in angle brackets (i.e., ``),
- e.g. `/home/eelco/Dev:/etc/nixos`. It can be extended using the
- [`-I` option](@docroot@/command-ref/opt-common.md#opt-I).
-
- If `NIX_PATH` is not set at all, Lix will fall back to the following list in [impure](@docroot@/command-ref/conf-file.md#conf-pure-eval) and [unrestricted](@docroot@/command-ref/conf-file.md#conf-restrict-eval) evaluation mode:
-
- 1. `$HOME/.nix-defexpr/channels`
- 2. `nixpkgs=/nix/var/nix/profiles/per-user/root/channels/nixpkgs`
- 3. `/nix/var/nix/profiles/per-user/root/channels`
-
- If `NIX_PATH` is set to an empty string, resolving search paths will always fail.
- For example, attempting to use `` will produce:
-
- error: file 'nixpkgs' was not found in the Nix search path
-
- - [`NIX_IGNORE_SYMLINK_STORE`](#env-NIX_IGNORE_SYMLINK_STORE)\
- Normally, the Nix store directory (typically `/nix/store`) is not
- allowed to contain any symlink components. This is to prevent
- “impure” builds. Builders sometimes “canonicalise” paths by
- resolving all symlink components. Thus, builds on different machines
- (with `/nix/store` resolving to different locations) could yield
- different results. This is generally not a problem, except when
- builds are deployed to machines where `/nix/store` resolves
- differently. If you are sure that you’re not going to do that, you
- can set `NIX_IGNORE_SYMLINK_STORE` to `1`.
-
- Note that if you’re symlinking the Nix store so that you can put it
- on another file system than the root file system, on Linux you’re
- better off using `bind` mount points, e.g.,
-
- ```console
- $ mkdir /nix
- $ mount -o bind /mnt/otherdisk/nix /nix
- ```
-
- Consult the mount 8 manual page for details.
-
- - [`NIX_STORE_DIR`](#env-NIX_STORE_DIR)\
- Overrides the location of the Nix store (default `prefix/store`).
-
- - [`NIX_DATA_DIR`](#env-NIX_DATA_DIR)\
- Overrides the location of the Lix static data directory (default
- `prefix/share`).
-
- - [`NIX_LOG_DIR`](#env-NIX_LOG_DIR)\
- Overrides the location of the Lix log directory (default
- `prefix/var/log/nix`).
-
- - [`NIX_STATE_DIR`](#env-NIX_STATE_DIR)\
- Overrides the location of the Lix state directory (default
- `prefix/var/nix`).
-
- - [`NIX_CONF_DIR`](#env-NIX_CONF_DIR)\
- Overrides the location of the system Lix configuration directory
- (default `prefix/etc/nix`).
-
- - [`NIX_CONFIG`](#env-NIX_CONFIG)\
- Applies settings from Lix configuration from the environment.
- The content is treated as if it was read from a Lix configuration file.
- Settings are separated by the newline character.
-
- - [`NIX_USER_CONF_FILES`](#env-NIX_USER_CONF_FILES)\
- Overrides the location of the Lix user configuration files to load from.
-
- The default are the locations according to the [XDG Base Directory Specification].
- See the [XDG Base Directories](#xdg-base-directories) sub-section for details.
-
- The variable is treated as a list separated by the `:` token.
-
- - [`TMPDIR`](#env-TMPDIR)\
- Use the specified directory to store temporary files. In particular,
- this includes temporary build directories; these can take up
- substantial amounts of disk space. The default is `/tmp`.
-
- - [`NIX_REMOTE`](#env-NIX_REMOTE)\
- This variable should be set to `daemon` if you want to use the Lix
- daemon to execute Nix operations. This is necessary in [multi-user
- Nix installations](@docroot@/installation/multi-user.md). If the Lix
- daemon's Unix socket is at some non-standard path, this variable
- should be set to `unix://path/to/socket`. Otherwise, it should be
- left unset.
-
- - [`NIX_SHOW_STATS`](#env-NIX_SHOW_STATS)\
- If set to `1`, Lix will print some evaluation statistics, such as
- the number of values allocated.
-
- - [`NIX_COUNT_CALLS`](#env-NIX_COUNT_CALLS)\
- If set to `1`, Lix will print how often functions were called during
- Nix expression evaluation. This is useful for profiling your Nix
- expressions.
-
- - [`GC_INITIAL_HEAP_SIZE`](#env-GC_INITIAL_HEAP_SIZE)\
- If Nix has been configured to use the Boehm garbage collector, this
- variable sets the initial size of the heap in bytes. It defaults to
- 384 MiB. Setting it to a low value reduces memory consumption, but
- will increase runtime due to the overhead of garbage collection.
-
-## XDG Base Directories
-
-Lix follows the [XDG Base Directory Specification].
-
-For backwards compatibility, commands in Lix will follow the standard only when [`use-xdg-base-directories`] is enabled.
-[New Nix commands](@docroot@/command-ref/new-cli/nix.md) (experimental) conform to the standard by default.
-
-The following environment variables are used to determine locations of various state and configuration files:
-
-- `XDG_CONFIG_HOME` (default `~/.config`)
-- `XDG_STATE_HOME` (default `~/.local/state`)
-- `XDG_CACHE_HOME` (default `~/.cache`)
-
-
-[XDG Base Directory Specification]: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
-[`use-xdg-base-directories`]: @docroot@/command-ref/conf-file.md#conf-use-xdg-base-directories
diff --git a/doc/manual/src/command-ref/experimental-commands.md b/doc/manual/src/command-ref/experimental-commands.md
deleted file mode 100644
index 286ddc6d6..000000000
--- a/doc/manual/src/command-ref/experimental-commands.md
+++ /dev/null
@@ -1,8 +0,0 @@
-# Experimental Commands
-
-This section lists [experimental commands](@docroot@/contributing/experimental-features.md#xp-feature-nix-command).
-
-> **Warning**
->
-> These commands may be removed in the future, or their syntax may
-> change in incompatible ways.
diff --git a/doc/manual/src/command-ref/files.md b/doc/manual/src/command-ref/files.md
deleted file mode 100644
index e2d08923b..000000000
--- a/doc/manual/src/command-ref/files.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Files
-
-This section lists configuration files that you can use when you work
-with Lix.
diff --git a/doc/manual/src/command-ref/files/channels.md b/doc/manual/src/command-ref/files/channels.md
deleted file mode 100644
index 7b1f27128..000000000
--- a/doc/manual/src/command-ref/files/channels.md
+++ /dev/null
@@ -1,26 +0,0 @@
-## Channels
-
-A directory containing symlinks to Nix channels, managed by [`nix-channel`]:
-
-- `$XDG_STATE_HOME/nix/profiles/channels` for regular users
-- `$NIX_STATE_DIR/profiles/per-user/root/channels` for `root`
-
-[`nix-channel`] uses a [profile](@docroot@/command-ref/files/profiles.md) to store channels.
-This profile contains symlinks to the contents of those channels.
-
-## Subscribed channels
-
-The list of subscribed channels is stored in
-
-- `~/.nix-channels`
-- `$XDG_STATE_HOME/nix/channels` if [`use-xdg-base-directories`] is set to `true`
-
-in the following format:
-
-```
-
-...
-```
-
-[`nix-channel`]: @docroot@/command-ref/nix-channel.md
-[`use-xdg-base-directories`]: @docroot@/command-ref/conf-file.md#conf-use-xdg-base-directories
diff --git a/doc/manual/src/command-ref/files/default-nix-expression.md b/doc/manual/src/command-ref/files/default-nix-expression.md
deleted file mode 100644
index 620f7035c..000000000
--- a/doc/manual/src/command-ref/files/default-nix-expression.md
+++ /dev/null
@@ -1,52 +0,0 @@
-## Default Nix expression
-
-The source for the default [Nix expressions](@docroot@/language/index.md) used by [`nix-env`]:
-
-- `~/.nix-defexpr`
-- `$XDG_STATE_HOME/nix/defexpr` if [`use-xdg-base-directories`] is set to `true`.
-
-It is loaded as follows:
-
-- If the default expression is a file, it is loaded as a Nix expression.
-- If the default expression is a directory containing a `default.nix` file, that `default.nix` file is loaded as a Nix expression.
-- If the default expression is a directory without a `default.nix` file, then its contents (both files and subdirectories) are loaded as Nix expressions.
- The expressions are combined into a single attribute set, each expression under an attribute with the same name as the original file or subdirectory.
- Subdirectories without a `default.nix` file are traversed recursively in search of more Nix expressions, but the names of these intermediate directories are not added to the attribute paths of the default Nix expression.
-
-Then, the resulting expression is interpreted like this:
-
-- If the expression is an attribute set, it is used as the default Nix expression.
-- If the expression is a function, an empty set is passed as argument and the return value is used as the default Nix expression.
-
-
-For example, if the default expression contains two files, `foo.nix` and `bar.nix`, then the default Nix expression will be equivalent to
-
-```nix
-{
- foo = import ~/.nix-defexpr/foo.nix;
- bar = import ~/.nix-defexpr/bar.nix;
-}
-```
-
-The file [`manifest.nix`](@docroot@/command-ref/files/manifest.nix.md) is always ignored.
-
-The command [`nix-channel`] places a symlink to the user's current [channels profile](@docroot@/command-ref/files/channels.md) in this directory.
-This makes all subscribed channels available as attributes in the default expression.
-
-## User channel link
-
-A symlink that ensures that [`nix-env`] can find your channels:
-
-- `~/.nix-defexpr/channels`
-- `$XDG_STATE_HOME/defexpr/channels` if [`use-xdg-base-directories`] is set to `true`.
-
-This symlink points to:
-
-- `$XDG_STATE_HOME/profiles/channels` for regular users
-- `$NIX_STATE_DIR/profiles/per-user/root/channels` for `root`
-
-In a multi-user installation, you may also have `~/.nix-defexpr/channels_root`, which links to the channels of the root user.[`nix-env`]: ../nix-env.md
-
-[`nix-env`]: @docroot@/command-ref/nix-env.md
-[`nix-channel`]: @docroot@/command-ref/nix-channel.md
-[`use-xdg-base-directories`]: @docroot@/command-ref/conf-file.md#conf-use-xdg-base-directories
diff --git a/doc/manual/src/command-ref/files/manifest.json.md b/doc/manual/src/command-ref/files/manifest.json.md
deleted file mode 100644
index bcfe7373d..000000000
--- a/doc/manual/src/command-ref/files/manifest.json.md
+++ /dev/null
@@ -1,45 +0,0 @@
-## `manifest.json`
-
-The manifest file records the provenance of the packages that are installed in a [profile](./profiles.md) managed by [`nix profile`](@docroot@/command-ref/new-cli/nix3-profile.md) (experimental).
-
-Here is an example of what the file might look like after installing `zoom-us` from Nixpkgs:
-
-```json
-{
- "version": 1,
- "elements": [
- {
- "active": true,
- "attrPath": "legacyPackages.x86_64-linux.zoom-us",
- "originalUrl": "flake:nixpkgs",
- "storePaths": [
- "/nix/store/wbhg2ga8f3h87s9h5k0slxk0m81m4cxl-zoom-us-5.3.469451.0927"
- ],
- "uri": "github:NixOS/nixpkgs/13d0c311e3ae923a00f734b43fd1d35b47d8943a"
- },
- …
- ]
-}
-```
-
-Each object in the array `elements` denotes an installed package and
-has the following fields:
-
-* `originalUrl`: The [flake reference](@docroot@/command-ref/new-cli/nix3-flake.md) specified by
- the user at the time of installation (e.g. `nixpkgs`). This is also
- the flake reference that will be used by `nix profile upgrade`.
-
-* `uri`: The locked flake reference to which `originalUrl` resolved.
-
-* `attrPath`: The flake output attribute that provided this
- package. Note that this is not necessarily the attribute that the
- user specified, but the one resulting from applying the default
- attribute paths and prefixes; for instance, `hello` might resolve to
- `packages.x86_64-linux.hello` and the empty string to
- `packages.x86_64-linux.default`.
-
-* `storePath`: The paths in the Nix store containing the package.
-
-* `active`: Whether the profile contains symlinks to the files of this
- package. If set to false, the package is kept in the Nix store, but
- is not "visible" in the profile's symlink tree.
diff --git a/doc/manual/src/command-ref/files/manifest.nix.md b/doc/manual/src/command-ref/files/manifest.nix.md
deleted file mode 100644
index d7d1b605b..000000000
--- a/doc/manual/src/command-ref/files/manifest.nix.md
+++ /dev/null
@@ -1,128 +0,0 @@
-## `manifest.nix`
-
-The manifest file records the provenance of the packages that are installed in a [profile](./profiles.md) managed by [`nix-env`](@docroot@/command-ref/nix-env.md).
-
-Here is an example of how this file might look like after installing `hello` from Nixpkgs:
-
-```nix
-[{
- meta = {
- available = true;
- broken = false;
- changelog =
- "https://git.savannah.gnu.org/cgit/hello.git/plain/NEWS?h=v2.12.1";
- description = "A program that produces a familiar, friendly greeting";
- homepage = "https://www.gnu.org/software/hello/manual/";
- insecure = false;
- license = {
- deprecated = false;
- free = true;
- fullName = "GNU General Public License v3.0 or later";
- redistributable = true;
- shortName = "gpl3Plus";
- spdxId = "GPL-3.0-or-later";
- url = "https://spdx.org/licenses/GPL-3.0-or-later.html";
- };
- longDescription = ''
- GNU Hello is a program that prints "Hello, world!" when you run it.
- It is fully customizable.
- '';
- maintainers = [{
- email = "edolstra+nixpkgs@gmail.com";
- github = "edolstra";
- githubId = 1148549;
- name = "Eelco Dolstra";
- }];
- name = "hello-2.12.1";
- outputsToInstall = [ "out" ];
- platforms = [
- "i686-cygwin"
- "x86_64-cygwin"
- "x86_64-darwin"
- "i686-darwin"
- "aarch64-darwin"
- "armv7a-darwin"
- "i686-freebsd13"
- "x86_64-freebsd13"
- "aarch64-genode"
- "i686-genode"
- "x86_64-genode"
- "x86_64-solaris"
- "js-ghcjs"
- "aarch64-linux"
- "armv5tel-linux"
- "armv6l-linux"
- "armv7a-linux"
- "armv7l-linux"
- "i686-linux"
- "m68k-linux"
- "microblaze-linux"
- "microblazeel-linux"
- "mipsel-linux"
- "mips64el-linux"
- "powerpc64-linux"
- "powerpc64le-linux"
- "riscv32-linux"
- "riscv64-linux"
- "s390-linux"
- "s390x-linux"
- "x86_64-linux"
- "mmix-mmixware"
- "aarch64-netbsd"
- "armv6l-netbsd"
- "armv7a-netbsd"
- "armv7l-netbsd"
- "i686-netbsd"
- "m68k-netbsd"
- "mipsel-netbsd"
- "powerpc-netbsd"
- "riscv32-netbsd"
- "riscv64-netbsd"
- "x86_64-netbsd"
- "aarch64_be-none"
- "aarch64-none"
- "arm-none"
- "armv6l-none"
- "avr-none"
- "i686-none"
- "microblaze-none"
- "microblazeel-none"
- "msp430-none"
- "or1k-none"
- "m68k-none"
- "powerpc-none"
- "powerpcle-none"
- "riscv32-none"
- "riscv64-none"
- "rx-none"
- "s390-none"
- "s390x-none"
- "vc4-none"
- "x86_64-none"
- "i686-openbsd"
- "x86_64-openbsd"
- "x86_64-redox"
- "wasm64-wasi"
- "wasm32-wasi"
- "x86_64-windows"
- "i686-windows"
- ];
- position =
- "/nix/store/7niq32w715567hbph0q13m5lqna64c1s-nixos-unstable.tar.gz/nixos-unstable.tar.gz/pkgs/applications/misc/hello/default.nix:34";
- unfree = false;
- unsupported = false;
- };
- name = "hello-2.12.1";
- out = {
- outPath = "/nix/store/260q5867crm1xjs4khgqpl6vr9kywql1-hello-2.12.1";
- };
- outPath = "/nix/store/260q5867crm1xjs4khgqpl6vr9kywql1-hello-2.12.1";
- outputs = [ "out" ];
- system = "x86_64-linux";
- type = "derivation";
-}]
-```
-
-Each element in this list corresponds to an installed package.
-It incorporates some attributes of the original derivation, including `meta`, `name`, `out`, `outPath`, `outputs`, `system`.
-This information is used by Nix for querying and updating the package.
diff --git a/doc/manual/src/command-ref/files/profiles.md b/doc/manual/src/command-ref/files/profiles.md
deleted file mode 100644
index a6b679e34..000000000
--- a/doc/manual/src/command-ref/files/profiles.md
+++ /dev/null
@@ -1,74 +0,0 @@
-## Profiles
-
-A directory that contains links to profiles managed by [`nix-env`] and [`nix profile`]:
-
-- `$XDG_STATE_HOME/nix/profiles` for regular users
-- `$NIX_STATE_DIR/profiles/per-user/root` if the user is `root`
-
-A profile is a directory of symlinks to files in the Nix store.
-
-### Filesystem layout
-
-Profiles are versioned as follows. When using a profile named *path*, *path* is a symlink to *path*`-`*N*`-link`, where *N* is the version of the profile.
-In turn, *path*`-`*N*`-link` is a symlink to a path in the Nix store.
-For example:
-
-```console
-$ ls -l ~alice/.local/state/nix/profiles/profile*
-lrwxrwxrwx 1 alice users 14 Nov 25 14:35 /home/alice/.local/state/nix/profiles/profile -> profile-7-link
-lrwxrwxrwx 1 alice users 51 Oct 28 16:18 /home/alice/.local/state/nix/profiles/profile-5-link -> /nix/store/q69xad13ghpf7ir87h0b2gd28lafjj1j-profile
-lrwxrwxrwx 1 alice users 51 Oct 29 13:20 /home/alice/.local/state/nix/profiles/profile-6-link -> /nix/store/6bvhpysd7vwz7k3b0pndn7ifi5xr32dg-profile
-lrwxrwxrwx 1 alice users 51 Nov 25 14:35 /home/alice/.local/state/nix/profiles/profile-7-link -> /nix/store/mp0x6xnsg0b8qhswy6riqvimai4gm677-profile
-```
-
-Each of these symlinks is a root for the Lix garbage collector.
-
-The contents of the store path corresponding to each version of the
-profile is a tree of symlinks to the files of the installed packages,
-e.g.
-
-```console
-$ ll -R ~eelco/.local/state/nix/profiles/profile-7-link/
-/home/eelco/.local/state/nix/profiles/profile-7-link/:
-total 20
-dr-xr-xr-x 2 root root 4096 Jan 1 1970 bin
--r--r--r-- 2 root root 1402 Jan 1 1970 manifest.nix
-dr-xr-xr-x 4 root root 4096 Jan 1 1970 share
-
-/home/eelco/.local/state/nix/profiles/profile-7-link/bin:
-total 20
-lrwxrwxrwx 5 root root 79 Jan 1 1970 chromium -> /nix/store/ijm5k0zqisvkdwjkc77mb9qzb35xfi4m-chromium-86.0.4240.111/bin/chromium
-lrwxrwxrwx 7 root root 87 Jan 1 1970 spotify -> /nix/store/w9182874m1bl56smps3m5zjj36jhp3rn-spotify-1.1.26.501.gbe11e53b-15/bin/spotify
-lrwxrwxrwx 3 root root 79 Jan 1 1970 zoom-us -> /nix/store/wbhg2ga8f3h87s9h5k0slxk0m81m4cxl-zoom-us-5.3.469451.0927/bin/zoom-us
-
-/home/eelco/.local/state/nix/profiles/profile-7-link/share/applications:
-total 12
-lrwxrwxrwx 4 root root 120 Jan 1 1970 chromium-browser.desktop -> /nix/store/4cf803y4vzfm3gyk3vzhzb2327v0kl8a-chromium-unwrapped-86.0.4240.111/share/applications/chromium-browser.desktop
-lrwxrwxrwx 7 root root 110 Jan 1 1970 spotify.desktop -> /nix/store/w9182874m1bl56smps3m5zjj36jhp3rn-spotify-1.1.26.501.gbe11e53b-15/share/applications/spotify.desktop
-lrwxrwxrwx 3 root root 107 Jan 1 1970 us.zoom.Zoom.desktop -> /nix/store/wbhg2ga8f3h87s9h5k0slxk0m81m4cxl-zoom-us-5.3.469451.0927/share/applications/us.zoom.Zoom.desktop
-
-…
-```
-
-Each profile version contains a manifest file:
-- [`manifest.nix`](@docroot@/command-ref/files/manifest.nix.md) used by [`nix-env`](@docroot@/command-ref/nix-env.md).
-- [`manifest.json`](@docroot@/command-ref/files/manifest.json.md) used by [`nix profile`](@docroot@/command-ref/new-cli/nix3-profile.md) (experimental).
-
-## User profile link
-
-A symbolic link to the user's current profile:
-
-- `~/.nix-profile`
-- `$XDG_STATE_HOME/nix/profile` if [`use-xdg-base-directories`] is set to `true`.
-
-By default, this symlink points to:
-
-- `$XDG_STATE_HOME/nix/profiles/profile` for regular users
-- `$NIX_STATE_DIR/profiles/per-user/root/profile` for `root`
-
-The `PATH` environment variable should include `/bin` subdirectory of the profile link (e.g. `~/.nix-profile/bin`) for the user environment to be visible to the user.
-The [installer](@docroot@/installation/installing-binary.md) sets this up by default, unless you enable [`use-xdg-base-directories`].
-
-[`nix-env`]: @docroot@/command-ref/nix-env.md
-[`nix profile`]: @docroot@/command-ref/new-cli/nix3-profile.md
-[`use-xdg-base-directories`]: @docroot@/command-ref/conf-file.md#conf-use-xdg-base-directories
diff --git a/doc/manual/src/command-ref/main-commands.md b/doc/manual/src/command-ref/main-commands.md
deleted file mode 100644
index 0c1ca4fa1..000000000
--- a/doc/manual/src/command-ref/main-commands.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Main Commands
-
-This section lists commands and options that you can use when you work
-with Lix.
diff --git a/doc/manual/src/command-ref/meson.build b/doc/manual/src/command-ref/meson.build
deleted file mode 100644
index 03d5f0a9c..000000000
--- a/doc/manual/src/command-ref/meson.build
+++ /dev/null
@@ -1,66 +0,0 @@
-xp_features_json = custom_target(
- command : [nix, '__dump-xp-features'],
- capture : true,
- output : 'xp-features.json',
-)
-
-experimental_features_shortlist_md = custom_target(
- command : nix_eval_for_docs + [
- '--expr',
- 'import @INPUT0@ (builtins.fromJSON (builtins.readFile @INPUT1@))',
- ],
- input : [
- '../../generate-xp-features-shortlist.nix',
- xp_features_json,
- ],
- capture : true,
- output : 'experimental-features-shortlist.md',
- env : nix_env_for_docs,
-)
-
-# Intermediate step for manpage generation.
-# This splorks the output of generate-manpage.nix as JSON,
-# which gets written as a directory tree below.
-nix3_cli_files_json = custom_target(
- command : nix_eval_for_docs_common + [
- '--json',
- '--expr',
- 'import @INPUT0@ true (builtins.readFile @INPUT1@)',
- ],
- input : [
- '../../generate-manpage.nix',
- nix3_cli_json,
- ],
- capture : true,
- output : 'new-cli.json',
- env : nix_env_for_docs,
-)
-nix3_cli_files = custom_target(
- command : [
- python,
- '@INPUT0@',
- '-i', '@INPUT1@',
- '-o', '@OUTPUT@',
- ],
- input : [
- '../../json-to-tree.py',
- nix3_cli_files_json,
- ],
- output : 'new-cli',
-)
-
-conf_file_md = custom_target(
- command : [
- nix_eval_for_docs,
- '--expr',
- '(import @INPUT0@).showSettings { inlineHTML = true; } (builtins.fromJSON (builtins.readFile @INPUT1@))',
- ],
- capture : true,
- input : [
- '../../utils.nix',
- conf_file_json,
- experimental_features_shortlist_md,
- ],
- output : 'conf-file.md',
- env : nix_env_for_docs,
-)
diff --git a/doc/manual/src/command-ref/new-cli/nix.md b/doc/manual/src/command-ref/new-cli/nix.md
deleted file mode 100644
index 586800c40..000000000
--- a/doc/manual/src/command-ref/new-cli/nix.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-build.md b/doc/manual/src/command-ref/new-cli/nix3-build.md
deleted file mode 100644
index 08d067501..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-build.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-build.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-bundle.md b/doc/manual/src/command-ref/new-cli/nix3-bundle.md
deleted file mode 100644
index ebfcca2f4..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-bundle.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-bundle.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-config-show.md b/doc/manual/src/command-ref/new-cli/nix3-config-show.md
deleted file mode 100644
index a39cd13e9..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-config-show.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-config-show.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-config.md b/doc/manual/src/command-ref/new-cli/nix3-config.md
deleted file mode 100644
index ba824c7bc..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-config.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-config.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-copy.md b/doc/manual/src/command-ref/new-cli/nix3-copy.md
deleted file mode 100644
index 29fefff59..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-copy.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-copy.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-daemon.md b/doc/manual/src/command-ref/new-cli/nix3-daemon.md
deleted file mode 100644
index a0c0fd02e..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-daemon.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-daemon.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-derivation-add.md b/doc/manual/src/command-ref/new-cli/nix3-derivation-add.md
deleted file mode 100644
index 4ec3ff16c..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-derivation-add.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-derivation-add.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-derivation-show.md b/doc/manual/src/command-ref/new-cli/nix3-derivation-show.md
deleted file mode 100644
index 8cf5dbe0a..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-derivation-show.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-derivation-show.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-derivation.md b/doc/manual/src/command-ref/new-cli/nix3-derivation.md
deleted file mode 100644
index 3a80ebbb5..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-derivation.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-derivation.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-develop.md b/doc/manual/src/command-ref/new-cli/nix3-develop.md
deleted file mode 100644
index 55cb03987..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-develop.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-develop.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-doctor.md b/doc/manual/src/command-ref/new-cli/nix3-doctor.md
deleted file mode 100644
index f6e0b401a..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-doctor.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-doctor.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-edit.md b/doc/manual/src/command-ref/new-cli/nix3-edit.md
deleted file mode 100644
index a841f2456..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-edit.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-edit.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-eval.md b/doc/manual/src/command-ref/new-cli/nix3-eval.md
deleted file mode 100644
index 16ac2517e..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-eval.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-eval.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-archive.md b/doc/manual/src/command-ref/new-cli/nix3-flake-archive.md
deleted file mode 100644
index 5e4cdb1b2..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-archive.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-archive.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-check.md b/doc/manual/src/command-ref/new-cli/nix3-flake-check.md
deleted file mode 100644
index 677c964aa..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-check.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-check.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-clone.md b/doc/manual/src/command-ref/new-cli/nix3-flake-clone.md
deleted file mode 100644
index be53e26ce..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-clone.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-clone.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-info.md b/doc/manual/src/command-ref/new-cli/nix3-flake-info.md
deleted file mode 100644
index 118e09b23..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-info.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-info.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-init.md b/doc/manual/src/command-ref/new-cli/nix3-flake-init.md
deleted file mode 100644
index 48cc0f3ef..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-init.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-init.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-lock.md b/doc/manual/src/command-ref/new-cli/nix3-flake-lock.md
deleted file mode 100644
index 9d6845653..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-lock.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-lock.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-metadata.md b/doc/manual/src/command-ref/new-cli/nix3-flake-metadata.md
deleted file mode 100644
index 8930bb5e1..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-metadata.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-metadata.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-new.md b/doc/manual/src/command-ref/new-cli/nix3-flake-new.md
deleted file mode 100644
index 5b7d9ebdf..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-new.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-new.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-prefetch.md b/doc/manual/src/command-ref/new-cli/nix3-flake-prefetch.md
deleted file mode 100644
index 69b41faae..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-prefetch.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-prefetch.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-show.md b/doc/manual/src/command-ref/new-cli/nix3-flake-show.md
deleted file mode 100644
index 59755e960..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-show.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-show.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake-update.md b/doc/manual/src/command-ref/new-cli/nix3-flake-update.md
deleted file mode 100644
index f897e504f..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake-update.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake-update.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-flake.md b/doc/manual/src/command-ref/new-cli/nix3-flake.md
deleted file mode 100644
index 97d38f1bb..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-flake.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-flake.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-fmt.md b/doc/manual/src/command-ref/new-cli/nix3-fmt.md
deleted file mode 100644
index ed31de3f7..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-fmt.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-fmt.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-hash-file.md b/doc/manual/src/command-ref/new-cli/nix3-hash-file.md
deleted file mode 100644
index b81754594..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-hash-file.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-hash-file.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-hash-path.md b/doc/manual/src/command-ref/new-cli/nix3-hash-path.md
deleted file mode 100644
index 9928928f2..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-hash-path.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-hash-path.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-hash-to-base16.md b/doc/manual/src/command-ref/new-cli/nix3-hash-to-base16.md
deleted file mode 100644
index fb04ccee8..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-hash-to-base16.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-hash-to-base16.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-hash-to-base32.md b/doc/manual/src/command-ref/new-cli/nix3-hash-to-base32.md
deleted file mode 100644
index 2e40c1077..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-hash-to-base32.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-hash-to-base32.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-hash-to-base64.md b/doc/manual/src/command-ref/new-cli/nix3-hash-to-base64.md
deleted file mode 100644
index 8ec8ecbc6..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-hash-to-base64.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-hash-to-base64.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-hash-to-sri.md b/doc/manual/src/command-ref/new-cli/nix3-hash-to-sri.md
deleted file mode 100644
index 00298dff0..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-hash-to-sri.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-hash-to-sri.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-hash.md b/doc/manual/src/command-ref/new-cli/nix3-hash.md
deleted file mode 100644
index 68ab9862e..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-hash.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-hash.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-help-stores.md b/doc/manual/src/command-ref/new-cli/nix3-help-stores.md
deleted file mode 100644
index f397cc046..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-help-stores.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-help-stores.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-help.md b/doc/manual/src/command-ref/new-cli/nix3-help.md
deleted file mode 100644
index 306f1ea7a..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-help.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-help.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-key-convert-secret-to-public.md b/doc/manual/src/command-ref/new-cli/nix3-key-convert-secret-to-public.md
deleted file mode 100644
index 9f6e1be3a..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-key-convert-secret-to-public.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-key-convert-secret-to-public.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-key-generate-secret.md b/doc/manual/src/command-ref/new-cli/nix3-key-generate-secret.md
deleted file mode 100644
index 28225d3c8..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-key-generate-secret.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-key-generate-secret.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-key.md b/doc/manual/src/command-ref/new-cli/nix3-key.md
deleted file mode 100644
index 7df72030b..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-key.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-key.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-log.md b/doc/manual/src/command-ref/new-cli/nix3-log.md
deleted file mode 100644
index 8e590bfde..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-log.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-log.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-nar-cat.md b/doc/manual/src/command-ref/new-cli/nix3-nar-cat.md
deleted file mode 100644
index 21e137cc5..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-nar-cat.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-nar-cat.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-nar-dump-path.md b/doc/manual/src/command-ref/new-cli/nix3-nar-dump-path.md
deleted file mode 100644
index 39d4a0f8d..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-nar-dump-path.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-nar-dump-path.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-nar-ls.md b/doc/manual/src/command-ref/new-cli/nix3-nar-ls.md
deleted file mode 100644
index 60c75831a..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-nar-ls.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-nar-ls.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-nar.md b/doc/manual/src/command-ref/new-cli/nix3-nar.md
deleted file mode 100644
index 91217904d..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-nar.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-nar.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-path-info.md b/doc/manual/src/command-ref/new-cli/nix3-path-info.md
deleted file mode 100644
index 8db34e0f1..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-path-info.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-path-info.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-print-dev-env.md b/doc/manual/src/command-ref/new-cli/nix3-print-dev-env.md
deleted file mode 100644
index 7754780eb..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-print-dev-env.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-print-dev-env.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-profile-diff-closures.md b/doc/manual/src/command-ref/new-cli/nix3-profile-diff-closures.md
deleted file mode 100644
index eba30aa16..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-profile-diff-closures.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-profile-diff-closures.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-profile-history.md b/doc/manual/src/command-ref/new-cli/nix3-profile-history.md
deleted file mode 100644
index 85e8afc44..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-profile-history.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-profile-history.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-profile-install.md b/doc/manual/src/command-ref/new-cli/nix3-profile-install.md
deleted file mode 100644
index bb530cd9a..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-profile-install.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-profile-install.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-profile-list.md b/doc/manual/src/command-ref/new-cli/nix3-profile-list.md
deleted file mode 100644
index 7f6e7a3fa..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-profile-list.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-profile-list.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-profile-remove.md b/doc/manual/src/command-ref/new-cli/nix3-profile-remove.md
deleted file mode 100644
index 3651cb086..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-profile-remove.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-profile-remove.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-profile-rollback.md b/doc/manual/src/command-ref/new-cli/nix3-profile-rollback.md
deleted file mode 100644
index 9c73cf2f0..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-profile-rollback.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-profile-rollback.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-profile-upgrade.md b/doc/manual/src/command-ref/new-cli/nix3-profile-upgrade.md
deleted file mode 100644
index 1b498cfd0..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-profile-upgrade.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-profile-upgrade.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-profile-wipe-history.md b/doc/manual/src/command-ref/new-cli/nix3-profile-wipe-history.md
deleted file mode 100644
index 662169dbe..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-profile-wipe-history.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-profile-wipe-history.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-profile.md b/doc/manual/src/command-ref/new-cli/nix3-profile.md
deleted file mode 100644
index c98b611a3..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-profile.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-profile.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-realisation-info.md b/doc/manual/src/command-ref/new-cli/nix3-realisation-info.md
deleted file mode 100644
index 20d172987..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-realisation-info.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-realisation-info.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-realisation.md b/doc/manual/src/command-ref/new-cli/nix3-realisation.md
deleted file mode 100644
index 7c176f1c6..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-realisation.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-realisation.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-registry-add.md b/doc/manual/src/command-ref/new-cli/nix3-registry-add.md
deleted file mode 100644
index 9bb491fb3..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-registry-add.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-registry-add.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-registry-list.md b/doc/manual/src/command-ref/new-cli/nix3-registry-list.md
deleted file mode 100644
index 42c595eaf..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-registry-list.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-registry-list.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-registry-pin.md b/doc/manual/src/command-ref/new-cli/nix3-registry-pin.md
deleted file mode 100644
index 256f95cab..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-registry-pin.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-registry-pin.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-registry-remove.md b/doc/manual/src/command-ref/new-cli/nix3-registry-remove.md
deleted file mode 100644
index 4e2dda4f7..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-registry-remove.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-registry-remove.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-registry.md b/doc/manual/src/command-ref/new-cli/nix3-registry.md
deleted file mode 100644
index 5551d19b3..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-registry.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-registry.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-repl.md b/doc/manual/src/command-ref/new-cli/nix3-repl.md
deleted file mode 100644
index da82694fd..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-repl.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-repl.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-run.md b/doc/manual/src/command-ref/new-cli/nix3-run.md
deleted file mode 100644
index 1114efd9c..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-run.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-run.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-search.md b/doc/manual/src/command-ref/new-cli/nix3-search.md
deleted file mode 100644
index b72a5add5..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-search.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-search.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-shell.md b/doc/manual/src/command-ref/new-cli/nix3-shell.md
deleted file mode 100644
index 82f0af1e2..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-shell.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-shell.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-add-file.md b/doc/manual/src/command-ref/new-cli/nix3-store-add-file.md
deleted file mode 100644
index fa30cf660..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-add-file.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-add-file.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-add-path.md b/doc/manual/src/command-ref/new-cli/nix3-store-add-path.md
deleted file mode 100644
index 88ccd4b51..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-add-path.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-add-path.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-cat.md b/doc/manual/src/command-ref/new-cli/nix3-store-cat.md
deleted file mode 100644
index de617fc4e..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-cat.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-cat.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-copy-log.md b/doc/manual/src/command-ref/new-cli/nix3-store-copy-log.md
deleted file mode 100644
index 44998311f..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-copy-log.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-copy-log.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-copy-sigs.md b/doc/manual/src/command-ref/new-cli/nix3-store-copy-sigs.md
deleted file mode 100644
index cc03ab44e..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-copy-sigs.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-copy-sigs.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-delete.md b/doc/manual/src/command-ref/new-cli/nix3-store-delete.md
deleted file mode 100644
index 42a05162d..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-delete.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-delete.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-diff-closures.md b/doc/manual/src/command-ref/new-cli/nix3-store-diff-closures.md
deleted file mode 100644
index fe6bcd235..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-diff-closures.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-diff-closures.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-dump-path.md b/doc/manual/src/command-ref/new-cli/nix3-store-dump-path.md
deleted file mode 100644
index c4f34f450..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-dump-path.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-dump-path.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-gc.md b/doc/manual/src/command-ref/new-cli/nix3-store-gc.md
deleted file mode 100644
index da79527ab..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-gc.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-gc.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-ls.md b/doc/manual/src/command-ref/new-cli/nix3-store-ls.md
deleted file mode 100644
index fb64bcb21..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-ls.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-ls.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-make-content-addressed.md b/doc/manual/src/command-ref/new-cli/nix3-store-make-content-addressed.md
deleted file mode 100644
index 0a4b6c93a..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-make-content-addressed.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-make-content-addressed.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-optimise.md b/doc/manual/src/command-ref/new-cli/nix3-store-optimise.md
deleted file mode 100644
index cc84844d7..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-optimise.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-optimise.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-path-from-hash-part.md b/doc/manual/src/command-ref/new-cli/nix3-store-path-from-hash-part.md
deleted file mode 100644
index c9f4d4f1c..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-path-from-hash-part.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-path-from-hash-part.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-ping.md b/doc/manual/src/command-ref/new-cli/nix3-store-ping.md
deleted file mode 100644
index e199e904e..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-ping.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-ping.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-prefetch-file.md b/doc/manual/src/command-ref/new-cli/nix3-store-prefetch-file.md
deleted file mode 100644
index c72742413..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-prefetch-file.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-prefetch-file.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-repair.md b/doc/manual/src/command-ref/new-cli/nix3-store-repair.md
deleted file mode 100644
index 7ad9058d8..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-repair.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-repair.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-sign.md b/doc/manual/src/command-ref/new-cli/nix3-store-sign.md
deleted file mode 100644
index ec28f973b..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-sign.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-sign.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store-verify.md b/doc/manual/src/command-ref/new-cli/nix3-store-verify.md
deleted file mode 100644
index 1d115da04..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store-verify.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store-verify.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-store.md b/doc/manual/src/command-ref/new-cli/nix3-store.md
deleted file mode 100644
index 1a4c3b350..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-store.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-store.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-upgrade-nix.md b/doc/manual/src/command-ref/new-cli/nix3-upgrade-nix.md
deleted file mode 100644
index 39f095573..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-upgrade-nix.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-upgrade-nix.md}}
diff --git a/doc/manual/src/command-ref/new-cli/nix3-why-depends.md b/doc/manual/src/command-ref/new-cli/nix3-why-depends.md
deleted file mode 100644
index c6629ffcd..000000000
--- a/doc/manual/src/command-ref/new-cli/nix3-why-depends.md
+++ /dev/null
@@ -1 +0,0 @@
-{{#include @generated@/command-ref/new-cli/nix3-why-depends.md}}
diff --git a/doc/manual/src/command-ref/nix-build.md b/doc/manual/src/command-ref/nix-build.md
deleted file mode 100644
index b548edf82..000000000
--- a/doc/manual/src/command-ref/nix-build.md
+++ /dev/null
@@ -1,125 +0,0 @@
-# Name
-
-`nix-build` - build a Nix expression
-
-# Synopsis
-
-`nix-build` [*paths…*]
- [`--arg` *name* *value*]
- [`--argstr` *name* *value*]
- [{`--attr` | `-A`} *attrPath*]
- [`--no-out-link`]
- [`--dry-run`]
- [{`--out-link` | `-o`} *outlink*]
-
-# Disambiguation
-
-This man page describes the command `nix-build`, which is distinct from `nix
-build`. For documentation on the latter, run `nix build --help` or see `man
-nix3-build`.
-
-# Description
-
-The `nix-build` command builds the derivations described by the Nix
-expressions in *paths*. If the build succeeds, it places a symlink to
-the result in the current directory. The symlink is called `result`. If
-there are multiple Nix expressions, or the Nix expressions evaluate to
-multiple derivations, multiple sequentially numbered symlinks are
-created (`result`, `result-2`, and so on).
-
-If no *paths* are specified, then `nix-build` will use `default.nix` in
-the current directory, if it exists.
-
-If an element of *paths* starts with `http://` or `https://`, it is
-interpreted as the URL of a tarball that will be downloaded and unpacked
-to a temporary location. The tarball must include a single top-level
-directory containing at least a file named `default.nix`.
-
-`nix-build` is essentially a wrapper around
-[`nix-instantiate`](nix-instantiate.md) (to translate a high-level Nix
-expression to a low-level [store derivation]) and [`nix-store
---realise`](@docroot@/command-ref/nix-store/realise.md) (to build the store
-derivation).
-
-[store derivation]: ../glossary.md#gloss-store-derivation
-
-> **Warning**
->
-> The result of the build is automatically registered as a root of the
-> Nix garbage collector. This root disappears automatically when the
-> `result` symlink is deleted or renamed. So don’t rename the symlink.
-
-# Options
-
-All options not listed here are passed to
-[`nix-store --realise`](nix-store/realise.md),
-except for `--arg` and `--attr` / `-A` which are passed to [`nix-instantiate`](nix-instantiate.md).
-
- - [`--no-out-link`](#opt-no-out-link)
-
- Do not create a symlink to the output path. Note that as a result
- the output does not become a root of the garbage collector, and so
- might be deleted by `nix-store --gc`.
-
- - [`--dry-run`](#opt-dry-run)
-
- Show what store paths would be built or downloaded.
-
- - [`--out-link`](#opt-out-link) / `-o` *outlink*
-
- Change the name of the symlink to the output path created from
- `result` to *outlink*.
-
-{{#include ./status-build-failure.md}}
-
-{{#include ./opt-common.md}}
-
-{{#include ./env-common.md}}
-
-# Examples
-
-```console
-$ nix-build '' --attr firefox
-store derivation is /nix/store/qybprl8sz2lc...-firefox-1.5.0.7.drv
-/nix/store/d18hyl92g30l...-firefox-1.5.0.7
-
-$ ls -l result
-lrwxrwxrwx ... result -> /nix/store/d18hyl92g30l...-firefox-1.5.0.7
-
-$ ls ./result/bin/
-firefox firefox-config
-```
-
-If a derivation has multiple outputs, `nix-build` will build the default
-(first) output. You can also build all outputs:
-
-```console
-$ nix-build '' --attr openssl.all
-```
-
-This will create a symlink for each output named `result-outputname`.
-The suffix is omitted if the output name is `out`. So if `openssl` has
-outputs `out`, `bin` and `man`, `nix-build` will create symlinks
-`result`, `result-bin` and `result-man`. It’s also possible to build a
-specific output:
-
-```console
-$ nix-build '' --attr openssl.man
-```
-
-This will create a symlink `result-man`.
-
-Build a Nix expression given on the command line:
-
-```console
-$ nix-build --expr 'with import { }; runCommand "foo" { } "echo bar > $out"'
-$ cat ./result
-bar
-```
-
-Build the GNU Hello package from the latest revision of the master
-branch of Nixpkgs:
-
-```console
-$ nix-build https://github.com/NixOS/nixpkgs/archive/master.tar.gz --attr hello
-```
diff --git a/doc/manual/src/command-ref/nix-channel.md b/doc/manual/src/command-ref/nix-channel.md
deleted file mode 100644
index cebbc7b00..000000000
--- a/doc/manual/src/command-ref/nix-channel.md
+++ /dev/null
@@ -1,106 +0,0 @@
-# Name
-
-`nix-channel` - manage Nix channels
-
-# Synopsis
-
-`nix-channel` {`--add` url [*name*] | `--remove` *name* | `--list` | `--update` [*names…*] | `--list-generations` | `--rollback` [*generation*] }
-
-# Description
-
-Channels are a mechanism for referencing remote Nix expressions and conveniently retrieving their latest version.
-
-The moving parts of channels are:
-- The official channels listed at
-- The user-specific list of [subscribed channels](#subscribed-channels)
-- The [downloaded channel contents](#channels)
-- The [Nix expression search path](@docroot@/command-ref/conf-file.md#conf-nix-path), set with the [`-I` option](#opt-i) or the [`NIX_PATH` environment variable](#env-NIX_PATH)
-
-> **Note**
->
-> The state of a subscribed channel is external to the Nix expressions relying on it.
-> This may limit reproducibility.
->
-> Dependencies on other Nix expressions can be declared explicitly with:
-> - [`fetchurl`](@docroot@/language/builtins.md#builtins-fetchurl), [`fetchTarball`](@docroot@/language/builtins.md#builtins-fetchTarball), or [`fetchGit`](@docroot@/language/builtins.md#builtins-fetchGit) in Nix expressions
-> - the [`-I` option](@docroot@/command-ref/opt-common.md#opt-I) in command line invocations
-
-This command has the following operations:
-
- - `--add` *url* \[*name*\]\
- Add a channel *name* located at *url* to the list of subscribed channels.
- If *name* is omitted, default to the last component of *url*, with the suffixes `-stable` or `-unstable` removed.
-
- > **Note**
- >
- > `--add` does not automatically perform an update.
- > Use `--update` explicitly.
-
- A channel URL must point to a directory containing a file `nixexprs.tar.gz`.
- At the top level, that tarball must contain a single directory with a `default.nix` file that serves as the channel’s entry point.
-
- - `--remove` *name*\
- Remove the channel *name* from the list of subscribed channels.
-
- - `--list`\
- Print the names and URLs of all subscribed channels on standard output.
-
- - `--update` \[*names*…\]\
- Download the Nix expressions of subscribed channels and create a new generation.
- Update all channels if none is specified, and only those included in *names* otherwise.
-
- - `--list-generations`\
- Prints a list of all the current existing generations for the
- channel profile.
-
- Works the same way as
- ```
- nix-env --profile /nix/var/nix/profiles/per-user/$USER/channels --list-generations
- ```
-
- - `--rollback` \[*generation*\]\
- Revert channels to the state before the last call to `nix-channel --update`.
- Optionally, you can specify a specific channel *generation* number to restore.
-
-{{#include ./opt-common.md}}
-
-{{#include ./env-common.md}}
-
-# Files
-
-`nix-channel` operates on the following files.
-
-{{#include ./files/channels.md}}
-
-# Examples
-
-Subscribe to the Nixpkgs channel and run `hello` from the GNU Hello package:
-
-```console
-$ nix-channel --add https://nixos.org/channels/nixpkgs-unstable
-$ nix-channel --list
-nixpkgs https://nixos.org/channels/nixpkgs
-$ nix-channel --update
-$ nix-shell -p hello --run hello
-hello
-```
-
-Revert channel updates using `--rollback`:
-
-```console
-$ nix-instantiate --eval '' --attr lib.version
-"22.11pre296212.530a53dcbc9"
-
-$ nix-channel --rollback
-switching from generation 483 to 482
-
-$ nix-instantiate --eval '' --attr lib.version
-"22.11pre281526.d0419badfad"
-```
-
-Remove a channel:
-
-```console
-$ nix-channel --remove nixpkgs
-$ nix-channel --list
-```
diff --git a/doc/manual/src/command-ref/nix-collect-garbage.md b/doc/manual/src/command-ref/nix-collect-garbage.md
deleted file mode 100644
index f9a3f1940..000000000
--- a/doc/manual/src/command-ref/nix-collect-garbage.md
+++ /dev/null
@@ -1,79 +0,0 @@
-# Name
-
-`nix-collect-garbage` - delete unreachable [store objects]
-
-# Synopsis
-
-`nix-collect-garbage` [`--delete-old`] [`-d`] [`--delete-older-than` *period*] [`--max-freed` *bytes*] [`--dry-run`]
-
-# Description
-
-The command `nix-collect-garbage` is mostly an alias of [`nix-store --gc`](@docroot@/command-ref/nix-store/gc.md).
-That is, it deletes all unreachable [store objects] in the Nix store to clean up your system.
-
-However, it provides two additional options,
-[`--delete-old`](#opt-delete-old) and [`--delete-older-than`](#opt-delete-older-than),
-which also delete old [profiles], allowing potentially more [store objects] to be deleted because profiles are also garbage collection roots.
-These options are the equivalent of running
-[`nix-env --delete-generations`](@docroot@/command-ref/nix-env/delete-generations.md)
-with various augments on multiple profiles,
-prior to running `nix-collect-garbage` (or just `nix-store --gc`) without any flags.
-
-> **Note**
->
-> Deleting previous configurations makes rollbacks to them impossible.
-
-These flags should be used with care, because they potentially delete generations of profiles used by other users on the system.
-
-## Locations searched for profiles
-
-`nix-collect-garbage` cannot know about all profiles; that information doesn't exist.
-Instead, it looks in a few locations, and acts on all profiles it finds there:
-
-1. The default profile locations as specified in the [profiles] section of the manual.
-
-2. > **NOTE**
- >
- > Not stable; subject to change
- >
- > Do not rely on this functionality; it just exists for migration purposes and is may change in the future.
- > These deprecated paths remain a private implementation detail of Lix.
-
-
-
- `$NIX_STATE_DIR/profiles` and `$NIX_STATE_DIR/profiles/per-user`.
-
- With the exception of `$NIX_STATE_DIR/profiles/per-user/root` and `$NIX_STATE_DIR/profiles/default`, these directories are no longer used by other commands.
- `nix-collect-garbage` looks there anyways in order to clean up profiles from older versions of Nix.
-
-# Options
-
-These options are for deleting old [profiles] prior to deleting unreachable [store objects].
-
-- [`--delete-old`](#opt-delete-old) / `-d`\
- Delete all old generations of profiles.
-
- This is the equivalent of invoking `nix-env --delete-generations old` on each found profile.
-
-- [`--delete-older-than`](#opt-delete-older-than) *period*\
- Delete all generations of profiles older than the specified amount (except for the generations that were active at that point in time).
- *period* is a value such as `30d`, which would mean 30 days.
-
- This is the equivalent of invoking [`nix-env --delete-generations `](@docroot@/command-ref/nix-env/delete-generations.md#generations-time) on each found profile.
- See the documentation of that command for additional information about the *period* argument.
-
-{{#include ./opt-common.md}}
-
-{{#include ./env-common.md}}
-
-# Example
-
-To delete from the Nix store everything that is not used by the current
-generations of each profile, do
-
-```console
-$ nix-collect-garbage -d
-```
-
-[profiles]: @docroot@/command-ref/files/profiles.md
-[store objects]: @docroot@/glossary.md#gloss-store-object
diff --git a/doc/manual/src/command-ref/nix-copy-closure.md b/doc/manual/src/command-ref/nix-copy-closure.md
deleted file mode 100644
index fbf6828da..000000000
--- a/doc/manual/src/command-ref/nix-copy-closure.md
+++ /dev/null
@@ -1,91 +0,0 @@
-# Name
-
-`nix-copy-closure` - copy a closure to or from a remote machine via SSH
-
-# Synopsis
-
-`nix-copy-closure`
- [`--to` | `--from`]
- [`--gzip`]
- [`--include-outputs`]
- [`--use-substitutes` | `-s`]
- [`-v`]
- _user@machine_ _paths_
-
-# Description
-
-`nix-copy-closure` gives you an easy and efficient way to exchange
-software between machines. Given one or more Nix store _paths_ on the
-local machine, `nix-copy-closure` computes the closure of those paths
-(i.e. all their dependencies in the Nix store), and copies all paths
-in the closure to the remote machine via the `ssh` (Secure Shell)
-command. With the `--from` option, the direction is reversed: the
-closure of _paths_ on a remote machine is copied to the Nix store on
-the local machine.
-
-This command is efficient because it only sends the store paths
-that are missing on the target machine.
-
-Since `nix-copy-closure` calls `ssh`, you may be asked to type in the
-appropriate password or passphrase. In fact, you may be asked _twice_
-because `nix-copy-closure` currently connects twice to the remote
-machine, first to get the set of paths missing on the target machine,
-and second to send the dump of those paths. When using public key
-authentication, you can avoid typing the passphrase with `ssh-agent`.
-
-# Options
-
- - `--to`\
- Copy the closure of _paths_ from the local Nix store to the Nix
- store on _machine_. This is the default.
-
- - `--from`\
- Copy the closure of _paths_ from the Nix store on _machine_ to the
- local Nix store.
-
- - `--gzip`\
- Enable compression of the SSH connection.
-
- - `--include-outputs`\
- Also copy the outputs of [store derivation]s included in the closure.
-
- [store derivation]: ../glossary.md#gloss-store-derivation
-
- - `--use-substitutes` / `-s`\
- Attempt to download missing paths on the target machine using Nix’s
- substitute mechanism. Any paths that cannot be substituted on the
- target are still copied normally from the source. This is useful,
- for instance, if the connection between the source and target
- machine is slow, but the connection between the target machine and
- `nixos.org` (the default binary cache server) is
- fast.
-
- - `-v`\
- Show verbose output.
-
-{{#include ./opt-common.md}}
-
-# Environment variables
-
- - `NIX_SSHOPTS`\
- Additional options to be passed to `ssh` on the command
- line.
-
-{{#include ./env-common.md}}
-
-# Examples
-
-Copy Firefox with all its dependencies to a remote machine:
-
-```console
-$ nix-copy-closure --to alice@itchy.labs $(type -tP firefox)
-```
-
-Copy Subversion from a remote machine and then install it into a user
-environment:
-
-```console
-$ nix-copy-closure --from alice@itchy.labs \
- /nix/store/0dj0503hjxy5mbwlafv1rsbdiyx1gkdy-subversion-1.4.4
-$ nix-env --install /nix/store/0dj0503hjxy5mbwlafv1rsbdiyx1gkdy-subversion-1.4.4
-```
diff --git a/doc/manual/src/command-ref/nix-daemon.md b/doc/manual/src/command-ref/nix-daemon.md
deleted file mode 100644
index 268bbc558..000000000
--- a/doc/manual/src/command-ref/nix-daemon.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Name
-
-`nix-daemon` - Lix multi-user support daemon
-
-# Synopsis
-
-`nix-daemon`
-
-# Description
-
-The Lix daemon is necessary in multi-user Lix installations. It runs
-build tasks and other operations on the Nix store on behalf of
-unprivileged users.
diff --git a/doc/manual/src/command-ref/nix-env.md b/doc/manual/src/command-ref/nix-env.md
deleted file mode 100644
index 5a9e05fed..000000000
--- a/doc/manual/src/command-ref/nix-env.md
+++ /dev/null
@@ -1,90 +0,0 @@
-# Name
-
-`nix-env` - manipulate or query Nix user environments
-
-# Synopsis
-
-`nix-env` *operation* [*options*] [*arguments…*]
- [`--option` *name* *value*]
- [`--arg` *name* *value*]
- [`--argstr` *name* *value*]
- [{`--file` | `-f`} *path*]
- [{`--profile` | `-p`} *path*]
- [`--system-filter` *system*]
- [`--dry-run`]
-
-# Description
-
-The command `nix-env` is used to manipulate Nix user environments. User
-environments are sets of software packages available to a user at some
-point in time. In other words, they are a synthesised view of the
-programs available in the Nix store. There may be many user
-environments: different users can have different environments, and
-individual users can switch between different environments.
-
-`nix-env` takes exactly one *operation* flag which indicates the
-subcommand to be performed. The following operations are available:
-
-- [`--install`](./nix-env/install.md) - add packages to user environment
-- [`--upgrade`](./nix-env/upgrade.md) - upgrade packages in user environment
-- [`--uninstall`](./nix-env/uninstall.md) - remove packages from user environment
-- [`--set`](./nix-env/set.md) - set profile to contain a specified derivation
-- [`--set-flag`](./nix-env/set-flag.md) - modify meta attributes of installed packages
-- [`--query`](./nix-env/query.md) - display information about packages
-- [`--switch-profile`](./nix-env/switch-profile.md) - set user environment to a given profile
-- [`--list-generations`](./nix-env/list-generations.md) - list profile generations
-- [`--delete-generations`](./nix-env/delete-generations.md) - delete profile generations
-- [`--switch-generation`](./nix-env/switch-generation.md) - set user environment to a given profile generation
-- [`--rollback`](./nix-env/rollback.md) - set user environment to previous generation
-
-These pages can be viewed offline:
-
-- `man nix-env-`.
-
- Example: `man nix-env-install`
-
-- `nix-env --help --`
-
- Example: `nix-env --help --install`
-
-# Selectors
-
-Several commands, such as `nix-env --query ` and `nix-env --install `, take a list of
-arguments that specify the packages on which to operate. These are
-extended regular expressions that must match the entire name of the
-package. (For details on regular expressions, see **regex**(7).) The match is
-case-sensitive. The regular expression can optionally be followed by a
-dash and a version number; if omitted, any version of the package will
-match. Here are some examples:
-
- - `firefox`\
- Matches the package name `firefox` and any version.
-
- - `firefox-32.0`\
- Matches the package name `firefox` and version `32.0`.
-
- - `gtk\\+`\
- Matches the package name `gtk+`. The `+` character must be escaped
- using a backslash to prevent it from being interpreted as a
- quantifier, and the backslash must be escaped in turn with another
- backslash to ensure that the shell passes it on.
-
- - `.\*`\
- Matches any package name. This is the default for most commands.
-
- - `'.*zip.*'`\
- Matches any package name containing the string `zip`. Note the dots:
- `'*zip*'` does not work, because in a regular expression, the
- character `*` is interpreted as a quantifier.
-
- - `'.*(firefox|chromium).*'`\
- Matches any package name containing the strings `firefox` or
- `chromium`.
-
-# Files
-
-`nix-env` operates on the following files.
-
-{{#include ./files/default-nix-expression.md}}
-
-{{#include ./files/profiles.md}}
diff --git a/doc/manual/src/command-ref/nix-env/delete-generations.md b/doc/manual/src/command-ref/nix-env/delete-generations.md
deleted file mode 100644
index adc6fc219..000000000
--- a/doc/manual/src/command-ref/nix-env/delete-generations.md
+++ /dev/null
@@ -1,95 +0,0 @@
-# Name
-
-`nix-env --delete-generations` - delete profile generations
-
-# Synopsis
-
-`nix-env` `--delete-generations` *generations*
-
-# Description
-
-This operation deletes the specified generations of the current profile.
-
-*generations* can be a one of the following:
-
-- `...` :\
- A list of generation numbers, each one a separate command-line argument.
-
- Delete exactly the profile generations given by their generation number.
- Deleting the current generation is not allowed.
-
-- The special value `old`
-
- Delete all generations except the current one.
-
- > **WARNING**
- >
- > Older *and newer* generations will be deleted by this operation.
- >
- > One might expect this to just delete older generations than the curent one, but that is only true if the current generation is also the latest.
- > Because one can roll back to a previous generation, it is possible to have generations newer than the current one.
- > They will also be deleted.
-
-- `d` :\
- The last *number* days
-
- *Example*: `30d`
-
- Delete all generations created more than *number* days ago, except the most recent one of them.
- This allows rolling back to generations that were available within the specified period.
-
-- `+` :\
- The last *number* generations up to the present
-
- *Example*: `+5`
-
- Keep the last *number* generations, along with any newer than current.
-
-Periodically deleting old generations is important to make garbage collection
-effective.
-The is because profiles are also garbage collection roots — any [store object] reachable from a profile is "alive" and ineligible for deletion.
-
-[store object]: @docroot@/glossary.md#gloss-store-object
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-## Delete explicit generation numbers
-
-```console
-$ nix-env --delete-generations 3 4 8
-```
-
-Delete the generations numbered 3, 4, and 8, so long as the current active generation is not any of those.
-
-## Keep most-recent by count (number of generations)
-
-```console
-$ nix-env --delete-generations +5
-```
-
-Suppose `30` is the current generation, and we currently have generations numbered `20` through `32`.
-
-Then this command will delete generations `20` through `25` (`<= 30 - 5`),
-and keep generations `26` through `31` (`> 30 - 5`).
-
-## Keep most-recent by time (number of days)
-
-```console
-$ nix-env --delete-generations 30d
-```
-
-This command will delete all generations older than 30 days, except for the generation that was active 30 days ago (if it currently exists).
-
-## Delete all older
-
-```console
-$ nix-env --profile other_profile --delete-generations old
-```
diff --git a/doc/manual/src/command-ref/nix-env/env-common.md b/doc/manual/src/command-ref/nix-env/env-common.md
deleted file mode 100644
index 735817959..000000000
--- a/doc/manual/src/command-ref/nix-env/env-common.md
+++ /dev/null
@@ -1,6 +0,0 @@
-# Environment variables
-
-- `NIX_PROFILE`\
- Location of the Nix profile. Defaults to the target of the symlink
- `~/.nix-profile`, if it exists, or `/nix/var/nix/profiles/default`
- otherwise.
diff --git a/doc/manual/src/command-ref/nix-env/install.md b/doc/manual/src/command-ref/nix-env/install.md
deleted file mode 100644
index 5c532b856..000000000
--- a/doc/manual/src/command-ref/nix-env/install.md
+++ /dev/null
@@ -1,186 +0,0 @@
-# Name
-
-`nix-env --install` - add packages to user environment
-
-# Synopsis
-
-`nix-env` {`--install` | `-i`} *args…*
- [{`--prebuilt-only` | `-b`}]
- [{`--attr` | `-A`}]
- [`--from-expression`] [`-E`]
- [`--from-profile` *path*]
- [`--preserve-installed` | `-P`]
- [`--remove-all` | `-r`]
-
-# Description
-
-The install operation creates a new user environment, based on the
-current generation of the active profile, to which a set of store paths
-described by *args* is added. The arguments *args* map to store paths in
-a number of possible ways:
-
- - By default, *args* is a set of derivation names denoting derivations
- in the active Nix expression. These are realised, and the resulting
- output paths are installed. Currently installed derivations with a
- name equal to the name of a derivation being added are removed
- unless the option `--preserve-installed` is specified.
-
- If there are multiple derivations matching a name in *args* that
- have the same name (e.g., `gcc-3.3.6` and `gcc-4.1.1`), then the
- derivation with the highest *priority* is used. A derivation can
- define a priority by declaring the `meta.priority` attribute. This
- attribute should be a number, with a higher value denoting a lower
- priority. The default priority is `5`.
-
- If there are multiple matching derivations with the same priority,
- then the derivation with the highest version will be installed.
-
- You can force the installation of multiple derivations with the same
- name by being specific about the versions. For instance, `nix-env --install
- gcc-3.3.6 gcc-4.1.1` will install both version of GCC (and will
- probably cause a user environment conflict\!).
-
- - If `--attr` (`-A`) is specified, the arguments are *attribute
- paths* that select attributes from the top-level Nix
- expression. This is faster than using derivation names and
- unambiguous. To find out the attribute paths of available
- packages, use `nix-env --query --available --attr-path `.
-
- - If `--from-profile` *path* is given, *args* is a set of names
- denoting installed store paths in the profile *path*. This is an
- easy way to copy user environment elements from one profile to
- another.
-
- - If `--from-expression` is given, *args* are Nix
- [functions](@docroot@/language/constructs.md#functions)
- that are called with the active Nix expression as their single
- argument. The derivations returned by those function calls are
- installed. This allows derivations to be specified in an
- unambiguous way, which is necessary if there are multiple
- derivations with the same name.
-
- - If *args* are [store derivations](@docroot@/glossary.md#gloss-store-derivation), then these are
- [realised](@docroot@/command-ref/nix-store/realise.md), and the resulting output paths
- are installed.
-
- - If *args* are store paths that are not store derivations, then these
- are [realised](@docroot@/command-ref/nix-store/realise.md) and installed.
-
- - By default all outputs are installed for each derivation. That can
- be reduced by setting `meta.outputsToInstall`.
-
-# Flags
-
- - `--prebuilt-only` / `-b`\
- Use only derivations for which a substitute is registered, i.e.,
- there is a pre-built binary available that can be downloaded in lieu
- of building the derivation. Thus, no packages will be built from
- source.
-
- - `--preserve-installed` / `-P`\
- Do not remove derivations with a name matching one of the
- derivations being installed. Usually, trying to have two versions of
- the same package installed in the same generation of a profile will
- lead to an error in building the generation, due to file name
- clashes between the two versions. However, this is not the case for
- all packages.
-
- - `--remove-all` / `-r`\
- Remove all previously installed packages first. This is equivalent
- to running `nix-env --uninstall '.*'` first, except that everything happens
- in a single transaction.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-To install a package using a specific attribute path from the active Nix expression:
-
-```console
-$ nix-env --install --attr gcc40mips
-installing `gcc-4.0.2'
-$ nix-env --install --attr xorg.xorgserver
-installing `xorg-server-1.2.0'
-```
-
-To install a specific version of `gcc` using the derivation name:
-
-```console
-$ nix-env --install gcc-3.3.2
-installing `gcc-3.3.2'
-uninstalling `gcc-3.1'
-```
-
-Using attribute path for selecting a package is preferred,
-as it is much faster and there will not be multiple matches.
-
-Note the previously installed version is removed, since
-`--preserve-installed` was not specified.
-
-To install an arbitrary version:
-
-```console
-$ nix-env --install gcc
-installing `gcc-3.3.2'
-```
-
-To install all derivations in the Nix expression `foo.nix`:
-
-```console
-$ nix-env --file ~/foo.nix --install '.*'
-```
-
-To copy the store path with symbolic name `gcc` from another profile:
-
-```console
-$ nix-env --install --from-profile /nix/var/nix/profiles/foo gcc
-```
-
-To install a specific [store derivation] (typically created by
-`nix-instantiate`):
-
-```console
-$ nix-env --install /nix/store/fibjb1bfbpm5mrsxc4mh2d8n37sxh91i-gcc-3.4.3.drv
-```
-
-To install a specific output path:
-
-```console
-$ nix-env --install /nix/store/y3cgx0xj1p4iv9x0pnnmdhr8iyg741vk-gcc-3.4.3
-```
-
-To install from a Nix expression specified on the command-line:
-
-```console
-$ nix-env --file ./foo.nix --install --expr \
- 'f: (f {system = "i686-linux";}).subversionWithJava'
-```
-
-I.e., this evaluates to `(f: (f {system =
-"i686-linux";}).subversionWithJava) (import ./foo.nix)`, thus selecting
-the `subversionWithJava` attribute from the set returned by calling the
-function defined in `./foo.nix`.
-
-A dry-run tells you which paths will be downloaded or built from source:
-
-```console
-$ nix-env --file '' --install --attr hello --dry-run
-(dry run; not doing anything)
-installing ‘hello-2.10’
-this path will be fetched (0.04 MiB download, 0.19 MiB unpacked):
- /nix/store/wkhdf9jinag5750mqlax6z2zbwhqb76n-hello-2.10
- ...
-```
-
-To install Firefox from the latest revision in the Nixpkgs/NixOS 14.12
-channel:
-
-```console
-$ nix-env --file https://github.com/NixOS/nixpkgs/archive/nixos-14.12.tar.gz --install --attr firefox
-```
diff --git a/doc/manual/src/command-ref/nix-env/list-generations.md b/doc/manual/src/command-ref/nix-env/list-generations.md
deleted file mode 100644
index ab04122cf..000000000
--- a/doc/manual/src/command-ref/nix-env/list-generations.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Name
-
-`nix-env --list-generations` - list profile generations
-
-# Synopsis
-
-`nix-env` `--list-generations`
-
-# Description
-
-This operation print a list of all the currently existing generations
-for the active profile. These may be switched to using the
-`--switch-generation` operation. It also prints the creation date of the
-generation, and indicates the current generation.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-```console
-$ nix-env --list-generations
- 95 2004-02-06 11:48:24
- 96 2004-02-06 11:49:01
- 97 2004-02-06 16:22:45
- 98 2004-02-06 16:24:33 (current)
-```
diff --git a/doc/manual/src/command-ref/nix-env/opt-common.md b/doc/manual/src/command-ref/nix-env/opt-common.md
deleted file mode 100644
index 636281b6d..000000000
--- a/doc/manual/src/command-ref/nix-env/opt-common.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# Options
-
-The following options are allowed for all `nix-env` operations, but may not always have an effect.
-
- - `--file` / `-f` *path*\
- Specifies the Nix expression (designated below as the *active Nix
- expression*) used by the `--install`, `--upgrade`, and `--query
- --available` operations to obtain derivations. The default is
- `~/.nix-defexpr`.
-
- If the argument starts with `http://` or `https://`, it is
- interpreted as the URL of a tarball that will be downloaded and
- unpacked to a temporary location. The tarball must include a single
- top-level directory containing at least a file named `default.nix`.
-
- - `--profile` / `-p` *path*\
- Specifies the profile to be used by those operations that operate on
- a profile (designated below as the *active profile*). A profile is a
- sequence of user environments called *generations*, one of which is
- the *current generation*.
-
- - `--dry-run`\
- For the `--install`, `--upgrade`, `--uninstall`,
- `--switch-generation`, `--delete-generations` and `--rollback`
- operations, this flag will cause `nix-env` to print what *would* be
- done if this flag had not been specified, without actually doing it.
-
- `--dry-run` also prints out which paths will be
- [substituted](@docroot@/glossary.md) (i.e., downloaded) and which paths
- will be built from source (because no substitute is available).
-
- - `--system-filter` *system*\
- By default, operations such as `--query
- --available` show derivations matching any platform. This option
- allows you to use derivations for the specified platform *system*.
diff --git a/doc/manual/src/command-ref/nix-env/query.md b/doc/manual/src/command-ref/nix-env/query.md
deleted file mode 100644
index 3fbb30839..000000000
--- a/doc/manual/src/command-ref/nix-env/query.md
+++ /dev/null
@@ -1,214 +0,0 @@
-# Name
-
-`nix-env --query` - display information about packages
-
-# Synopsis
-
-`nix-env` {`--query` | `-q`} *names…*
- [`--installed` | `--available` | `-a`]
- [{`--status` | `-s`}]
- [{`--attr-path` | `-P`}]
- [`--no-name`]
- [{`--compare-versions` | `-c`}]
- [`--system`]
- [`--drv-path`]
- [`--out-path`]
- [`--description`]
- [`--meta`]
- [`--xml`]
- [`--json`]
- [{`--prebuilt-only` | `-b`}]
- [{`--attr` | `-A`} *attribute-path*]
-
-# Description
-
-The query operation displays information about either the store paths
-that are installed in the current generation of the active profile
-(`--installed`), or the derivations that are available for installation
-in the active Nix expression (`--available`). It only prints information
-about derivations whose symbolic name matches one of *names*.
-
-The derivations are sorted by their `name` attributes.
-
-# Source selection
-
-The following flags specify the set of things on which the query
-operates.
-
- - `--installed`\
- The query operates on the store paths that are installed in the
- current generation of the active profile. This is the default.
-
- - `--available`; `-a`\
- The query operates on the derivations that are available in the
- active Nix expression.
-
-# Queries
-
-The following flags specify what information to display about the
-selected derivations. Multiple flags may be specified, in which case the
-information is shown in the order given here. Note that the name of the
-derivation is shown unless `--no-name` is specified.
-
- - `--xml`\
- Print the result in an XML representation suitable for automatic
- processing by other tools. The root element is called `items`, which
- contains a `item` element for each available or installed
- derivation. The fields discussed below are all stored in attributes
- of the `item` elements.
-
- - `--json`\
- Print the result in a JSON representation suitable for automatic
- processing by other tools.
-
- - `--prebuilt-only` / `-b`\
- Show only derivations for which a substitute is registered, i.e.,
- there is a pre-built binary available that can be downloaded in lieu
- of building the derivation. Thus, this shows all packages that
- probably can be installed quickly.
-
- - `--status`; `-s`\
- Print the *status* of the derivation. The status consists of three
- characters. The first is `I` or `-`, indicating whether the
- derivation is currently installed in the current generation of the
- active profile. This is by definition the case for `--installed`,
- but not for `--available`. The second is `P` or `-`, indicating
- whether the derivation is present on the system. This indicates
- whether installation of an available derivation will require the
- derivation to be built. The third is `S` or `-`, indicating whether
- a substitute is available for the derivation.
-
- - `--attr-path`; `-P`\
- Print the *attribute path* of the derivation, which can be used to
- unambiguously select it using the `--attr` option available in
- commands that install derivations like `nix-env --install`. This
- option only works together with `--available`
-
- - `--no-name`\
- Suppress printing of the `name` attribute of each derivation.
-
- - `--compare-versions` / `-c`\
- Compare installed versions to available versions, or vice versa (if
- `--available` is given). This is useful for quickly seeing whether
- upgrades for installed packages are available in a Nix expression. A
- column is added with the following meaning:
-
- - `<` *version*\
- A newer version of the package is available or installed.
-
- - `=` *version*\
- At most the same version of the package is available or
- installed.
-
- - `>` *version*\
- Only older versions of the package are available or installed.
-
- - `- ?`\
- No version of the package is available or installed.
-
- - `--system`\
- Print the `system` attribute of the derivation.
-
- - `--drv-path`\
- Print the path of the [store derivation](@docroot@/glossary.md#gloss-store-derivation).
-
- - `--out-path`\
- Print the output path of the derivation.
-
- - `--description`\
- Print a short (one-line) description of the derivation, if
- available. The description is taken from the `meta.description`
- attribute of the derivation.
-
- - `--meta`\
- Print all of the meta-attributes of the derivation. This option is
- only available with `--xml` or `--json`.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-To show installed packages:
-
-```console
-$ nix-env --query
-bison-1.875c
-docbook-xml-4.2
-firefox-1.0.4
-MPlayer-1.0pre7
-ORBit2-2.8.3
-…
-```
-
-To show available packages:
-
-```console
-$ nix-env --query --available
-firefox-1.0.7
-GConf-2.4.0.1
-MPlayer-1.0pre7
-ORBit2-2.8.3
-…
-```
-
-To show the status of available packages:
-
-```console
-$ nix-env --query --available --status
--P- firefox-1.0.7 (not installed but present)
---S GConf-2.4.0.1 (not present, but there is a substitute for fast installation)
---S MPlayer-1.0pre3 (i.e., this is not the installed MPlayer, even though the version is the same!)
-IP- ORBit2-2.8.3 (installed and by definition present)
-…
-```
-
-To show available packages in the Nix expression `foo.nix`:
-
-```console
-$ nix-env --file ./foo.nix --query --available
-foo-1.2.3
-```
-
-To compare installed versions to what’s available:
-
-```console
-$ nix-env --query --compare-versions
-...
-acrobat-reader-7.0 - ? (package is not available at all)
-autoconf-2.59 = 2.59 (same version)
-firefox-1.0.4 < 1.0.7 (a more recent version is available)
-...
-```
-
-To show all packages with “`zip`” in the name:
-
-```console
-$ nix-env --query --available '.*zip.*'
-bzip2-1.0.6
-gzip-1.6
-zip-3.0
-…
-```
-
-To show all packages with “`firefox`” or “`chromium`” in the name:
-
-```console
-$ nix-env --query --available '.*(firefox|chromium).*'
-chromium-37.0.2062.94
-chromium-beta-38.0.2125.24
-firefox-32.0.3
-firefox-with-plugins-13.0.1
-…
-```
-
-To show all packages in the latest revision of the Nixpkgs repository:
-
-```console
-$ nix-env --file https://github.com/NixOS/nixpkgs/archive/master.tar.gz --query --available
-```
diff --git a/doc/manual/src/command-ref/nix-env/rollback.md b/doc/manual/src/command-ref/nix-env/rollback.md
deleted file mode 100644
index 1e3958cfc..000000000
--- a/doc/manual/src/command-ref/nix-env/rollback.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Name
-
-`nix-env --rollback` - set user environment to previous generation
-
-# Synopsis
-
-`nix-env` `--rollback`
-
-# Description
-
-This operation switches to the “previous” generation of the active
-profile, that is, the highest numbered generation lower than the current
-generation, if it exists. It is just a convenience wrapper around
-`--list-generations` and `--switch-generation`.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-```console
-$ nix-env --rollback
-switching from generation 92 to 91
-```
-
-```console
-$ nix-env --rollback
-error: no generation older than the current (91) exists
-```
diff --git a/doc/manual/src/command-ref/nix-env/set-flag.md b/doc/manual/src/command-ref/nix-env/set-flag.md
deleted file mode 100644
index 68a88d288..000000000
--- a/doc/manual/src/command-ref/nix-env/set-flag.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Name
-
-`nix-env --set-flag` - modify meta attributes of installed packages
-
-# Synopsis
-
-`nix-env` `--set-flag` *name* *value* *drvnames*
-
-# Description
-
-The `--set-flag` operation allows meta attributes of installed packages
-to be modified. There are several attributes that can be usefully
-modified, because they affect the behaviour of `nix-env` or the user
-environment build script:
-
- - `priority` can be changed to resolve filename clashes. The user
- environment build script uses the `meta.priority` attribute of
- derivations to resolve filename collisions between packages. Lower
- priority values denote a higher priority. For instance, the GCC
- wrapper package and the Binutils package in Nixpkgs both have a file
- `bin/ld`, so previously if you tried to install both you would get a
- collision. Now, on the other hand, the GCC wrapper declares a higher
- priority than Binutils, so the former’s `bin/ld` is symlinked in the
- user environment.
-
- - `keep` can be set to `true` to prevent the package from being
- upgraded or replaced. This is useful if you want to hang on to an
- older version of a package.
-
- - `active` can be set to `false` to “disable” the package. That is, no
- symlinks will be generated to the files of the package, but it
- remains part of the profile (so it won’t be garbage-collected). It
- can be set back to `true` to re-enable the package.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-To prevent the currently installed Firefox from being upgraded:
-
-```console
-$ nix-env --set-flag keep true firefox
-```
-
-After this, `nix-env --upgrade ` will ignore Firefox.
-
-To disable the currently installed Firefox, then install a new Firefox
-while the old remains part of the profile:
-
-```console
-$ nix-env --query
-firefox-2.0.0.9 (the current one)
-
-$ nix-env --preserve-installed --install firefox-2.0.0.11
-installing `firefox-2.0.0.11'
-building path(s) `/nix/store/myy0y59q3ig70dgq37jqwg1j0rsapzsl-user-environment'
-collision between `/nix/store/...-firefox-2.0.0.11/bin/firefox'
- and `/nix/store/...-firefox-2.0.0.9/bin/firefox'.
-(i.e., can’t have two active at the same time)
-
-$ nix-env --set-flag active false firefox
-setting flag on `firefox-2.0.0.9'
-
-$ nix-env --preserve-installed --install firefox-2.0.0.11
-installing `firefox-2.0.0.11'
-
-$ nix-env --query
-firefox-2.0.0.11 (the enabled one)
-firefox-2.0.0.9 (the disabled one)
-```
-
-To make files from `binutils` take precedence over files from `gcc`:
-
-```console
-$ nix-env --set-flag priority 5 binutils
-$ nix-env --set-flag priority 10 gcc
-```
diff --git a/doc/manual/src/command-ref/nix-env/set.md b/doc/manual/src/command-ref/nix-env/set.md
deleted file mode 100644
index dc2765217..000000000
--- a/doc/manual/src/command-ref/nix-env/set.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# Name
-
-`nix-env --set` - set profile to contain a specified derivation
-
-## Synopsis
-
-`nix-env` `--set` *drvname*
-
-## Description
-
-The `--set` operation modifies the current generation of a profile so
-that it contains exactly the specified derivation, and nothing else.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-## Examples
-
-The following updates a profile such that its current generation will
-contain just Firefox:
-
-```console
-$ nix-env --profile /nix/var/nix/profiles/browser --set firefox
-```
diff --git a/doc/manual/src/command-ref/nix-env/switch-generation.md b/doc/manual/src/command-ref/nix-env/switch-generation.md
deleted file mode 100644
index d211c5f85..000000000
--- a/doc/manual/src/command-ref/nix-env/switch-generation.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Name
-
-`nix-env --switch-generation` - set user environment to given profile generation
-
-# Synopsis
-
-`nix-env` {`--switch-generation` | `-G`} *generation*
-
-# Description
-
-This operation makes generation number *generation* the current
-generation of the active profile. That is, if the `profile` is the path
-to the active profile, then the symlink `profile` is made to point to
-`profile-generation-link`, which is in turn a symlink to the actual user
-environment in the Nix store.
-
-Switching will fail if the specified generation does not exist.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-```console
-$ nix-env --switch-generation 42
-switching from generation 50 to 42
-```
diff --git a/doc/manual/src/command-ref/nix-env/switch-profile.md b/doc/manual/src/command-ref/nix-env/switch-profile.md
deleted file mode 100644
index 5ae2fdced..000000000
--- a/doc/manual/src/command-ref/nix-env/switch-profile.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# Name
-
-`nix-env --switch-profile` - set user environment to given profile
-
-# Synopsis
-
-`nix-env` {`--switch-profile` | `-S`} *path*
-
-# Description
-
-This operation makes *path* the current profile for the user. That is,
-the symlink `~/.nix-profile` is made to point to *path*.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-```console
-$ nix-env --switch-profile ~/my-profile
-```
diff --git a/doc/manual/src/command-ref/nix-env/uninstall.md b/doc/manual/src/command-ref/nix-env/uninstall.md
deleted file mode 100644
index 734cc7675..000000000
--- a/doc/manual/src/command-ref/nix-env/uninstall.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# Name
-
-`nix-env --uninstall` - remove packages from user environment
-
-# Synopsis
-
-`nix-env` {`--uninstall` | `-e`} *drvnames…*
-
-# Description
-
-The uninstall operation creates a new user environment, based on the
-current generation of the active profile, from which the store paths
-designated by the symbolic names *drvnames* are removed.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-```console
-$ nix-env --uninstall gcc
-$ nix-env --uninstall '.*' (remove everything)
-```
diff --git a/doc/manual/src/command-ref/nix-env/upgrade.md b/doc/manual/src/command-ref/nix-env/upgrade.md
deleted file mode 100644
index 11e0eddbe..000000000
--- a/doc/manual/src/command-ref/nix-env/upgrade.md
+++ /dev/null
@@ -1,140 +0,0 @@
-# Name
-
-`nix-env --upgrade` - upgrade packages in user environment
-
-# Synopsis
-
-`nix-env` {`--upgrade` | `-u`} *args*
- [`--lt` | `--leq` | `--eq` | `--always`]
- [{`--prebuilt-only` | `-b`}]
- [{`--attr` | `-A`}]
- [`--from-expression`] [`-E`]
- [`--from-profile` *path*]
- [`--preserve-installed` | `-P`]
-
-# Description
-
-The upgrade operation creates a new user environment, based on the
-current generation of the active profile, in which all store paths are
-replaced for which there are newer versions in the set of paths
-described by *args*. Paths for which there are no newer versions are
-left untouched; this is not an error. It is also not an error if an
-element of *args* matches no installed derivations.
-
-For a description of how *args* is mapped to a set of store paths, see
-[`--install`](#operation---install). If *args* describes multiple
-store paths with the same symbolic name, only the one with the highest
-version is installed.
-
-# Flags
-
- - `--lt`\
- Only upgrade a derivation to newer versions. This is the default.
-
- - `--leq`\
- In addition to upgrading to newer versions, also “upgrade” to
- derivations that have the same version. Version are not a unique
- identification of a derivation, so there may be many derivations
- that have the same version. This flag may be useful to force
- “synchronisation” between the installed and available derivations.
-
- - `--eq`\
- *Only* “upgrade” to derivations that have the same version. This may
- not seem very useful, but it actually is, e.g., when there is a new
- release of Nixpkgs and you want to replace installed applications
- with the same versions built against newer dependencies (to reduce
- the number of dependencies floating around on your system).
-
- - `--always`\
- In addition to upgrading to newer versions, also “upgrade” to
- derivations that have the same or a lower version. I.e., derivations
- may actually be downgraded depending on what is available in the
- active Nix expression.
-
- - `--prebuilt-only` / `-b`\
- Use only derivations for which a substitute is registered, i.e.,
- there is a pre-built binary available that can be downloaded in lieu
- of building the derivation. Thus, no packages will be built from
- source.
-
- - `--preserve-installed` / `-P`\
- Do not remove derivations with a name matching one of the
- derivations being installed. Usually, trying to have two versions of
- the same package installed in the same generation of a profile will
- lead to an error in building the generation, due to file name
- clashes between the two versions. However, this is not the case for
- all packages.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ./env-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-```console
-$ nix-env --upgrade --attr nixpkgs.gcc
-upgrading `gcc-3.3.1' to `gcc-3.4'
-```
-
-When there are no updates available, nothing will happen:
-
-```console
-$ nix-env --upgrade --attr nixpkgs.pan
-```
-
-Using `-A` is preferred when possible, as it is faster and unambiguous but
-it is also possible to upgrade to a specific version by matching the derivation name:
-
-```console
-$ nix-env --upgrade gcc-3.3.2 --always
-upgrading `gcc-3.4' to `gcc-3.3.2'
-```
-
-To try to upgrade everything
-(matching packages based on the part of the derivation name without version):
-
-```console
-$ nix-env --upgrade
-upgrading `hello-2.1.2' to `hello-2.1.3'
-upgrading `mozilla-1.2' to `mozilla-1.4'
-```
-
-# Versions
-
-The upgrade operation determines whether a derivation `y` is an upgrade
-of a derivation `x` by looking at their respective `name` attributes.
-The names (e.g., `gcc-3.3.1` are split into two parts: the package name
-(`gcc`), and the version (`3.3.1`). The version part starts after the
-first dash not followed by a letter. `y` is considered an upgrade of `x`
-if their package names match, and the version of `y` is higher than that
-of `x`.
-
-The versions are compared by splitting them into contiguous components
-of numbers and letters. E.g., `3.3.1pre5` is split into `[3, 3, 1,
-"pre", 5]`. These lists are then compared lexicographically (from left
-to right). Corresponding components `a` and `b` are compared as follows.
-If they are both numbers, integer comparison is used. If `a` is an empty
-string and `b` is a number, `a` is considered less than `b`. The special
-string component `pre` (for *pre-release*) is considered to be less than
-other components. String components are considered less than number
-components. Otherwise, they are compared lexicographically (i.e., using
-case-sensitive string comparison).
-
-This is illustrated by the following examples:
-
- 1.0 < 2.3
- 2.1 < 2.3
- 2.3 = 2.3
- 2.5 > 2.3
- 3.1 > 2.3
- 2.3.1 > 2.3
- 2.3.1 > 2.3a
- 2.3pre1 < 2.3
- 2.3pre3 < 2.3pre12
- 2.3a < 2.3c
- 2.3pre1 < 2.3c
- 2.3pre1 < 2.3q
diff --git a/doc/manual/src/command-ref/nix-hash.md b/doc/manual/src/command-ref/nix-hash.md
deleted file mode 100644
index 37c8facec..000000000
--- a/doc/manual/src/command-ref/nix-hash.md
+++ /dev/null
@@ -1,138 +0,0 @@
-# Name
-
-`nix-hash` - compute the cryptographic hash of a path
-
-# Synopsis
-
-`nix-hash` [`--flat`] [`--base32`] [`--truncate`] [`--type` *hashAlgo*] *path…*
-
-`nix-hash` [`--to-base16`|`--to-base32`|`--to-base64`|`--to-sri`] [`--type` *hashAlgo*] *hash…*
-
-# Description
-
-The command `nix-hash` computes the cryptographic hash of the contents
-of each *path* and prints it on standard output. By default, it computes
-an MD5 hash, but other hash algorithms are available as well. The hash
-is printed in hexadecimal. To generate the same hash as
-`nix-prefetch-url` you have to specify multiple arguments, see below for
-an example.
-
-The hash is computed over a *serialisation* of each path: a dump of
-the file system tree rooted at the path. This allows directories and
-symlinks to be hashed as well as regular files. The dump is in the
-*NAR format* produced by [`nix-store
---dump`](@docroot@/command-ref/nix-store/dump.md). Thus, `nix-hash path`
-yields the same cryptographic hash as `nix-store --dump path |
-md5sum`.
-
-# Options
-
- - `--flat`\
- Print the cryptographic hash of the contents of each regular file
- *path*. That is, do not compute the hash over the dump of *path*.
- The result is identical to that produced by the GNU commands
- `md5sum` and `sha1sum`.
-
- - `--base16`\
- Print the hash in a hexadecimal representation (default).
-
- - `--base32`\
- Print the hash in a base-32 representation rather than hexadecimal.
- This base-32 representation is more compact and can be used in Nix
- expressions (such as in calls to `fetchurl`).
-
- - `--base64`\
- Similar to --base32, but print the hash in a base-64 representation,
- which is more compact than the base-32 one.
-
- - `--sri`\
- Print the hash in SRI format with base-64 encoding.
- The type of hash algorithm will be prepended to the hash string,
- followed by a hyphen (-) and the base-64 hash body.
-
- - `--truncate`\
- Truncate hashes longer than 160 bits (such as SHA-256) to 160 bits.
-
- - `--type` *hashAlgo*\
- Use the specified cryptographic hash algorithm, which can be one of
- `md5`, `sha1`, `sha256`, and `sha512`.
-
- - `--to-base16`\
- Don’t hash anything, but convert the base-32 hash representation
- *hash* to hexadecimal.
-
- - `--to-base32`\
- Don’t hash anything, but convert the hexadecimal hash representation
- *hash* to base-32.
-
- - `--to-base64`\
- Don’t hash anything, but convert the hexadecimal hash representation
- *hash* to base-64.
-
- - `--to-sri`\
- Don’t hash anything, but convert the hexadecimal hash representation
- *hash* to SRI.
-
-# Examples
-
-Computing the same hash as `nix-prefetch-url`:
-
-```console
-$ nix-prefetch-url file://<(echo test)
-1lkgqb6fclns49861dwk9rzb6xnfkxbpws74mxnx01z9qyv1pjpj
-$ nix-hash --type sha256 --flat --base32 <(echo test)
-1lkgqb6fclns49861dwk9rzb6xnfkxbpws74mxnx01z9qyv1pjpj
-```
-
-Computing hashes:
-
-```console
-$ mkdir test
-$ echo "hello" > test/world
-
-$ nix-hash test/ (MD5 hash; default)
-8179d3caeff1869b5ba1744e5a245c04
-
-$ nix-store --dump test/ | md5sum (for comparison)
-8179d3caeff1869b5ba1744e5a245c04 -
-
-$ nix-hash --type sha1 test/
-e4fd8ba5f7bbeaea5ace89fe10255536cd60dab6
-
-$ nix-hash --type sha1 --base16 test/
-e4fd8ba5f7bbeaea5ace89fe10255536cd60dab6
-
-$ nix-hash --type sha1 --base32 test/
-nvd61k9nalji1zl9rrdfmsmvyyjqpzg4
-
-$ nix-hash --type sha1 --base64 test/
-5P2Lpfe76upazon+ECVVNs1g2rY=
-
-$ nix-hash --type sha1 --sri test/
-sha1-5P2Lpfe76upazon+ECVVNs1g2rY=
-
-$ nix-hash --type sha256 --flat test/
-error: reading file `test/': Is a directory
-
-$ nix-hash --type sha256 --flat test/world
-5891b5b522d5df086d0ff0b110fbd9d21bb4fc7163af34d08286a2e846f6be03
-```
-
-Converting between hexadecimal, base-32, base-64, and SRI:
-
-```console
-$ nix-hash --type sha1 --to-base32 e4fd8ba5f7bbeaea5ace89fe10255536cd60dab6
-nvd61k9nalji1zl9rrdfmsmvyyjqpzg4
-
-$ nix-hash --type sha1 --to-base16 nvd61k9nalji1zl9rrdfmsmvyyjqpzg4
-e4fd8ba5f7bbeaea5ace89fe10255536cd60dab6
-
-$ nix-hash --type sha1 --to-base64 e4fd8ba5f7bbeaea5ace89fe10255536cd60dab6
-5P2Lpfe76upazon+ECVVNs1g2rY=
-
-$ nix-hash --type sha1 --to-sri nvd61k9nalji1zl9rrdfmsmvyyjqpzg4
-sha1-5P2Lpfe76upazon+ECVVNs1g2rY=
-
-$ nix-hash --to-base16 sha1-5P2Lpfe76upazon+ECVVNs1g2rY=
-e4fd8ba5f7bbeaea5ace89fe10255536cd60dab6
-```
diff --git a/doc/manual/src/command-ref/nix-instantiate.md b/doc/manual/src/command-ref/nix-instantiate.md
deleted file mode 100644
index 479c9abcf..000000000
--- a/doc/manual/src/command-ref/nix-instantiate.md
+++ /dev/null
@@ -1,194 +0,0 @@
-# Name
-
-`nix-instantiate` - instantiate store derivations from Nix expressions
-
-# Synopsis
-
-`nix-instantiate`
- [`--parse` | `--eval` [`--strict`] [`--json`] [`--xml`] ]
- [`--read-write-mode`]
- [`--arg` *name* *value*]
- [{`--attr`| `-A`} *attrPath*]
- [`--add-root` *path*]
- [`--expr` | `-E`]
- *files…*
-
-`nix-instantiate` `--find-file` *files…*
-
-# Description
-
-The command `nix-instantiate` produces [store derivation]s from (high-level) Nix expressions.
-It evaluates the Nix expressions in each of *files* (which defaults to
-*./default.nix*). Each top-level expression should evaluate to a
-derivation, a list of derivations, or a set of derivations. The paths
-of the resulting store derivations are printed on standard output.
-
-[store derivation]: ../glossary.md#gloss-store-derivation
-
-If *files* is the character `-`, then a Nix expression will be read from
-standard input.
-
-# Options
-
- - `--add-root` *path*\
- See the [corresponding option](nix-store.md) in `nix-store`.
-
- - `--parse`\
- Just parse the input files, and print their abstract syntax trees on
- standard output as a Nix expression.
-
- - `--eval`\
- Just parse and evaluate the input files, and print the resulting
- values on standard output. No instantiation of store derivations
- takes place.
-
- > **Warning**
- >
- > This option produces output which can be parsed as a Nix expression which
- > will produce a different result than the input expression when evaluated.
- > For example, these two Nix expressions print the same result despite
- > having different meaning:
- >
- > ```console
- > $ nix-instantiate --eval --expr '{ a = {}; }'
- > { a = ; }
- > $ nix-instantiate --eval --expr '{ a = ; }'
- > { a = ; }
- > ```
- >
- > For human-readable output, `nix eval` (experimental) is more informative:
- >
- > ```console
- > $ nix-instantiate --eval --expr 'a: a'
- >
- > $ nix eval --expr 'a: a'
- > «lambda @ «string»:1:1»
- > ```
- >
- > For machine-readable output, the `--xml` option produces unambiguous
- > output:
- >
- > ```console
- > $ nix-instantiate --eval --xml --expr '{ foo = ; }'
- >
- >
- >
- >
- >
- >
- >
- > ```
-
- - `--find-file`\
- Look up the given files in Nix’s search path (as specified by the
- `NIX_PATH` environment variable). If found, print the corresponding
- absolute paths on standard output. For instance, if `NIX_PATH` is
- `nixpkgs=/home/alice/nixpkgs`, then `nix-instantiate --find-file
- nixpkgs/default.nix` will print `/home/alice/nixpkgs/default.nix`.
-
- - `--strict`\
- When used with `--eval`, recursively evaluate list elements and
- attributes. Normally, such sub-expressions are left unevaluated
- (since the Nix language is lazy).
-
- > **Warning**
- >
- > This option can cause non-termination, because lazy data
- > structures can be infinitely large.
-
- - `--json`\
- When used with `--eval`, print the resulting value as an JSON
- representation of the abstract syntax tree rather than as a Nix expression.
-
- - `--xml`\
- When used with `--eval`, print the resulting value as an XML
- representation of the abstract syntax tree rather than as a Nix expression.
- The schema is the same as that used by the [`toXML`
- built-in](../language/builtins.md).
-
- - `--read-write-mode`\
- When used with `--eval`, perform evaluation in read/write mode so
- nix language features that require it will still work (at the cost
- of needing to do instantiation of every evaluated derivation). If
- this option is not enabled, there may be uninstantiated store paths
- in the final output.
-
-{{#include ./opt-common.md}}
-
-{{#include ./env-common.md}}
-
-# Examples
-
-Instantiate [store derivation]s from a Nix expression, and build them using `nix-store`:
-
-```console
-$ nix-instantiate test.nix (instantiate)
-/nix/store/cigxbmvy6dzix98dxxh9b6shg7ar5bvs-perl-BerkeleyDB-0.26.drv
-
-$ nix-store --realise $(nix-instantiate test.nix) (build)
-...
-/nix/store/qhqk4n8ci095g3sdp93x7rgwyh9rdvgk-perl-BerkeleyDB-0.26 (output path)
-
-$ ls -l /nix/store/qhqk4n8ci095g3sdp93x7rgwyh9rdvgk-perl-BerkeleyDB-0.26
-dr-xr-xr-x 2 eelco users 4096 1970-01-01 01:00 lib
-...
-```
-
-You can also give a Nix expression on the command line:
-
-```console
-$ nix-instantiate --expr 'with import { }; hello'
-/nix/store/j8s4zyv75a724q38cb0r87rlczaiag4y-hello-2.8.drv
-```
-
-This is equivalent to:
-
-```console
-$ nix-instantiate '' --attr hello
-```
-
-Parsing and evaluating Nix expressions:
-
-```console
-$ nix-instantiate --parse --expr '1 + 2'
-1 + 2
-```
-
-```console
-$ nix-instantiate --eval --expr '1 + 2'
-3
-```
-
-```console
-$ nix-instantiate --eval --xml --expr '1 + 2'
-
-
-
-```
-
-The difference between non-strict and strict evaluation:
-
-```console
-$ nix-instantiate --eval --xml --expr '{ x = {}; }'
-
-
-
-
-
-
-
-
-$ nix-instantiate --eval --xml --strict --expr '{ x = {}; }'
-
-
-
-
-
-
-
-
-
-```
diff --git a/doc/manual/src/command-ref/nix-prefetch-url.md b/doc/manual/src/command-ref/nix-prefetch-url.md
deleted file mode 100644
index 45ef01e02..000000000
--- a/doc/manual/src/command-ref/nix-prefetch-url.md
+++ /dev/null
@@ -1,81 +0,0 @@
-# Name
-
-`nix-prefetch-url` - copy a file from a URL into the store and print its hash
-
-# Synopsis
-
-`nix-prefetch-url` *url* [*hash*]
- [`--type` *hashAlgo*]
- [`--print-path`]
- [`--unpack`]
- [`--name` *name*]
-
-# Description
-
-The command `nix-prefetch-url` downloads the file referenced by the URL
-*url*, prints its cryptographic hash, and copies it into the Nix store.
-The file name in the store is `hash-baseName`, where *baseName* is
-everything following the final slash in *url*.
-
-This command is just a convenience for Nix expression writers. Often a
-Nix expression fetches some source distribution from the network using
-the `fetchurl` expression contained in Nixpkgs. However, `fetchurl`
-requires a cryptographic hash. If you don't know the hash, you would
-have to download the file first, and then `fetchurl` would download it
-again when you build your Nix expression. Since `fetchurl` uses the same
-name for the downloaded file as `nix-prefetch-url`, the redundant
-download can be avoided.
-
-If *hash* is specified, then a download is not performed if the Nix
-store already contains a file with the same hash and base name.
-Otherwise, the file is downloaded, and an error is signaled if the
-actual hash of the file does not match the specified hash.
-
-This command prints the hash on standard output.
-The hash is printed using base-32 unless `--type md5` is specified,
-in which case it's printed using base-16.
-Additionally, if the option `--print-path` is used,
-the path of the downloaded file in the Nix store is also printed.
-
-# Options
-
- - `--type` *hashAlgo*\
- Use the specified cryptographic hash algorithm,
- which can be one of `md5`, `sha1`, `sha256`, and `sha512`.
- The default is `sha256`.
-
- - `--print-path`\
- Print the store path of the downloaded file on standard output.
-
- - `--unpack`\
- Unpack the archive (which must be a tarball or zip file) and add the
- result to the Nix store. The resulting hash can be used with
- functions such as Nixpkgs’s `fetchzip` or `fetchFromGitHub`.
-
- - `--executable`\
- Set the executable bit on the downloaded file.
-
- - `--name` *name*\
- Override the name of the file in the Nix store. By default, this is
- `hash-basename`, where *basename* is the last component of *url*.
- Overriding the name is necessary when *basename* contains characters
- that are not allowed in Nix store paths.
-
-# Examples
-
-```console
-$ nix-prefetch-url ftp://ftp.gnu.org/pub/gnu/hello/hello-2.10.tar.gz
-0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i
-```
-
-```console
-$ nix-prefetch-url --print-path mirror://gnu/hello/hello-2.10.tar.gz
-0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i
-/nix/store/3x7dwzq014bblazs7kq20p9hyzz0qh8g-hello-2.10.tar.gz
-```
-
-```console
-$ nix-prefetch-url --unpack --print-path https://github.com/NixOS/patchelf/archive/0.8.tar.gz
-079agjlv0hrv7fxnx9ngipx14gyncbkllxrp9cccnh3a50fxcmy7
-/nix/store/19zrmhm3m40xxaw81c8cqm6aljgrnwj2-0.8.tar.gz
-```
diff --git a/doc/manual/src/command-ref/nix-shell.md b/doc/manual/src/command-ref/nix-shell.md
deleted file mode 100644
index 1eaf3c36a..000000000
--- a/doc/manual/src/command-ref/nix-shell.md
+++ /dev/null
@@ -1,291 +0,0 @@
-# Name
-
-`nix-shell` - start an interactive shell based on a Nix expression
-
-# Synopsis
-
-`nix-shell`
- [`--arg` *name* *value*]
- [`--argstr` *name* *value*]
- [{`--attr` | `-A`} *attrPath*]
- [`--command` *cmd*]
- [`--run` *cmd*]
- [`--exclude` *regexp*]
- [`--pure`]
- [`--keep` *name*]
- {{`--packages` | `-p`} {*packages* | *expressions*} … | [*path*]}
-
-# Disambiguation
-
-This man page describes the command `nix-shell`, which is distinct from `nix
-shell`. For documentation on the latter, run `nix shell --help` or see `man
-nix3-shell`.
-
-# Description
-
-The command `nix-shell` will build the dependencies of the specified
-derivation, but not the derivation itself. It will then start an
-interactive shell in which all environment variables defined by the
-derivation *path* have been set to their corresponding values, and the
-script `$stdenv/setup` has been sourced. This is useful for reproducing
-the environment of a derivation for development.
-
-If *path* is not given, `nix-shell` defaults to `shell.nix` if it
-exists, and `default.nix` otherwise.
-
-If *path* starts with `http://` or `https://`, it is interpreted as the
-URL of a tarball that will be downloaded and unpacked to a temporary
-location. The tarball must include a single top-level directory
-containing at least a file named `default.nix`.
-
-If the derivation defines the variable `shellHook`, it will be run
-after `$stdenv/setup` has been sourced. Since this hook is not executed
-by regular Nix builds, it allows you to perform initialisation specific
-to `nix-shell`. For example, the derivation attribute
-
-```nix
-shellHook =
- ''
- echo "Hello shell"
- export SOME_API_TOKEN="$(cat ~/.config/some-app/api-token)"
- '';
-```
-
-will cause `nix-shell` to print `Hello shell` and set the `SOME_API_TOKEN`
-environment variable to a user-configured value.
-
-# Options
-
-All options not listed here are passed to `nix-store
---realise`, except for `--arg` and `--attr` / `-A` which are passed to
-`nix-instantiate`.
-
- - `--command` *cmd*\
- In the environment of the derivation, run the shell command *cmd*.
- This command is executed in an interactive shell. (Use `--run` to
- use a non-interactive shell instead.) However, a call to `exit` is
- implicitly added to the command, so the shell will exit after
- running the command. To prevent this, add `return` at the end;
- e.g. `--command "echo Hello; return"` will print `Hello` and then
- drop you into the interactive shell. This can be useful for doing
- any additional initialisation.
-
- - `--run` *cmd*\
- Like `--command`, but executes the command in a non-interactive
- shell. This means (among other things) that if you hit Ctrl-C while
- the command is running, the shell exits.
-
- - `--exclude` *regexp*\
- Do not build any dependencies whose store path matches the regular
- expression *regexp*. This option may be specified multiple times.
-
- - `--pure`\
- If this flag is specified, the environment is almost entirely
- cleared before the interactive shell is started, so you get an
- environment that more closely corresponds to the “real” Nix build. A
- few variables, in particular `HOME`, `USER` and `DISPLAY`, are
- retained.
-
- - `--packages` / `-p` *packages*…\
- Set up an environment in which the specified packages are present.
- The command line arguments are interpreted as attribute names inside
- the Nix Packages collection. Thus, `nix-shell --packages libjpeg openjdk`
- will start a shell in which the packages denoted by the attribute
- names `libjpeg` and `openjdk` are present.
-
- - `-i` *interpreter*\
- The chained script interpreter to be invoked by `nix-shell`. Only
- applicable in `#!`-scripts (described below).
-
- - `--keep` *name*\
- When a `--pure` shell is started, keep the listed environment
- variables.
-
-{{#include ./opt-common.md}}
-
-# Environment variables
-
- - `NIX_BUILD_SHELL`\
- Shell used to start the interactive environment. Defaults to the
- `bash` found in ``, falling back to the `bash` found in
- `PATH` if not found.
-
-{{#include ./env-common.md}}
-
-# Examples
-
-To build the dependencies of the package Pan, and start an interactive
-shell in which to build it:
-
-```console
-$ nix-shell '' --attr pan
-[nix-shell]$ eval ${unpackPhase:-unpackPhase}
-[nix-shell]$ cd $sourceRoot
-[nix-shell]$ eval ${patchPhase:-patchPhase}
-[nix-shell]$ eval ${configurePhase:-configurePhase}
-[nix-shell]$ eval ${buildPhase:-buildPhase}
-[nix-shell]$ ./pan/gui/pan
-```
-
-The reason we use form `eval ${configurePhase:-configurePhase}` here is because
-those packages that override these phases do so by exporting the overridden
-values in the environment variable of the same name.
-Here bash is being told to either evaluate the contents of 'configurePhase',
-if it exists as a variable, otherwise evaluate the configurePhase function.
-
-To clear the environment first, and do some additional automatic
-initialisation of the interactive shell:
-
-```console
-$ nix-shell '' --attr pan --pure \
- --command 'export NIX_DEBUG=1; export NIX_CORES=8; return'
-```
-
-Nix expressions can also be given on the command line using the `-E` and
-`-p` flags. For instance, the following starts a shell containing the
-packages `sqlite` and `libX11`:
-
-```console
-$ nix-shell --expr 'with import { }; runCommand "dummy" { buildInputs = [ sqlite xorg.libX11 ]; } ""'
-```
-
-A shorter way to do the same is:
-
-```console
-$ nix-shell --packages sqlite xorg.libX11
-[nix-shell]$ echo $NIX_LDFLAGS
-… -L/nix/store/j1zg5v…-sqlite-3.8.0.2/lib -L/nix/store/0gmcz9…-libX11-1.6.1/lib …
-```
-
-Note that `-p` accepts multiple full nix expressions that are valid in
-the `buildInputs = [ ... ]` shown above, not only package names. So the
-following is also legal:
-
-```console
-$ nix-shell --packages sqlite 'git.override { withManual = false; }'
-```
-
-The `-p` flag looks up Nixpkgs in the Nix search path. You can override
-it by passing `-I` or setting `NIX_PATH`. For example, the following
-gives you a shell containing the Pan package from a specific revision of
-Nixpkgs:
-
-```console
-$ nix-shell --packages pan -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/8a3eea054838b55aca962c3fbde9c83c102b8bf2.tar.gz
-
-[nix-shell:~]$ pan --version
-Pan 0.139
-```
-
-# Use as a `#!`-interpreter
-
-You can use `nix-shell` as a script interpreter to allow scripts written
-in arbitrary languages to obtain their own dependencies via Nix. This is
-done by starting the script with the following lines:
-
-```bash
-#! /usr/bin/env nix-shell
-#! nix-shell -i real-interpreter --packages packages
-```
-
-where *real-interpreter* is the “real” script interpreter that will be
-invoked by `nix-shell` after it has obtained the dependencies and
-initialised the environment, and *packages* are the attribute names of
-the dependencies in Nixpkgs.
-
-The lines starting with `#! nix-shell` specify `nix-shell` options (see
-above). Note that you cannot write `#! /usr/bin/env nix-shell -i ...`
-because many operating systems only allow one argument in `#!` lines.
-
-For example, here is a Python script that depends on Python and the
-`prettytable` package:
-
-```python
-#! /usr/bin/env nix-shell
-#! nix-shell -i python --packages python pythonPackages.prettytable
-
-import prettytable
-
-# Print a simple table.
-t = prettytable.PrettyTable(["N", "N^2"])
-for n in range(1, 10): t.add_row([n, n * n])
-print t
-```
-
-Similarly, the following is a Perl script that specifies that it
-requires Perl and the `HTML::TokeParser::Simple` and `LWP` packages:
-
-```perl
-#! /usr/bin/env nix-shell
-#! nix-shell -i perl --packages perl perlPackages.HTMLTokeParserSimple perlPackages.LWP
-
-use HTML::TokeParser::Simple;
-
-# Fetch nixos.org and print all hrefs.
-my $p = HTML::TokeParser::Simple->new(url => 'http://nixos.org/');
-
-while (my $token = $p->get_tag("a")) {
- my $href = $token->get_attr("href");
- print "$href\n" if $href;
-}
-```
-
-Sometimes you need to pass a simple Nix expression to customize a
-package like Terraform:
-
-```bash
-#! /usr/bin/env nix-shell
-#! nix-shell -i bash --packages 'terraform.withPlugins (plugins: [ plugins.openstack ])'
-
-terraform apply
-```
-
-> **Note**
->
-> You must use single or double quotes (`'`, `"`) when passing a simple Nix expression
-> in a nix-shell shebang.
-
-Finally, using the merging of multiple nix-shell shebangs the following
-Haskell script uses a specific branch of Nixpkgs/NixOS (the 20.03 stable
-branch):
-
-```haskell
-#! /usr/bin/env nix-shell
-#! nix-shell -i runghc --packages 'haskellPackages.ghcWithPackages (ps: [ps.download-curl ps.tagsoup])'
-#! nix-shell -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/nixos-20.03.tar.gz
-
-import Network.Curl.Download
-import Text.HTML.TagSoup
-import Data.Either
-import Data.ByteString.Char8 (unpack)
-
--- Fetch nixos.org and print all hrefs.
-main = do
- resp <- openURI "https://nixos.org/"
- let tags = filter (isTagOpenName "a") $ parseTags $ unpack $ fromRight undefined resp
- let tags' = map (fromAttrib "href") tags
- mapM_ putStrLn $ filter (/= "") tags'
-```
-
-If you want to be even more precise, you can specify a specific revision
-of Nixpkgs:
-
- #! nix-shell -I nixpkgs=https://github.com/NixOS/nixpkgs/archive/0672315759b3e15e2121365f067c1c8c56bb4722.tar.gz
-
-The examples above all used `-p` to get dependencies from Nixpkgs. You
-can also use a Nix expression to build your own dependencies. For
-example, the Python example could have been written as:
-
-```python
-#! /usr/bin/env nix-shell
-#! nix-shell deps.nix -i python
-```
-
-where the file `deps.nix` in the same directory as the `#!`-script
-contains:
-
-```nix
-with import {};
-
-runCommand "dummy" { buildInputs = [ python pythonPackages.prettytable ]; } ""
-```
diff --git a/doc/manual/src/command-ref/nix-store.md b/doc/manual/src/command-ref/nix-store.md
deleted file mode 100644
index c7c5fdd2f..000000000
--- a/doc/manual/src/command-ref/nix-store.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# Name
-
-`nix-store` - manipulate or query the Nix store
-
-# Synopsis
-
-`nix-store` *operation* [*options…*] [*arguments…*]
- [`--option` *name* *value*]
- [`--add-root` *path*]
-
-# Description
-
-The command `nix-store` performs primitive operations on the Nix store.
-You generally do not need to run this command manually.
-
-`nix-store` takes exactly one *operation* flag which indicates the subcommand to be performed. The following operations are available:
-
-- [`--realise`](./nix-store/realise.md)
-- [`--serve`](./nix-store/serve.md)
-- [`--gc`](./nix-store/gc.md)
-- [`--delete`](./nix-store/delete.md)
-- [`--query`](./nix-store/query.md)
-- [`--add`](./nix-store/add.md)
-- [`--add-fixed`](./nix-store/add-fixed.md)
-- [`--verify`](./nix-store/verify.md)
-- [`--verify-path`](./nix-store/verify-path.md)
-- [`--repair-path`](./nix-store/repair-path.md)
-- [`--dump`](./nix-store/dump.md)
-- [`--restore`](./nix-store/restore.md)
-- [`--export`](./nix-store/export.md)
-- [`--import`](./nix-store/import.md)
-- [`--optimise`](./nix-store/optimise.md)
-- [`--read-log`](./nix-store/read-log.md)
-- [`--dump-db`](./nix-store/dump-db.md)
-- [`--load-db`](./nix-store/load-db.md)
-- [`--print-env`](./nix-store/print-env.md)
-- [`--generate-binary-cache-key`](./nix-store/generate-binary-cache-key.md)
-
-These pages can be viewed offline:
-
-- `man nix-store-`.
-
- Example: `man nix-store-realise`
-
-- `nix-store --help --`
-
- Example: `nix-store --help --realise`
diff --git a/doc/manual/src/command-ref/nix-store/add-fixed.md b/doc/manual/src/command-ref/nix-store/add-fixed.md
deleted file mode 100644
index 3f02e3155..000000000
--- a/doc/manual/src/command-ref/nix-store/add-fixed.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Name
-
-`nix-store --add-fixed` - add paths to store using given hashing algorithm
-
-## Synopsis
-
-`nix-store` `--add-fixed` [`--recursive`] *algorithm* *paths…*
-
-## Description
-
-The operation `--add-fixed` adds the specified paths to the Nix store.
-Unlike `--add` paths are registered using the specified hashing
-algorithm, resulting in the same output path as a fixed-output
-derivation. This can be used for sources that are not available from a
-public url or broke since the download expression was written.
-
-This operation has the following options:
-
- - `--recursive`\
- Use recursive instead of flat hashing mode, used when adding
- directories to the store.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-## Example
-
-```console
-$ nix-store --add-fixed sha256 ./hello-2.10.tar.gz
-/nix/store/3x7dwzq014bblazs7kq20p9hyzz0qh8g-hello-2.10.tar.gz
-```
diff --git a/doc/manual/src/command-ref/nix-store/add.md b/doc/manual/src/command-ref/nix-store/add.md
deleted file mode 100644
index 87d504cd3..000000000
--- a/doc/manual/src/command-ref/nix-store/add.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# Name
-
-`nix-store --add` - add paths to Nix store
-
-# Synopsis
-
-`nix-store` `--add` *paths…*
-
-# Description
-
-The operation `--add` adds the specified paths to the Nix store. It
-prints the resulting paths in the Nix store on standard output.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-# Example
-
-```console
-$ nix-store --add ./foo.c
-/nix/store/m7lrha58ph6rcnv109yzx1nk1cj7k7zf-foo.c
-```
diff --git a/doc/manual/src/command-ref/nix-store/delete.md b/doc/manual/src/command-ref/nix-store/delete.md
deleted file mode 100644
index 550c5ea29..000000000
--- a/doc/manual/src/command-ref/nix-store/delete.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Name
-
-`nix-store --delete` - delete store paths
-
-# Synopsis
-
-`nix-store` `--delete` [`--ignore-liveness`] *paths…*
-
-# Description
-
-The operation `--delete` deletes the store paths *paths* from the Nix
-store, but only if it is safe to do so; that is, when the path is not
-reachable from a root of the garbage collector. This means that you can
-only delete paths that would also be deleted by `nix-store --gc`. Thus,
-`--delete` is a more targeted version of `--gc`.
-
-With the option `--ignore-liveness`, reachability from the roots is
-ignored. However, the path still won’t be deleted if there are other
-paths in the store that refer to it (i.e., depend on it).
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-# Example
-
-```console
-$ nix-store --delete /nix/store/zq0h41l75vlb4z45kzgjjmsjxvcv1qk7-mesa-6.4
-0 bytes freed (0.00 MiB)
-error: cannot delete path `/nix/store/zq0h41l75vlb4z45kzgjjmsjxvcv1qk7-mesa-6.4' since it is still alive
-```
diff --git a/doc/manual/src/command-ref/nix-store/dump-db.md b/doc/manual/src/command-ref/nix-store/dump-db.md
deleted file mode 100644
index b2c77ced0..000000000
--- a/doc/manual/src/command-ref/nix-store/dump-db.md
+++ /dev/null
@@ -1,26 +0,0 @@
-# Name
-
-`nix-store --dump-db` - export Nix database
-
-# Synopsis
-
-`nix-store` `--dump-db` [*paths…*]
-
-# Description
-
-The operation `--dump-db` writes a dump of the Nix database to standard
-output. It can be loaded into an empty Nix store using `--load-db`. This
-is useful for making backups and when migrating to different database
-schemas.
-
-By default, `--dump-db` will dump the entire Nix database. When one or
-more store paths is passed, only the subset of the Nix database for
-those store paths is dumped. As with `--export`, the user is responsible
-for passing all the store paths for a closure. See `--export` for an
-example.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
diff --git a/doc/manual/src/command-ref/nix-store/dump.md b/doc/manual/src/command-ref/nix-store/dump.md
deleted file mode 100644
index c2f3c42ef..000000000
--- a/doc/manual/src/command-ref/nix-store/dump.md
+++ /dev/null
@@ -1,40 +0,0 @@
-# Name
-
-`nix-store --dump` - write a single path to a Nix Archive
-
-## Synopsis
-
-`nix-store` `--dump` *path*
-
-## Description
-
-The operation `--dump` produces a NAR (Nix ARchive) file containing the
-contents of the file system tree rooted at *path*. The archive is
-written to standard output.
-
-A NAR archive is like a TAR or Zip archive, but it contains only the
-information that Nix considers important. For instance, timestamps are
-elided because all files in the Nix store have their timestamp set to 0
-anyway. Likewise, all permissions are left out except for the execute
-bit, because all files in the Nix store have 444 or 555 permission.
-
-Also, a NAR archive is *canonical*, meaning that “equal” paths always
-produce the same NAR archive. For instance, directory entries are
-always sorted so that the actual on-disk order doesn’t influence the
-result. This means that the cryptographic hash of a NAR dump of a
-path is usable as a fingerprint of the contents of the path. Indeed,
-the hashes of store paths stored in Nix’s database (see `nix-store --query
---hash`) are SHA-256 hashes of the NAR dump of each store path.
-
-NAR archives support filenames of unlimited length and 64-bit file
-sizes. They can contain regular files, directories, and symbolic links,
-but not other types of files (such as device nodes).
-
-A Nix archive can be unpacked using `nix-store
---restore`.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
diff --git a/doc/manual/src/command-ref/nix-store/export.md b/doc/manual/src/command-ref/nix-store/export.md
deleted file mode 100644
index 1bc46f53b..000000000
--- a/doc/manual/src/command-ref/nix-store/export.md
+++ /dev/null
@@ -1,41 +0,0 @@
-# Name
-
-`nix-store --export` - export store paths to a Nix Archive
-
-## Synopsis
-
-`nix-store` `--export` *paths…*
-
-## Description
-
-The operation `--export` writes a serialisation of the specified store
-paths to standard output in a format that can be imported into another
-Nix store with `nix-store --import`. This is like `nix-store
---dump`, except that the NAR archive produced by that command doesn’t
-contain the necessary meta-information to allow it to be imported into
-another Nix store (namely, the set of references of the path).
-
-This command does not produce a *closure* of the specified paths, so if
-a store path references other store paths that are missing in the target
-Nix store, the import will fail.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-To copy a whole closure, do something
-like:
-
-```console
-$ nix-store --export $(nix-store --query --requisites paths) > out
-```
-
-To import the whole closure again, run:
-
-```console
-$ nix-store --import < out
-```
diff --git a/doc/manual/src/command-ref/nix-store/gc.md b/doc/manual/src/command-ref/nix-store/gc.md
deleted file mode 100644
index 4d7b41db2..000000000
--- a/doc/manual/src/command-ref/nix-store/gc.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# Name
-
-`nix-store --gc` - run garbage collection
-
-# Synopsis
-
-`nix-store` `--gc` [`--print-roots` | `--print-live` | `--print-dead`] [`--max-freed` *bytes*]
-
-# Description
-
-Without additional flags, the operation `--gc` performs a garbage
-collection on the Nix store. That is, all paths in the Nix store not
-reachable via file system references from a set of “roots”, are deleted.
-
-The following suboperations may be specified:
-
- - `--print-roots`\
- This operation prints on standard output the set of roots used by
- the garbage collector.
-
- - `--print-live`\
- This operation prints on standard output the set of “live” store
- paths, which are all the store paths reachable from the roots. Live
- paths should never be deleted, since that would break consistency —
- it would become possible that applications are installed that
- reference things that are no longer present in the store.
-
- - `--print-dead`\
- This operation prints out on standard output the set of “dead” store
- paths, which is just the opposite of the set of live paths: any path
- in the store that is not live (with respect to the roots) is dead.
-
-By default, all unreachable paths are deleted. The following options
-control what gets deleted and in what order:
-
- - `--max-freed` *bytes*\
- Keep deleting paths until at least *bytes* bytes have been deleted,
- then stop. The argument *bytes* can be followed by the
- multiplicative suffix `K`, `M`, `G` or `T`, denoting KiB, MiB, GiB
- or TiB units.
-
-The behaviour of the collector is also influenced by the
-`keep-outputs` and `keep-derivations` settings in the Nix
-configuration file.
-
-By default, the collector prints the total number of freed bytes when it
-finishes (or when it is interrupted). With `--print-dead`, it prints the
-number of bytes that would be freed.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-To delete all unreachable paths, just do:
-
-```console
-$ nix-store --gc
-deleting `/nix/store/kq82idx6g0nyzsp2s14gfsc38npai7lf-cairo-1.0.4.tar.gz.drv'
-...
-8825586 bytes freed (8.42 MiB)
-```
-
-To delete at least 100 MiBs of unreachable paths:
-
-```console
-$ nix-store --gc --max-freed $((100 * 1024 * 1024))
-```
diff --git a/doc/manual/src/command-ref/nix-store/generate-binary-cache-key.md b/doc/manual/src/command-ref/nix-store/generate-binary-cache-key.md
deleted file mode 100644
index 8085d877b..000000000
--- a/doc/manual/src/command-ref/nix-store/generate-binary-cache-key.md
+++ /dev/null
@@ -1,29 +0,0 @@
-# Name
-
-`nix-store --generate-binary-cache-key` - generate key pair to use for a binary cache
-
-## Synopsis
-
-`nix-store` `--generate-binary-cache-key` *key-name* *secret-key-file* *public-key-file*
-
-## Description
-
-This command generates an [Ed25519 key pair](http://ed25519.cr.yp.to/)
-that can be used to create a signed binary cache. It takes three
-mandatory parameters:
-
-1. A key name, such as `cache.example.org-1`, that is used to look up
- keys on the client when it verifies signatures. It can be anything,
- but it’s suggested to use the host name of your cache (e.g.
- `cache.example.org`) with a suffix denoting the number of the key
- (to be incremented every time you need to revoke a key).
-
-2. The file name where the secret key is to be stored.
-
-3. The file name where the public key is to be stored.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
diff --git a/doc/manual/src/command-ref/nix-store/import.md b/doc/manual/src/command-ref/nix-store/import.md
deleted file mode 100644
index 2711316a7..000000000
--- a/doc/manual/src/command-ref/nix-store/import.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Name
-
-`nix-store --import` - import Nix Archive into the store
-
-# Synopsis
-
-`nix-store` `--import`
-
-# Description
-
-The operation `--import` reads a serialisation of a set of store paths
-produced by `nix-store --export` from standard input and adds those
-store paths to the Nix store. Paths that already exist in the Nix store
-are ignored. If a path refers to another path that doesn’t exist in the
-Nix store, the import fails.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
diff --git a/doc/manual/src/command-ref/nix-store/load-db.md b/doc/manual/src/command-ref/nix-store/load-db.md
deleted file mode 100644
index e2f438ed6..000000000
--- a/doc/manual/src/command-ref/nix-store/load-db.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Name
-
-`nix-store --load-db` - import Nix database
-
-# Synopsis
-
-`nix-store` `--load-db`
-
-# Description
-
-The operation `--load-db` reads a dump of the Nix database created by
-`--dump-db` from standard input and loads it into the Nix database.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
diff --git a/doc/manual/src/command-ref/nix-store/opt-common.md b/doc/manual/src/command-ref/nix-store/opt-common.md
deleted file mode 100644
index 04092ab45..000000000
--- a/doc/manual/src/command-ref/nix-store/opt-common.md
+++ /dev/null
@@ -1,35 +0,0 @@
-# Options
-
-The following options are allowed for all `nix-store` operations, but may not always have an effect.
-
-- [`--add-root`](#opt-add-root) *path*
-
- Causes the result of a realisation (`--realise` and
- `--force-realise`) to be registered as a root of the garbage
- collector. *path* will be created as a symlink to the resulting
- store path. In addition, a uniquely named symlink to *path* will
- be created in `/nix/var/nix/gcroots/auto/`. For instance,
-
- ```console
- $ nix-store --add-root /home/eelco/bla/result --realise ...
-
- $ ls -l /nix/var/nix/gcroots/auto
- lrwxrwxrwx 1 ... 2005-03-13 21:10 dn54lcypm8f8... -> /home/eelco/bla/result
-
- $ ls -l /home/eelco/bla/result
- lrwxrwxrwx 1 ... 2005-03-13 21:10 /home/eelco/bla/result -> /nix/store/1r11343n6qd4...-f-spot-0.0.10
- ```
-
- Thus, when `/home/eelco/bla/result` is removed, the GC root in the
- `auto` directory becomes a dangling symlink and will be ignored by
- the collector.
-
- > **Warning**
- >
- > Note that it is not possible to move or rename GC roots, since
- > the symlink in the `auto` directory will still point to the old
- > location.
-
- If there are multiple results, then multiple symlinks will be
- created by sequentially numbering symlinks beyond the first one
- (e.g., `foo`, `foo-2`, `foo-3`, and so on).
diff --git a/doc/manual/src/command-ref/nix-store/optimise.md b/doc/manual/src/command-ref/nix-store/optimise.md
deleted file mode 100644
index 2a0b583c8..000000000
--- a/doc/manual/src/command-ref/nix-store/optimise.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# Name
-
-`nix-store --optimise` - reduce disk space usage
-
-## Synopsis
-
-`nix-store` `--optimise`
-
-## Description
-
-The operation `--optimise` reduces Nix store disk space usage by finding
-identical files in the store and hard-linking them to each other. It
-typically reduces the size of the store by something like 25-35%. Only
-regular files and symlinks are hard-linked in this manner. Files are
-considered identical when they have the same NAR archive serialisation:
-that is, regular files must have the same contents and permission
-(executable or non-executable), and symlinks must have the same
-contents.
-
-After completion, or when the command is interrupted, a report on the
-achieved savings is printed on standard error.
-
-Use `-vv` or `-vvv` to get some progress indication.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-## Example
-
-```console
-$ nix-store --optimise
-hashing files in `/nix/store/qhqx7l2f1kmwihc9bnxs7rc159hsxnf3-gcc-4.1.1'
-...
-541838819 bytes (516.74 MiB) freed by hard-linking 54143 files;
-there are 114486 files with equal contents out of 215894 files in total
-```
diff --git a/doc/manual/src/command-ref/nix-store/print-env.md b/doc/manual/src/command-ref/nix-store/print-env.md
deleted file mode 100644
index a02fcb7a3..000000000
--- a/doc/manual/src/command-ref/nix-store/print-env.md
+++ /dev/null
@@ -1,30 +0,0 @@
-# Name
-
-`nix-store --print-env` - print the build environment of a derivation
-
-## Synopsis
-
-`nix-store` `--print-env` *drvpath*
-
-## Description
-
-The operation `--print-env` prints out the environment of a derivation
-in a format that can be evaluated by a shell. The command line arguments
-of the builder are placed in the variable `_args`.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-## Example
-
-```console
-$ nix-store --print-env $(nix-instantiate '' -A firefox)
-…
-export src; src='/nix/store/plpj7qrwcz94z2psh6fchsi7s8yihc7k-firefox-12.0.source.tar.bz2'
-export stdenv; stdenv='/nix/store/7c8asx3yfrg5dg1gzhzyq2236zfgibnn-stdenv'
-export system; system='x86_64-linux'
-export _args; _args='-e /nix/store/9krlzvny65gdc8s7kpb6lkx8cd02c25c-default-builder.sh'
-```
diff --git a/doc/manual/src/command-ref/nix-store/query.md b/doc/manual/src/command-ref/nix-store/query.md
deleted file mode 100644
index 37f1b63a9..000000000
--- a/doc/manual/src/command-ref/nix-store/query.md
+++ /dev/null
@@ -1,227 +0,0 @@
-# Name
-
-`nix-store --query` - display information about store paths
-
-# Synopsis
-
-`nix-store` {`--query` | `-q`}
- {`--outputs` | `--requisites` | `-R` | `--references` | `--referrers` |
- `--referrers-closure` | `--deriver` | `-d` | `--valid-derivers` |
- `--graph` | `--tree` | `--binding` *name* | `-b` *name* | `--hash` |
- `--size` | `--roots`}
- [`--use-output`] [`-u`] [`--force-realise`] [`-f`]
- *paths…*
-
-# Description
-
-The operation `--query` displays various bits of information about the
-store paths . The queries are described below. At most one query can be
-specified. The default query is `--outputs`.
-
-The paths *paths* may also be symlinks from outside of the Nix store, to
-the Nix store. In that case, the query is applied to the target of the
-symlink.
-
-# Common query options
-
- - `--use-output`; `-u`\
- For each argument to the query that is a [store derivation], apply the
- query to the output path of the derivation instead.
-
- - `--force-realise`; `-f`\
- Realise each argument to the query first (see [`nix-store --realise`](./realise.md)).
-
-[store derivation]: @docroot@/glossary.md#gloss-store-derivation
-
-# Queries
-
- - `--outputs`\
- Prints out the [output paths] of the store
- derivations *paths*. These are the paths that will be produced when
- the derivation is built.
-
- [output paths]: ../../glossary.md#gloss-output-path
-
- - `--requisites`; `-R`\
- Prints out the [closure] of the store path *paths*.
-
- [closure]: ../../glossary.md#gloss-closure
-
- This query has one option:
-
- - `--include-outputs`
- Also include the existing output paths of [store derivation]s,
- and their closures.
-
- This query can be used to implement various kinds of deployment. A
- *source deployment* is obtained by distributing the closure of a
- store derivation. A *binary deployment* is obtained by distributing
- the closure of an output path. A *cache deployment* (combined
- source/binary deployment, including binaries of build-time-only
- dependencies) is obtained by distributing the closure of a store
- derivation and specifying the option `--include-outputs`.
-
- - `--references`\
- Prints the set of [references] of the store paths
- *paths*, that is, their immediate dependencies. (For *all*
- dependencies, use `--requisites`.)
-
- [references]: ../../glossary.md#gloss-reference
-
- - `--referrers`\
- Prints the set of *referrers* of the store paths *paths*, that is,
- the store paths currently existing in the Nix store that refer to
- one of *paths*. Note that contrary to the references, the set of
- referrers is not constant; it can change as store paths are added or
- removed.
-
- - `--referrers-closure`\
- Prints the closure of the set of store paths *paths* under the
- referrers relation; that is, all store paths that directly or
- indirectly refer to one of *paths*. These are all the path currently
- in the Nix store that are dependent on *paths*.
-
- - `--deriver`; `-d`\
- Prints the [deriver] that was used to build the store paths *paths*. If
- the path has no deriver (e.g., if it is a source file), or if the
- deriver is not known (e.g., in the case of a binary-only
- deployment), the string `unknown-deriver` is printed.
- The returned deriver is not guaranteed to exist in the local store, for
- example when *paths* were substituted from a binary cache.
- Use `--valid-derivers` instead to obtain valid paths only.
-
- [deriver]: ../../glossary.md#gloss-deriver
-
- - `--valid-derivers`\
- Prints a set of derivation files (`.drv`) which are supposed produce
- said paths when realized. Might print nothing, for example for source paths
- or paths subsituted from a binary cache.
-
- - `--graph`\
- Prints the references graph of the store paths *paths* in the format
- of the `dot` tool of AT\&T's [Graphviz
- package](http://www.graphviz.org/). This can be used to visualise
- dependency graphs. To obtain a build-time dependency graph, apply
- this to a store derivation. To obtain a runtime dependency graph,
- apply it to an output path.
-
- - `--tree`\
- Prints the references graph of the store paths *paths* as a nested
- ASCII tree. References are ordered by descending closure size; this
- tends to flatten the tree, making it more readable. The query only
- recurses into a store path when it is first encountered; this
- prevents a blowup of the tree representation of the graph.
-
- - `--graphml`\
- Prints the references graph of the store paths *paths* in the
- [GraphML](http://graphml.graphdrawing.org/) file format. This can be
- used to visualise dependency graphs. To obtain a build-time
- dependency graph, apply this to a [store derivation]. To obtain a
- runtime dependency graph, apply it to an output path.
-
- - `--binding` *name*; `-b` *name*\
- Prints the value of the attribute *name* (i.e., environment
- variable) of the [store derivation]s *paths*. It is an error for a
- derivation to not have the specified attribute.
-
- - `--hash`\
- Prints the SHA-256 hash of the contents of the store paths *paths*
- (that is, the hash of the output of `nix-store --dump` on the given
- paths). Since the hash is stored in the Nix database, this is a fast
- operation.
-
- - `--size`\
- Prints the size in bytes of the contents of the store paths *paths*
- — to be precise, the size of the output of `nix-store --dump` on
- the given paths. Note that the actual disk space required by the
- store paths may be higher, especially on filesystems with large
- cluster sizes.
-
- - `--roots`\
- Prints the garbage collector roots that point, directly or
- indirectly, at the store paths *paths*.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-Print the closure (runtime dependencies) of the `svn` program in the
-current user environment:
-
-```console
-$ nix-store --query --requisites $(which svn)
-/nix/store/5mbglq5ldqld8sj57273aljwkfvj22mc-subversion-1.1.4
-/nix/store/9lz9yc6zgmc0vlqmn2ipcpkjlmbi51vv-glibc-2.3.4
-...
-```
-
-Print the build-time dependencies of `svn`:
-
-```console
-$ nix-store --query --requisites $(nix-store --query --deriver $(which svn))
-/nix/store/02iizgn86m42q905rddvg4ja975bk2i4-grep-2.5.1.tar.bz2.drv
-/nix/store/07a2bzxmzwz5hp58nf03pahrv2ygwgs3-gcc-wrapper.sh
-/nix/store/0ma7c9wsbaxahwwl04gbw3fcd806ski4-glibc-2.3.4.drv
-... lots of other paths ...
-```
-
-The difference with the previous example is that we ask the closure of
-the derivation (`-qd`), not the closure of the output path that contains
-`svn`.
-
-Show the build-time dependencies as a tree:
-
-```console
-$ nix-store --query --tree $(nix-store --query --deriver $(which svn))
-/nix/store/7i5082kfb6yjbqdbiwdhhza0am2xvh6c-subversion-1.1.4.drv
-+---/nix/store/d8afh10z72n8l1cr5w42366abiblgn54-builder.sh
-+---/nix/store/fmzxmpjx2lh849ph0l36snfj9zdibw67-bash-3.0.drv
-| +---/nix/store/570hmhmx3v57605cqg9yfvvyh0nnb8k8-bash
-| +---/nix/store/p3srsbd8dx44v2pg6nbnszab5mcwx03v-builder.sh
-...
-```
-
-Show all paths that depend on the same OpenSSL library as `svn`:
-
-```console
-$ nix-store --query --referrers $(nix-store --query --binding openssl $(nix-store --query --deriver $(which svn)))
-/nix/store/23ny9l9wixx21632y2wi4p585qhva1q8-sylpheed-1.0.0
-/nix/store/5mbglq5ldqld8sj57273aljwkfvj22mc-subversion-1.1.4
-/nix/store/dpmvp969yhdqs7lm2r1a3gng7pyq6vy4-subversion-1.1.3
-/nix/store/l51240xqsgg8a7yrbqdx1rfzyv6l26fx-lynx-2.8.5
-```
-
-Show all paths that directly or indirectly depend on the Glibc (C
-library) used by `svn`:
-
-```console
-$ nix-store --query --referrers-closure $(ldd $(which svn) | grep /libc.so | awk '{print $3}')
-/nix/store/034a6h4vpz9kds5r6kzb9lhh81mscw43-libgnomeprintui-2.8.2
-/nix/store/15l3yi0d45prm7a82pcrknxdh6nzmxza-gawk-3.1.4
-...
-```
-
-Note that `ldd` is a command that prints out the dynamic libraries used
-by an ELF executable.
-
-Make a picture of the runtime dependency graph of the current user
-environment:
-
-```console
-$ nix-store --query --graph ~/.nix-profile | dot -Tps > graph.ps
-$ gv graph.ps
-```
-
-Show every garbage collector root that points to a store path that
-depends on `svn`:
-
-```console
-$ nix-store --query --roots $(which svn)
-/nix/var/nix/profiles/default-81-link
-/nix/var/nix/profiles/default-82-link
-/home/eelco/.local/state/nix/profiles/profile-97-link
-```
diff --git a/doc/manual/src/command-ref/nix-store/read-log.md b/doc/manual/src/command-ref/nix-store/read-log.md
deleted file mode 100644
index f68de4c8c..000000000
--- a/doc/manual/src/command-ref/nix-store/read-log.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# Name
-
-`nix-store --read-log` - print build log
-
-# Synopsis
-
-`nix-store` {`--read-log` | `-l`} *paths…*
-
-# Description
-
-The operation `--read-log` prints the build log of the specified store
-paths on standard output. The build log is whatever the builder of a
-derivation wrote to standard output and standard error. If a store path
-is not a derivation, the deriver of the store path is used.
-
-Build logs are kept in `/nix/var/log/nix/drvs`. However, there is no
-guarantee that a build log is available for any particular store path.
-For instance, if the path was downloaded as a pre-built binary through a
-substitute, then the log is unavailable.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-# Example
-
-```console
-$ nix-store --read-log $(which ktorrent)
-building /nix/store/dhc73pvzpnzxhdgpimsd9sw39di66ph1-ktorrent-2.2.1
-unpacking sources
-unpacking source archive /nix/store/p8n1jpqs27mgkjw07pb5269717nzf5f8-ktorrent-2.2.1.tar.gz
-ktorrent-2.2.1/
-ktorrent-2.2.1/NEWS
-...
-```
diff --git a/doc/manual/src/command-ref/nix-store/realise.md b/doc/manual/src/command-ref/nix-store/realise.md
deleted file mode 100644
index a421a4220..000000000
--- a/doc/manual/src/command-ref/nix-store/realise.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Name
-
-`nix-store --realise` - build or fetch store objects
-
-# Synopsis
-
-`nix-store` {`--realise` | `-r`} *paths…* [`--dry-run`]
-
-# Description
-
-
-Each of *paths* is processed as follows:
-
-- If the path leads to a [store derivation]:
- 1. If it is not [valid], substitute the store derivation file itself.
- 2. Realise its [output paths]:
- - Try to fetch from [substituters] the [store objects] associated with the output paths in the store derivation's [closure].
- - With [content-addressed derivations] (experimental): Determine the output paths to realise by querying content-addressed realisation entries in the [Nix database].
- - For any store paths that cannot be substituted, produce the required store objects. This involves first realising all outputs of the derivation's dependencies and then running the derivation's [`builder`](@docroot@/language/derivations.md#attr-builder) executable.
-- Otherwise, and if the path is not already valid: Try to fetch the associated [store objects] in the path's [closure] from [substituters].
-
-If no substitutes are available and no store derivation is given, realisation fails.
-
-[store paths]: @docroot@/glossary.md#gloss-store-path
-[valid]: @docroot@/glossary.md#gloss-validity
-[store derivation]: @docroot@/glossary.md#gloss-store-derivation
-[output paths]: @docroot@/glossary.md#gloss-output-path
-[store objects]: @docroot@/glossary.md#gloss-store-object
-[closure]: @docroot@/glossary.md#gloss-closure
-[substituters]: @docroot@/command-ref/conf-file.md#conf-substituters
-[content-addressed derivations]: @docroot@/contributing/experimental-features.md#xp-feature-ca-derivations
-[Nix database]: @docroot@/glossary.md#gloss-nix-database
-
-The resulting paths are printed on standard output.
-For non-derivation arguments, the argument itself is printed.
-
-{{#include ../status-build-failure.md}}
-
-# Options
-
- - `--dry-run`\
- Print on standard error a description of what packages would be
- built or downloaded, without actually performing the operation.
-
- - `--ignore-unknown`\
- If a non-derivation path does not have a substitute, then silently
- ignore it.
-
- - `--check`\
- This option allows you to check whether a derivation is
- deterministic. It rebuilds the specified derivation and checks
- whether the result is bitwise-identical with the existing outputs,
- printing an error if that’s not the case. The outputs of the
- specified derivation must already exist. When used with `-K`, if an
- output path is not identical to the corresponding output from the
- previous build, the new output path is left in
- `/nix/store/name.check.`
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-This operation is typically used to build [store derivation]s produced by
-[`nix-instantiate`](@docroot@/command-ref/nix-instantiate.md):
-
-```console
-$ nix-store --realise $(nix-instantiate ./test.nix)
-/nix/store/31axcgrlbfsxzmfff1gyj1bf62hvkby2-aterm-2.3.1
-```
-
-This is essentially what [`nix-build`](@docroot@/command-ref/nix-build.md) does.
-
-To test whether a previously-built derivation is deterministic:
-
-```console
-$ nix-build '' --attr hello --check -K
-```
-
-Use [`nix-store --read-log`](./read-log.md) to show the stderr and stdout of a build:
-
-```console
-$ nix-store --read-log $(nix-instantiate ./test.nix)
-```
diff --git a/doc/manual/src/command-ref/nix-store/repair-path.md b/doc/manual/src/command-ref/nix-store/repair-path.md
deleted file mode 100644
index 4e4b6a67c..000000000
--- a/doc/manual/src/command-ref/nix-store/repair-path.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Name
-
-`nix --repair-path` - re-download path from substituter
-
-# Synopsis
-
-`nix-store` `--repair-path` *paths…*
-
-# Description
-
-The operation `--repair-path` attempts to “repair” the specified paths
-by redownloading them using the available substituters. If no
-substitutes are available, then repair is not possible.
-
-> **Warning**
->
-> During repair, there is a very small time window during which the old
-> path (if it exists) is moved out of the way and replaced with the new
-> path. If repair is interrupted in between, then the system may be left
-> in a broken state (e.g., if the path contains a critical system
-> component like the GNU C Library).
-
-# Example
-
-```console
-$ nix-store --verify-path /nix/store/dj7a81wsm1ijwwpkks3725661h3263p5-glibc-2.13
-path `/nix/store/dj7a81wsm1ijwwpkks3725661h3263p5-glibc-2.13' was modified!
- expected hash `2db57715ae90b7e31ff1f2ecb8c12ec1cc43da920efcbe3b22763f36a1861588',
- got `481c5aa5483ebc97c20457bb8bca24deea56550d3985cda0027f67fe54b808e4'
-
-$ nix-store --repair-path /nix/store/dj7a81wsm1ijwwpkks3725661h3263p5-glibc-2.13
-fetching path `/nix/store/d7a81wsm1ijwwpkks3725661h3263p5-glibc-2.13'...
-…
-```
diff --git a/doc/manual/src/command-ref/nix-store/restore.md b/doc/manual/src/command-ref/nix-store/restore.md
deleted file mode 100644
index fcba43df4..000000000
--- a/doc/manual/src/command-ref/nix-store/restore.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Name
-
-`nix-store --restore` - extract a Nix archive
-
-## Synopsis
-
-`nix-store` `--restore` *path*
-
-## Description
-
-The operation `--restore` unpacks a NAR archive to *path*, which must
-not already exist. The archive is read from standard input.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
diff --git a/doc/manual/src/command-ref/nix-store/serve.md b/doc/manual/src/command-ref/nix-store/serve.md
deleted file mode 100644
index 3ef5a64e2..000000000
--- a/doc/manual/src/command-ref/nix-store/serve.md
+++ /dev/null
@@ -1,37 +0,0 @@
-# Name
-
-`nix-store --serve` - serve local Nix store over SSH
-
-# Synopsis
-
-`nix-store` `--serve` [`--write`]
-
-# Description
-
-The operation `--serve` provides access to the Nix store over stdin and
-stdout, and is intended to be used as a means of providing Nix store
-access to a restricted ssh user.
-
-The following flags are available:
-
- - `--write`\
- Allow the connected client to request the realization of
- derivations. In effect, this can be used to make the host act as a
- remote builder.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-# Examples
-
-To turn a host into a build server, the `authorized_keys` file can be
-used to provide build access to a given SSH public key:
-
-```console
-$ cat <>/root/.ssh/authorized_keys
-command="nice -n20 nix-store --serve --write" ssh-rsa AAAAB3NzaC1yc2EAAAA...
-EOF
-```
diff --git a/doc/manual/src/command-ref/nix-store/verify-path.md b/doc/manual/src/command-ref/nix-store/verify-path.md
deleted file mode 100644
index 77e8fb222..000000000
--- a/doc/manual/src/command-ref/nix-store/verify-path.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# Name
-
-`nix-store --verify-path` - check path contents against Nix database
-
-## Synopsis
-
-`nix-store` `--verify-path` *paths…*
-
-## Description
-
-The operation `--verify-path` compares the contents of the given store
-paths to their cryptographic hashes stored in Nix’s database. For every
-changed path, it prints a warning message. The exit status is 0 if no
-path has changed, and 1 otherwise.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
-
-## Example
-
-To verify the integrity of the `svn` command and all its dependencies:
-
-```console
-$ nix-store --verify-path $(nix-store --query --requisites $(which svn))
-```
diff --git a/doc/manual/src/command-ref/nix-store/verify.md b/doc/manual/src/command-ref/nix-store/verify.md
deleted file mode 100644
index 2695b3361..000000000
--- a/doc/manual/src/command-ref/nix-store/verify.md
+++ /dev/null
@@ -1,36 +0,0 @@
-# Name
-
-`nix-store --verify` - check Nix database for consistency
-
-# Synopsis
-
-`nix-store` `--verify` [`--check-contents`] [`--repair`]
-
-# Description
-
-The operation `--verify` verifies the internal consistency of the Nix
-database, and the consistency between the Nix database and the Nix
-store. Any inconsistencies encountered are automatically repaired.
-Inconsistencies are generally the result of the Nix store or database
-being modified by non-Nix tools, or of bugs in Nix itself.
-
-This operation has the following options:
-
- - `--check-contents`\
- Checks that the contents of every valid store path has not been
- altered by computing a SHA-256 hash of the contents and comparing it
- with the hash stored in the Nix database at build time. Paths that
- have been modified are printed out. For large stores,
- `--check-contents` is obviously quite slow.
-
- - `--repair`\
- If any valid path is missing from the store, or (if
- `--check-contents` is given) the contents of a valid path has been
- modified, then try to repair the path by redownloading it. See
- `nix-store --repair-path` for details.
-
-{{#include ./opt-common.md}}
-
-{{#include ../opt-common.md}}
-
-{{#include ../env-common.md}}
diff --git a/doc/manual/src/command-ref/opt-common-syn.md b/doc/manual/src/command-ref/opt-common-syn.md
deleted file mode 100644
index b66d318c2..000000000
--- a/doc/manual/src/command-ref/opt-common-syn.md
+++ /dev/null
@@ -1,57 +0,0 @@
-\--help
-
-\--version
-
-\--verbose
-
-\-v
-
-\--quiet
-
-\--log-format
-
-format
-
-\--no-build-output
-
-\-Q
-
-\--max-jobs
-
-\-j
-
-number
-
-\--cores
-
-number
-
-\--max-silent-time
-
-number
-
-\--timeout
-
-number
-
-\--keep-going
-
-\-k
-
-\--keep-failed
-
-\-K
-
-\--fallback
-
-\--readonly-mode
-
-\-I
-
-path
-
-\--option
-
-name
-
-value
diff --git a/doc/manual/src/command-ref/opt-common.md b/doc/manual/src/command-ref/opt-common.md
deleted file mode 100644
index cd289b7ea..000000000
--- a/doc/manual/src/command-ref/opt-common.md
+++ /dev/null
@@ -1,215 +0,0 @@
-# Common Options
-
-Most commands in Lix accept the following command-line options:
-
-- [`--help`](#opt-help)
-
- Prints out a summary of the command syntax and exits.
-
-- [`--version`](#opt-version)
-
- Prints out the Lix version number on standard output and exits.
-
-- [`--verbose`](#opt-verbose) / `-v`
-
- Increases the level of verbosity of diagnostic messages printed on standard error.
- For each Lix operation, the information printed on standard output is well-defined;
- any diagnostic information is printed on standard error, never on standard output.
-
- This option may be specified repeatedly.
- Currently, the following verbosity levels exist:
-
- - `0` “Errors only”
-
- Only print messages explaining why the Lix invocation failed.
-
- - `1` “Informational”
-
- Print *useful* messages about what Lix is doing.
- This is the default.
-
- - `2` “Talkative”
-
- Print more informational messages.
-
- - `3` “Chatty”
-
- Print even more informational messages.
-
- - `4` “Debug”
-
- Print debug information.
-
- - `5` “Vomit”
-
- Print vast amounts of debug information.
-
-- [`--quiet`](#opt-quiet)
-
- Decreases the level of verbosity of diagnostic messages printed on standard error.
- This is the inverse option to `-v` / `--verbose`.
-
- This option may be specified repeatedly.
- See the previous verbosity levels list.
-
-- [`--log-format`](#opt-log-format) *format*
-
- This option can be used to change the output of the log format, with *format* being one of:
-
- - `raw`
-
- This is the raw format, as outputted by nix-build.
-
- - `internal-json`
-
- Outputs the logs in a structured manner.
-
- > **Warning**
- >
- > While the schema itself is relatively stable, the format of
- > the error-messages (namely of the `msg`-field) can change
- > between releases.
-
- - `bar`
-
- Only display a progress bar during the builds.
-
- - `bar-with-logs`
-
- Display the raw logs, with the progress bar at the bottom.
-
-- [`--no-build-output`](#opt-no-build-output) / `-Q`
-
- By default, output written by builders to standard output and standard error is echoed to the Lix command's standard error.
- This option suppresses this behaviour.
- Note that the builder's standard output and error are always written to a log file in `prefix/nix/var/log/nix`.
-
-- [`--max-jobs`](#opt-max-jobs) / `-j` *number*
-
- Sets the maximum number of build jobs that Lix will perform in parallel to the specified number.
- Specify `auto` to use the number of CPUs in the system.
- The default is specified by the `max-jobs` configuration setting, which itself defaults to `1`.
- A higher value is useful on SMP systems or to exploit I/O latency.
-
- Setting it to `0` disallows building on the local machine, which is useful when you want builds to happen only on remote builders.
-
-- [`--cores`](#opt-cores)
-
- Sets the value of the `NIX_BUILD_CORES` environment variable in the invocation of builders.
- Builders can use this variable at their discretion to control the maximum amount of parallelism.
- For instance, in Nixpkgs, if the derivation attribute `enableParallelBuilding` is set to `true`, the builder passes the `-jN` flag to GNU Make.
- It defaults to the value of the `cores` configuration setting, if set, or `1` otherwise.
- The value `0` means that the builder should use all available CPU cores in the system.
-
-- [`--max-silent-time`](#opt-max-silent-time)
-
- Sets the maximum number of seconds that a builder can go without producing any data on standard output or standard error.
- The default is specified by the `max-silent-time` configuration setting.
- `0` means no time-out.
-
-- [`--timeout`](#opt-timeout)
-
- Sets the maximum number of seconds that a builder can run.
- The default is specified by the `timeout` configuration setting.
- `0` means no timeout.
-
-- [`--keep-going`](#opt-keep-going) / `-k`
-
- Keep going in case of failed builds, to the greatest extent possible.
- That is, if building an input of some derivation fails, Lix will still build the other inputs, but not the derivation itself.
- Without this option, Lix stops if any build fails (except for builds of substitutes), possibly killing builds in progress (in case of parallel or distributed builds).
-
-- [`--keep-failed`](#opt-keep-failed) / `-K`
-
- Specifies that in case of a build failure, the temporary directory (usually in `/tmp`) in which the build takes place should not be deleted.
- The path of the build directory is printed as an informational message.
-
-- [`--fallback`](#opt-fallback)
-
- Whenever Lix attempts to build a derivation for which substitutes are known for each output path, but realising the output paths through the substitutes fails, fall back on building the derivation.
-
- The most common scenario in which this is useful is when we have registered substitutes in order to perform binary distribution from, say, a network repository.
- If the repository is down, the realisation of the derivation will fail.
- When this option is specified, Lix will build the derivation instead.
- Thus, installation from binaries falls back on installation from source.
- This option is not the default since it is generally not desirable for a transient failure in obtaining the substitutes to lead to a full build from source (with the related consumption of resources).
-
-- [`--readonly-mode`](#opt-readonly-mode)
-
- When this option is used, no attempt is made to open the Lix database.
- Most Lix operations do need database access, so those operations will fail.
-
-
-
- FIXME(Lix): sometimes you want `--store dummy` instead, because this option sometimes doesn't work. Document why this is.
-
-
-
-- [`--arg`](#opt-arg) *name* *value*
-
- This option is accepted by `nix-env`, `nix-instantiate`, `nix-shell` and `nix-build`.
- When evaluating Nix expressions, the expression evaluator will automatically try to call functions that it encounters.
- It can automatically call functions for which every argument has a [default value](@docroot@/language/constructs.md#functions) (e.g., `{ argName ? defaultValue }: ...`).
-
- With `--arg`, you can also call functions that have arguments without a default value (or override a default value).
- That is, if the evaluator encounters a function with an argument named *name*, it will call it with value *value*.
-
- For instance, the top-level `default.nix` in Nixpkgs is actually a function:
-
- ```nix
- { # The system (e.g., `i686-linux') for which to build the packages.
- system ? builtins.currentSystem
- ...
- }: ...
- ```
-
- So if you call this Nix expression (e.g., when you do `nix-env --install --attr pkgname`), the function will be called automatically using the value [`builtins.currentSystem`](@docroot@/language/builtins.md) for the `system` argument.
- You can override this using `--arg`, e.g., `nix-env --install --attr pkgname --arg system \"i686-freebsd\"`.
- (Note that since the argument is a Nix string literal, you have to escape the quotes.)
-
-- [`--argstr`](#opt-argstr) *name* *value*
-
- This option is like `--arg`, only the value is not a Nix expression but a string.
- So instead of `--arg system \"i686-linux\"` (the outer quotes are to keep the shell happy) you can say `--argstr system i686-linux`.
-
-- [`--attr`](#opt-attr) / `-A` *attrPath*
-
- Select an attribute from the top-level Nix expression being evaluated.
- (`nix-env`, `nix-instantiate`, `nix-build` and `nix-shell` only.)
- The *attribute path* *attrPath* is a sequence of attribute names separated by dots.
- For instance, given a top-level Nix expression *e*, the attribute path `xorg.xorgserver` would cause the expression `e.xorg.xorgserver` to be used.
- See [`nix-env --install`](@docroot@/command-ref/nix-env/install.md) for some concrete examples.
-
- In addition to attribute names, you can also specify array indices.
- For instance, the attribute path `foo.3.bar` selects the `bar`
- attribute of the fourth element of the array in the `foo` attribute
- of the top-level expression.
-
-- [`--expr`](#opt-expr) / `-E`
-
- Interpret the command line arguments as a list of Nix expressions to be parsed and evaluated, rather than as a list of file names of Nix expressions.
- (`nix-instantiate`, `nix-build` and `nix-shell` only.)
-
- For `nix-shell`, this option is commonly used to give you a shell in which you can build the packages returned by the expression.
- If you want to get a shell which contain the *built* packages ready for use, give your expression to the `nix-shell --packages ` convenience flag instead.
-
-- [`-I`](#opt-I) *path*
-
- Add an entry to the [Nix expression search path](@docroot@/command-ref/conf-file.md#conf-nix-path).
- This option may be given multiple times.
- Paths added through `-I` take precedence over [`NIX_PATH`](@docroot@/command-ref/env-common.md#env-NIX_PATH).
-
-- [`--option`](#opt-option) *name* *value*
-
- Set the Lix configuration option *name* to *value*.
- This overrides settings in the Lix configuration file (see nix.conf(5)).
-
-- [`--repair`](#opt-repair)
-
- Fix corrupted or missing store paths by redownloading or rebuilding them.
- Note that this is slow because it requires computing a cryptographic hash of the contents of every path in the closure of the build.
- Also note the warning under `nix-store --repair-path`.
-
-> **Note**
->
-> See [`man nix.conf`](@docroot@/command-ref/conf-file.md#command-line-flags) for overriding configuration settings with command line flags.
diff --git a/doc/manual/src/command-ref/opt-inst-syn.md b/doc/manual/src/command-ref/opt-inst-syn.md
deleted file mode 100644
index 1703c40e3..000000000
--- a/doc/manual/src/command-ref/opt-inst-syn.md
+++ /dev/null
@@ -1,15 +0,0 @@
-\--prebuilt-only
-
-\-b
-
-\--attr
-
-\-A
-
-\--from-expression
-
-\-E
-
-\--from-profile
-
-path
diff --git a/doc/manual/src/command-ref/status-build-failure.md b/doc/manual/src/command-ref/status-build-failure.md
deleted file mode 100644
index 06114eb29..000000000
--- a/doc/manual/src/command-ref/status-build-failure.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Special exit codes for build failure
-
-1xx status codes are used when requested builds failed.
-The following codes are in use:
-
-- `100` Generic build failure
-
- The builder process returned with a non-zero exit code.
-
-- `101` Build timeout
-
- The build was aborted because it did not complete within the specified `timeout`.
-
-- `102` Hash mismatch
-
- The build output was rejected because it does not match the
- [`outputHash` attribute of the derivation](@docroot@/language/advanced-attributes.md).
-
-- `104` Not deterministic
-
- The build succeeded in check mode but the resulting output is not binary reproducible.
-
-With the `--keep-going` flag it's possible for multiple failures to occur.
-In this case the 1xx status codes are or combined using
-[bitwise OR](https://en.wikipedia.org/wiki/Bitwise_operation#OR).
-
-```
-0b1100100
- ^^^^
- |||`- timeout
- ||`-- output hash mismatch
- |`--- build failure
- `---- not deterministic
-```
diff --git a/doc/manual/src/command-ref/utilities.md b/doc/manual/src/command-ref/utilities.md
deleted file mode 100644
index 3ee09ea6c..000000000
--- a/doc/manual/src/command-ref/utilities.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# Utilities
-
-This section lists utilities that you can use when you work with Lix.
diff --git a/doc/manual/src/contributing/cli-guideline.md b/doc/manual/src/contributing/cli-guideline.md
deleted file mode 100644
index f170e5e8f..000000000
--- a/doc/manual/src/contributing/cli-guideline.md
+++ /dev/null
@@ -1,671 +0,0 @@
-# CLI guideline
-
-## Goals
-
-Purpose of this document is to provide a clear direction to **help design
-delightful command line** experience. This document contains guidelines to
-follow to ensure a consistent and approachable user experience.
-
-## Overview
-
-`nix` command provides a single entry to a number of sub-commands that help
-**developers and system administrators** in the life-cycle of a software
-project. We particularly need to pay special attention to help and assist new
-users of Lix.
-
-# Naming the `COMMANDS`
-
-Words matter. Naming is an important part of the usability. Users will be
-interacting with Lix on a regular basis so we should **name things for ease of
-understanding**.
-
-We recommend following the [Principle of Least
-Astonishment](https://en.wikipedia.org/wiki/Principle_of_least_astonishment).
-This means that you should **never use acronyms or abbreviations** unless they
-are commonly used in other tools (e.g. `nix init`). And if the command name is
-too long (> 10-12 characters) then shortening it makes sense (e.g.
-“prioritization” → “priority”).
-
-Commands should **follow a noun-verb dialogue**. Although noun-verb formatting
-seems backwards from a speaking perspective (i.e. `nix store copy` vs. `nix
-copy store`) it allows us to organize commands the same way users think about
-completing an action (the group first, then the command).
-
-## Naming rules
-
-Rules are there to guide you by limiting your options. But not everything can
-fit the rules all the time. In those cases document the exceptions in [Appendix
-1: Commands naming exceptions](#appendix-1-commands-naming-exceptions) and
-provide reason. The rules want to force a Nix developer to look, not just at
-the command at hand, but also the command in a full context alongside other
-`nix` commands.
-
-```shell
-$ nix [] [] []
-```
-
-- `GROUP`, `COMMAND`, `ARGUMENTS` and `OPTIONS` should be lowercase and in a
- singular form.
-- `GROUP` should be a **NOUN**.
-- `COMMAND` should be a **VERB**.
-- `ARGUMENTS` and `OPTIONS` are discussed in [*Input* section](#input).
-
-## Classification
-
-Some commands are more important, some less. While we want all of our commands
-to be perfect we can only spend limited amount of time testing and improving
-them.
-
-This classification tries to separate commands in 3 categories in terms of
-their importance in regards to the new users. Users who are likely to be
-impacted the most by bad user experience.
-
-- **Main commands**
-
- Commands used for our main use cases and most likely used by new users. We
- expect attention to details, such as:
-
- - Proper use of [colors](#colors), [emojis](#special-unicode-characters)
- and [aligning of text](#text-alignment).
- - [Autocomplete](#shell-completion) of options.
- - Show [next possible steps](#next-steps).
- - Showing some [“tips”](#educate-the-user) when running logs running tasks
- (eg. building / downloading) in order to teach users interesting bits of
- Nix ecosystem.
- - [Help pages](#help-is-essential) to be as good as we can write them
- pointing to external documentation and tutorials for more.
-
- Examples of such commands: `nix init`, `nix develop`, `nix build`, `nix run`,
- ...
-
-- **Infrequently used commands**
-
- From infrequently used commands we expect less attention to details, but
- still some:
-
- - Proper use of [colors](#colors), [emojis](#special-unicode-characters)
- and [aligning of text](#text-alignment).
- - [Autocomplete](#shell-completion) of options.
-
- Examples of such commands: `nix doctor`, `nix edit`, `nix eval`, ...
-
-- **Utility and scripting commands**
-
- Commands that expose certain internal functionality of `nix`, mostly used by
- other scripts.
-
- - [Autocomplete](#shell-completion) of options.
-
- Examples of such commands: `nix store copy`, `nix hash base16`, `nix store
- ping`, ...
-
-
-# Help is essential
-
-Help should be built into your command line so that new users can gradually
-discover new features when they need them.
-
-## Looking for help
-
-Since there is no standard way how user will look for help we rely on ways help
-is provided by commonly used tools. As a guide for this we took `git` and
-whenever in doubt look at it as a preferred direction.
-
-The rules are:
-
-- Help is shown by using `--help` or `help` command (eg `nix` `--``help` or
- `nix help`).
-- For non-COMMANDs (eg. `nix` `--``help` and `nix store` `--``help`) we **show
- a summary** of most common use cases. Summary is presented on the STDOUT
- without any use of PAGER.
-- For COMMANDs (eg. `nix init` `--``help` or `nix help init`) we display the
- man page of that command. By default the PAGER is used (as in `git`).
-- At the end of either summary or man page there should be an URL pointing to
- an online version of more detailed documentation.
-- The structure of summaries and man pages should be the same as in `git`.
-
-## Anticipate where help is needed
-
-Even better then requiring the user to search for help is to anticipate and
-predict when user might need it. Either because the lack of discoverability,
-typo in the input or simply taking the opportunity to teach the user of
-interesting - but less visible - details.
-
-### Shell completion
-
-This type of help is most common and almost expected by users. We need to
-**provide the best shell completion** for `bash`, `zsh` and `fish`.
-
-Completion needs to be **context aware**, this mean when a user types:
-
-```shell
-$ nix build n
-```
-
-we need to display a list of flakes starting with `n`.
-
-### Wrong input
-
-As we all know we humans make mistakes, all the time. When a typo - intentional
-or unintentional - is made, we should prompt for closest possible options or
-point to the documentation which would educate user to not make the same
-errors. Here are few examples:
-
-In first example we prompt the user for typing wrong command name:
-
-
-```shell
-$ nix int
-------------------------------------------------------------------------
- Error! Command `int` not found.
-------------------------------------------------------------------------
- Did you mean:
- |> nix init
- |> nix input
-```
-
-Sometimes users will make mistake either because of a typo or simply because of
-lack of discoverability. Our handling of this cases needs to be context
-sensitive.
-
-
-```shell
-$ nix init --template=template#pyton
-------------------------------------------------------------------------
- Error! Template `template#pyton` not found.
-------------------------------------------------------------------------
-Initializing Nix project at `/path/to/here`.
- Select a template for you new project:
- |> template#python
- template#python-pip
- template#python-poetry
-```
-
-### Next steps
-
-It can be invaluable to newcomers to show what a possible next steps and what
-is the usual development workflow with Lix. For example:
-
-
-```shell
-$ nix init --template=template#python
-Initializing project `template#python`
- in `/home/USER/dev/new-project`
-
- Next steps
- |> nix develop -- to enter development environment
- |> nix build -- to build your project
-```
-
-### Educate the user
-
-We should take any opportunity to **educate users**, but at the same time we
-must **be very very careful to not annoy users**. There is a thin line between
-being helpful and being annoying.
-
-An example of educating users might be to provide *Tips* in places where they
-are waiting.
-
-```shell
-$ nix build
- Started building my-project 1.2.3
- Downloaded python3.8-poetry 1.2.3 in 5.3 seconds
- Downloaded python3.8-requests 1.2.3 in 5.3 seconds
-------------------------------------------------------------------------
- Press `v` to increase logs verbosity
- |> `?` to see other options
-------------------------------------------------------------------------
- Learn something new with every build...
- |> See last logs of a build with `nix log --last` command.
-------------------------------------------------------------------------
- Evaluated my-project 1.2.3 in 14.43 seconds
-Downloading [12 / 200]
- |> firefox 1.2.3 [#########> ] 10Mb/s | 2min left
- Building [2 / 20]
- |> glibc 1.2.3 -> buildPhase:
-------------------------------------------------------------------------
-```
-
-Now **Learn** part of the output is where you educate users. You should only
-show it when you know that a build will take some time and not annoy users of
-the builds that take only few seconds.
-
-Every feature like this should go through an intensive review and testing to
-collect as much feedback as possible and to fine tune every little detail. If
-done right this can be an awesome features beginners and advance users will
-love, but if not done perfectly it will annoy users and leave bad impression.
-
-# Input
-
-Input to a command is provided via `ARGUMENTS` and `OPTIONS`.
-
-`ARGUMENTS` represent a required input for a function. When choosing to use
-`ARGUMENTS` over `OPTIONS` please be aware of the downsides that come with it:
-
-- User will need to remember the order of `ARGUMENTS`. This is not a problem if
- there is only one `ARGUMENT`.
-- With `OPTIONS` it is possible to provide much better auto completion.
-- With `OPTIONS` it is possible to provide much better error message.
-- Using `OPTIONS` it will mean there is a little bit more typing.
-
-We don’t discourage the use of `ARGUMENTS`, but simply want to make every
-developer consider the downsides and choose wisely.
-
-## Naming the `OPTIONS`
-
-The only naming convention - apart from the ones mentioned in Naming the
-`COMMANDS` section is how flags are named.
-
-Flags are a type of `OPTION` that represent an option that can be turned ON of
-OFF. We can say **flags are boolean type of** `**OPTION**`.
-
-Here are few examples of flag `OPTIONS`:
-
-- `--colors` vs. `--no-colors` (showing colors in the output)
-- `--emojis` vs. `--no-emojis` (showing emojis in the output)
-
-## Prompt when input not provided
-
-For *main commands* (as [per classification](#classification)) we want command
-to improve the discoverability of possible input. A new user will most likely
-not know which `ARGUMENTS` and `OPTIONS` are required or which values are
-possible for those options.
-
-In case the user does not provide the input or they provide wrong input,
-rather than show the error, prompt a user with an option to find and select
-correct input (see examples).
-
-Prompting is of course not required when TTY is not attached to STDIN. This
-would mean that scripts won't need to handle prompt, but rather handle errors.
-
-A place to use prompt and provide user with interactive select
-
-
-```shell
-$ nix init
-Initializing Nix project at `/path/to/here`.
- Select a template for you new project:
- |> py
- template#python-pip
- template#python-poetry
- [ Showing 2 templates from 1345 templates ]
-```
-
-Another great place to add prompts are **confirmation dialogues for dangerous
-actions**. For example when adding new substitutor via `OPTIONS` or via
-`flake.nix` we should prompt - for the first time - and let user review what is
-going to happen.
-
-
-```shell
-$ nix build --option substitutors https://cache.example.org
-------------------------------------------------------------------------
- Warning! A security related question needs to be answered.
-------------------------------------------------------------------------
- The following substitutors will be used to in `my-project`:
- - https://cache.example.org
-
- Do you allow `my-project` to use above mentioned substitutors?
- [y/N] |> y
-```
-
-# Output
-
-Terminal output can be quite limiting in many ways. Which should force us to
-think about the experience even more. As with every design the output is a
-compromise between being terse and being verbose, between showing help to
-beginners and annoying advance users. For this it is important that we know
-what are the priorities.
-
-Lix command line should be first and foremost written with beginners in mind.
-But users won't stay beginners for long and what was once useful might quickly
-become annoying. There is no golden rule that we can give in this guideline
-that would make it easier how to draw a line and find best compromise.
-
-What we would encourage is to **build prototypes**, do some **user testing**
-and collect **feedback**. Then repeat the cycle few times.
-
-First design the *happy path* and only after your iron it out, continue to work
-on **edge cases** (handling and displaying errors, changes of the output by
-certain `OPTIONS`, etc…)
-
-## Follow best practices
-
-Needless to say we Lix must be a good citizen and follow best practices in
-command line.
-
-In short: **STDOUT is for output, STDERR is for (human) messaging.**
-
-STDOUT and STDERR provide a way for you to output messages to the user while
-also allowing them to redirect content to a file. For example:
-
-```shell
-$ nix build > build.txt
-------------------------------------------------------------------------
- Error! Attribute `bin` missing at (1:94) from string.
-------------------------------------------------------------------------
-
- 1| with import { }; (pkgs.runCommandCC or pkgs.runCommand) "shell" { buildInputs = [ (surge.bin) ]; } ""
-```
-
-Because this warning is on STDERR, it doesn’t end up in the file.
-
-But not everything on STDERR is an error though. For example, you can run `nix
-build` and collect logs in a file while still seeing the progress.
-
-```
-$ nix build > build.txt
- Evaluated 1234 files in 1.2 seconds
- Downloaded python3.8-poetry 1.2.3 in 5.3 seconds
- Downloaded python3.8-requests 1.2.3 in 5.3 seconds
-------------------------------------------------------------------------
- Press `v` to increase logs verbosity
- |> `?` to see other options
-------------------------------------------------------------------------
- Learn something new with every build...
- |> See last logs of a build with `nix log --last` command.
-------------------------------------------------------------------------
- Evaluated my-project 1.2.3 in 14.43 seconds
-Downloading [12 / 200]
- |> firefox 1.2.3 [#########> ] 10Mb/s | 2min left
- Building [2 / 20]
- |> glibc 1.2.3 -> buildPhase:
-------------------------------------------------------------------------
-```
-
-## Errors (WIP)
-
-**TODO**: Once we have implementation for the *happy path* then we will think
-how to present errors.
-
-## Not only for humans
-
-Terse, machine-readable output formats can also be useful but shouldn’t get in
-the way of making beautiful CLI output. When needed, commands should offer a
-`--json` flag to allow users to easily parse and script the CLI.
-
-When TTY is not detected on STDOUT we should remove all design elements (no
-colors, no emojis and using ASCII instead of Unicode symbols). The same should
-happen when TTY is not detected on STDERR. We should not display progress /
-status section, but only print warnings and errors.
-
-## Returning future proof JSON
-
-The schema of JSON output should allow for backwards compatible extension. This section explains how to achieve this.
-
-Two definitions are helpful here, because while JSON only defines one "key-value"
-object type, we use it to cover two use cases:
-
- - **dictionary**: a map from names to value that all have the same type. In
- C++ this would be a `std::map` with string keys.
- - **record**: a fixed set of attributes each with their own type. In C++, this
- would be represented by a `struct`.
-
-It is best not to mix these use cases, as that may lead to incompatibilities when the schema changes. For example, adding a record field to a dictionary breaks consumers that assume all JSON object fields to have the same meaning and type.
-
-This leads to the following guidelines:
-
- - The top-level (root) value must be a record.
-
- Otherwise, one can not change the structure of a command's output.
-
- - The value of a dictionary item must be a record.
-
- Otherwise, the item type can not be extended.
-
- - List items should be records.
-
- Otherwise, one can not change the structure of the list items.
-
- If the order of the items does not matter, and each item has a unique key that is a string, consider representing the list as a dictionary instead. If the order of the items needs to be preserved, return a list of records.
-
- - Streaming JSON should return records.
-
- An example of a streaming JSON format is [JSON lines](https://jsonlines.org/), where each line represents a JSON value. These JSON values can be considered top-level values or list items, and they must be records.
-
-### Examples
-
-
-This is bad, because all keys must be assumed to be store implementations:
-
-```json
-{
- "local": { ... },
- "remote": { ... },
- "http": { ... }
-}
-```
-
-This is good, because the it is extensible at the root, and is somewhat self-documenting:
-
-```json
-{
- "storeTypes": { "local": { ... }, ... },
- "pluginSupport": true
-}
-```
-
-While the dictionary of store types seems like a very complete response at first, a use case may arise that warrants returning additional information.
-For example, the presence of plugin support may be crucial information for a client to proceed when their desired store type is missing.
-
-
-
-The following representation is bad because it is not extensible:
-
-```json
-{ "outputs": [ "out" "bin" ] }
-```
-
-However, simply converting everything to records is not enough, because the order of outputs must be preserved:
-
-```json
-{ "outputs": { "bin": {}, "out": {} } }
-```
-
-The first item is the default output. Deriving this information from the outputs ordering is not great, but this is how Lix currently happens to work.
-While it is possible for a JSON parser to preserve the order of fields, we can not rely on this capability to be present in all JSON libraries.
-
-This representation is extensible and preserves the ordering:
-
-```json
-{ "outputs": [ { "outputName": "out" }, { "outputName": "bin" } ] }
-```
-
-## Dialog with the user
-
-CLIs don't always make it clear when an action has taken place. For every
-action a user performs, your CLI should provide an equal and appropriate
-reaction, clearly highlighting the what just happened. For example:
-
-```shell
-$ nix build
- Downloaded python3.8-poetry 1.2.3 in 5.3 seconds
- Downloaded python3.8-requests 1.2.3 in 5.3 seconds
-...
- Success! You have successfully built my-project.
-$
-```
-
-Above command clearly states that command successfully completed. And in case
-of `nix build`, which is a command that might take some time to complete, it is
-equally important to also show that a command started.
-
-## Text alignment
-
-Text alignment is the number one design element that will present all of the
-Nix commands as a family and not as separate tools glued together.
-
-The format we should follow is:
-
-```shell
-$ nix COMMAND
- VERB_1 NOUN and other words
- VERB__1 NOUN and other words
- |> Some details
-```
-
-Few rules that we can extract from above example:
-
-- Each line should start at least with one space.
-- First word should be a VERB and must be aligned to the right.
-- Second word should be a NOUN and must be aligned to the left.
-- If you can not find a good VERB / NOUN pair, don’t worry make it as
- understandable to the user as possible.
-- More details of each line can be provided by `|>` character which is serving
- as the first word when aligning the text
-
-Don’t forget you should also test your terminal output with colors and emojis
-off (`--no-colors --no-emojis`).
-
-## Dim / Bright
-
-After comparing few terminals with different color schemes we would **recommend
-to avoid using dimmed text**. The difference from the rest of the text is very
-little in many terminal and color scheme combinations. Sometimes the difference
-is not even notable, therefore relying on it wouldn’t make much sense.
-
-**The bright text is much better supported** across terminals and color
-schemes. Most of the time the difference is perceived as if the bright text
-would be bold.
-
-## Colors
-
-Humans are already conditioned by society to attach certain meaning to certain
-colors. While the meaning is not universal, a simple collection of colors is
-used to represent basic emotions.
-
-Colors that can be used in output
-
-- Red = error, danger, stop
-- Green = success, good
-- Yellow/Orange = proceed with caution, warning, in progress
-- Blue/Magenta = stability, calm
-
-While colors are nice, when command line is used by machines (in automation
-scripts) you want to remove the colors. There should be a global `--no-colors`
-option that would remove the colors.
-
-## Special (Unicode) characters
-
-Most of the terminal have good support for Unicode characters and you should
-use them in your output by default. But always have a backup solution that is
-implemented only with ASCII characters and will be used when `--ascii` option
-is going to be passed in. Please make sure that you test your output also
-without Unicode characters
-
-More they showing all the different Unicode characters it is important to
-**establish common set of characters** that we use for certain situations.
-
-## Emojis
-
-Emojis help channel emotions even better than text, colors and special
-characters.
-
-We recommend **keeping the set of emojis to a minimum**. This will enable each
-emoji to stand out more.
-
-As not everybody is happy about emojis we should provide an `--no-emojis`
-option to disable them. Please make sure that you test your output also without
-emojis.
-
-## Tables
-
-All commands that are listing certain data can be implemented in some sort of a
-table. It’s important that each row of your output is a single ‘entry’ of data.
-Never output table borders. It’s noisy and a huge pain for parsing using other
-tools such as `grep`.
-
-Be mindful of the screen width. Only show a few columns by default with the
-table header, for more the table can be manipulated by the following options:
-
-- `--no-headers`: Show column headers by default but allow to hide them.
-- `--columns`: Comma-separated list of column names to add.
-- `--sort`: Allow sorting by column. Allow inverse and multi-column sort as well.
-
-## Interactive output
-
-Interactive output was selected to be able to strike the balance between
-beginners and advance users. While the default output will target beginners it
-can, with a few key strokes, be changed into and advance introspection tool.
-
-### Progress
-
-For longer running commands we should provide and overview the progress.
-This is shown best in `nix build` example:
-
-```shell
-$ nix build
- Started building my-project 1.2.3
- Downloaded python3.8-poetry 1.2.3 in 5.3 seconds
- Downloaded python3.8-requests 1.2.3 in 5.3 seconds
-------------------------------------------------------------------------
- Press `v` to increase logs verbosity
- |> `?` to see other options
-------------------------------------------------------------------------
- Learn something new with every build...
- |> See last logs of a build with `nix log --last` command.
-------------------------------------------------------------------------
- Evaluated my-project 1.2.3 in 14.43 seconds
-Downloading [12 / 200]
- |> firefox 1.2.3 [#########> ] 10Mb/s | 2min left
- Building [2 / 20]
- |> glibc 1.2.3 -> buildPhase:
-------------------------------------------------------------------------
-```
-
-### Search
-
-Use a `fzf` like fuzzy search when there are multiple options to choose from.
-
-```shell
-$ nix init
-Initializing Nix project at `/path/to/here`.
- Select a template for you new project:
- |> py
- template#python-pip
- template#python-poetry
- [ Showing 2 templates from 1345 templates ]
-```
-
-### Prompt
-
-In some situations we need to prompt the user and inform the user about what is
-going to happen.
-
-```shell
-$ nix build --option substitutors https://cache.example.org
-------------------------------------------------------------------------
- Warning! A security related question needs to be answered.
-------------------------------------------------------------------------
- The following substitutors will be used to in `my-project`:
- - https://cache.example.org
-
- Do you allow `my-project` to use above mentioned substitutors?
- [y/N] |> y
-```
-
-## Verbosity
-
-There are many ways that you can control verbosity.
-
-Verbosity levels are:
-
-- `ERROR` (level 0)
-- `WARN` (level 1)
-- `NOTICE` (level 2)
-- `INFO` (level 3)
-- `TALKATIVE` (level 4)
-- `CHATTY` (level 5)
-- `DEBUG` (level 6)
-- `VOMIT` (level 7)
-
-The default level that the command starts is `ERROR`. The simplest way to
-increase the verbosity by stacking `-v` option (eg: `-vvv == level 3 == INFO`).
-There are also two shortcuts, `--debug` to run in `DEBUG` verbosity level and
-`--quiet` to run in `ERROR` verbosity level.
-
-----------
-
-# Appendix 1: Commands naming exceptions
-
-`nix init` and `nix repl` are well established
diff --git a/doc/manual/src/contributing/contributing.md b/doc/manual/src/contributing/contributing.md
deleted file mode 100644
index 854139a31..000000000
--- a/doc/manual/src/contributing/contributing.md
+++ /dev/null
@@ -1 +0,0 @@
-# Contributing
diff --git a/doc/manual/src/contributing/cxx.md b/doc/manual/src/contributing/cxx.md
deleted file mode 100644
index ff9297158..000000000
--- a/doc/manual/src/contributing/cxx.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# C++ style guide
-
-Some miscellaneous notes on how we write C++.
-Formatting we hope to eventually normalize automatically, so this section is free to just discuss higher-level concerns.
-
-## The `*-impl.hh` pattern
-
-Let's start with some background info first.
-Headers, are supposed to contain declarations, not definitions.
-This allows us to change a definition without changing the declaration, and have a very small rebuild during development.
-Templates, however, need to be specialized to use-sites.
-Absent fancier techniques, templates require that the definition, not just mere declaration, must be available at use-sites in order to make that specialization on the fly as part of compiling those use-sites.
-Making definitions available like that means putting them in headers, but that is unfortunately means we get all the extra rebuilds we want to avoid by just putting declarations there as described above.
-
-The `*-impl.hh` pattern is a ham-fisted partial solution to this problem.
-It constitutes:
-
-- Declaring items only in the main `foo.hh`, including templates.
-
-- Putting template definitions in a companion `foo-impl.hh` header.
-
-Most C++ developers would accompany this by having `foo.hh` include `foo-impl.hh`, to ensure any file getting the template declarations also got the template definitions.
-But we've found not doing this has some benefits and fewer than imagined downsides.
-The fact remains that headers are rarely as minimal as they could be;
-there is often code that needs declarations from the headers but not the templates within them.
-With our pattern where `foo.hh` doesn't include `foo-impl.hh`, that means they can just include `foo.hh`
-Code that needs both just includes `foo.hh` and `foo-impl.hh`.
-This does make linking error possible where something forgets to include `foo-impl.hh` that needs it, but those are build-time only as easy to fix.
diff --git a/doc/manual/src/contributing/experimental-features.md b/doc/manual/src/contributing/experimental-features.md
deleted file mode 100644
index c27ba5da0..000000000
--- a/doc/manual/src/contributing/experimental-features.md
+++ /dev/null
@@ -1,102 +0,0 @@
-This section describes the notion of *experimental features*, and how it fits into the big picture of the development of Lix.
-
-
-
-This section has not been updated for Lix *development practices* and should not be considered authoritative with respect to those; see the Lix wiki for more up-to-date information as it gets written . The technical content on this page is correct.
-
-
-
-
-# What are experimental features?
-
-Experimental features are considered unstable, which means that they can be changed or removed at any time.
-Users must explicitly enable them by toggling the associated [experimental feature flags](@docroot@/command-ref/conf-file.md#conf-experimental-features).
-This allows accessing unstable functionality without unwittingly relying on it.
-
-Experimental feature flags were first introduced in [Nix 2.4](@docroot@/release-notes/rl-2.4.md).
-Before that, Nix did have experimental features, but they were not guarded by flags and were merely documented as unstable.
-This was a source of confusion and controversy.
-
-# When should a new feature be marked experimental?
-
-A change in the Lix codebase should be guarded by an experimental feature flag if it is considered likely to be reverted or adapted in a backwards-incompatible manner after gathering more experience with it in practice.
-
-Examples:
-
-- Changes to the Nix language, such as new built-ins, syntactic or semantic changes, etc.
-- Changes to the command-line interface
-
-# Lifecycle of an experimental feature
-
-Experimental features have to be treated on a case-by-case basis.
-However, the standard workflow for an experimental feature is as follows:
-
-- A new feature is implemented in a *pull request*
- - It is guarded by an experimental feature flag that is disabled by default
-- The pull request is merged, the *experimental* feature ends up in a release
- - Using the feature requires explicitly enabling it, signifying awareness of the potential risks
- - Being experimental, the feature can still be changed arbitrarily
-- The feature can be *removed*
- - The associated experimental feature flag is also removed
-- The feature can be declared *stable*
- - The associated experimental feature flag is removed
- - There should be enough evidence of users having tried the feature, such as feedback, fixed bugs, demonstrations of how it is put to use
- - Maintainers must feel confident that:
- - The feature is designed and implemented sensibly, that it is fit for purpose
- - Potential interactions are well-understood
- - Stabilising the feature will not incur an outsized maintenance burden in the future
-
-The following diagram illustrates the process:
-
-```
- .------.
- | idea |
- '------'
- |
- discussion, design, implementation
- |
- | .-------.
- | | |
- v v |
- .--------------. review
- | pull request | |
- '--------------' |
- | ^ | |
- | | '-------'
- .---' '----.
- | |
- merge user feedback,
- | (breaking) changes
- | |
- '---. .----'
- | |
- v |
- +--------------+
- .---| experimental |----.
- | +--------------+ |
- | |
-decision to stabilise decision against
- | keeping the feature
- | |
- v v
- +--------+ +---------+
- | stable | | removed |
- +--------+ +---------+
-```
-
-# Relation to the RFC process
-
-Experimental features and [RFCs](https://github.com/NixOS/rfcs/) both allow approaching substantial changes while minimizing the risk.
-However they serve different purposes:
-
-- An experimental feature enables developers to iterate on and deliver a new idea without committing to it or requiring a costly long-running fork.
- It is primarily an issue of *implementation*, targeting Nix developers and early testers.
-- The goal of an RFC is to make explicit all the implications of a change:
- Explain why it is wanted, which new use-cases it enables, which interface changes it requires, etc.
- It is primarily an issue of *design* and *communication*, targeting the broader community.
-
-This means that experimental features and RFCs are orthogonal mechanisms, and can be used independently or together as needed.
-
-# Currently available experimental features
-
-{{#include @generated@/contributing/experimental-feature-descriptions.md}}
diff --git a/doc/manual/src/contributing/hacking.md b/doc/manual/src/contributing/hacking.md
deleted file mode 100644
index a8591e7ca..000000000
--- a/doc/manual/src/contributing/hacking.md
+++ /dev/null
@@ -1,352 +0,0 @@
-# Hacking
-
-This section provides some notes on how to hack on Lix. To get the latest version of Lix from Forgejo:
-
-```console
-$ git clone https://git.lix.systems/lix-project/lix
-$ cd lix
-```
-
-The following instructions assume you already have some version of Nix or Lix installed locally, so that you can use it to set up the development environment. If you don't have it installed, follow the [installation instructions].
-
-[installation instructions]: ../installation/installation.md
-
-## Building Lix in a development shell
-
-### Setting up the development shell
-
-If you are using Lix or Nix with the [`flakes`] and [`nix-command`] experimental features enabled, the following command will build all dependencies and start a shell in which all environment variables are setup for those dependencies to be found:
-
-```bash
-$ nix develop
-```
-
-That will use the default stdenv for your system. To get a shell with one of the other [supported compilation environments](#compilation-environments), specify its attribute name after a hash (which you may need to quote, depending on your shell):
-
-```bash
-$ nix develop ".#native-clangStdenvPackages"
-```
-
-For classic Nix, use:
-
-```bash
-$ nix-shell -A native-clangStdenvPackages
-```
-
-[`flakes`]: @docroot@/contributing/experimental-features.md#xp-feature-flakes
-[`nix-command`]: @docroot@/contributing/experimental-features.md#xp-nix-command
-
-
-### 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.:
-
-```bash
-$ configurePhase
-$ buildPhase
-$ checkPhase
-$ installPhase
-$ installCheckPhase
-```
-
-To build manually, however, use the following:
-
-```bash
-$ meson setup ./build "--prefix=$out" $mesonFlags
-```
-
-(A simple `meson setup ./build` will also build, but will do a different thing, not having the settings from package.nix applied).
-
-```bash
-$ meson compile -C build
-$ meson test -C build --suite=check
-$ 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.
-
-If the tests fail and Meson helpfully has no output for why, use the `--print-error-logs` option to `meson test`.
-
-If you change a setting in the buildsystem (i.e., any of the `meson.build` files), most cases will automatically regenerate the Meson configuration just before compiling.
-Some cases, however, like trying to build a specific target whose name is new to the buildsystem (e.g. `meson compile -C build src/libmelt/libmelt.dylib`, when `libmelt.dylib` did not exist as a target the last time the buildsystem was generated), then you can reconfigure using new settings but existing options, and only recompiling stuff affected by the changes:
-
-```bash
-$ meson setup --reconfigure build
-```
-
-Note that changes to the default values in `meson.options` or in the `default_options :` argument to `project()` are **not** propagated with `--reconfigure`.
-
-If you want a totally clean build, you can use:
-
-```bash
-$ meson setup --wipe build
-```
-
-That will work regardless of if `./build` exists or not.
-
-Specific, named targets may be addressed in `meson build -C build `, with the "target ID", if there is one, which is the first string argument passed to target functions that have one, and unrelated to the variable name, e.g.:
-
-```meson
-libexpr_dylib = library('nixexpr', …)
-```
-
-can be addressed with:
-
-```bash
-$ meson compile -C build nixexpr
-```
-
-All targets may be addressed as their output, relative to the build directory, e.g.:
-
-```bash
-$ meson compile -C build src/libexpr/libnixexpr.so
-```
-
-But Meson does not consider intermediate files like object files targets.
-To build a specific object file, use Ninja directly and specify the output file relative to the build directory:
-
-```bash
-$ ninja -C build src/libexpr/libnixexpr.so.p/nixexpr.cc.o
-```
-
-To inspect the canonical source of truth on what the state of the buildsystem configuration is, use:
-
-```bash
-$ meson introspect
-```
-
-## Building Lix outside of development shells
-
-To build a release version of Lix for the current operating system and CPU architecture:
-
-```console
-$ nix build
-```
-
-You can also build Lix for one of the [supported platforms](#platforms).
-
-> **Note**
->
-> You can use `native-ccacheStdenvPackages` to drastically improve rebuild time.
-> By default, [ccache](https://ccache.dev) keeps artifacts in `~/.cache/ccache/`.
-
-## Platforms
-
-Lix can be built for various platforms, as specified in [`flake.nix`]:
-
-[`flake.nix`]: https://github.com/nixos/nix/blob/master/flake.nix
-
-- `x86_64-linux`
-- `x86_64-darwin`
-- `i686-linux`
-- `aarch64-linux`
-- `aarch64-darwin`
-- `armv6l-linux`
-- `armv7l-linux`
-
-In order to build Lix for a different platform than the one you're currently
-on, you need a way for your current Nix installation to build code for that
-platform. Common solutions include [remote builders] and [binary format emulation]
-(only supported on NixOS).
-
-[remote builders]: ../advanced-topics/distributed-builds.md
-[binary format emulation]: https://nixos.org/manual/nixos/stable/options.html#opt-boot.binfmt.emulatedSystems
-
-Given such a setup, executing the build only requires selecting the respective attribute.
-For example, to compile for `aarch64-linux`:
-
-```console
-$ nix-build --attr packages.aarch64-linux.default
-```
-
-or for Nix with the [`flakes`] and [`nix-command`] experimental features enabled:
-
-```console
-$ 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.
-
-### Building for multiple platforms at once
-
-It is useful to perform multiple cross and native builds on the same source tree, for example to ensure that better support for one platform doesn't break the build for another.
-As Lix now uses Meson, out-of-tree builds are supported first class. In the invocation
-
-```bash
-$ meson setup build
-```
-
-the argument after `setup` specifies the directory for this build, conventionally simply called "build", but it may be called anything, and you may run `meson setup ` for as many different directories as you want.
-To compile the configuration for a given build directory, pass that build directory to the `-C` argument of `meson compile`:
-
-```bash
-$ meson setup some-custom-build
-$ meson compile -C some-custom-build
-```
-
-## System type
-
-Lix uses a string with the following format to identify the *system type* or *platform* it runs on:
-
-```
--[-]
-```
-
-It is set when Lix is compiled for the given system, and determined by [Meson's `host_machine.cpu_family()` and `host_machine.system()` values](https://mesonbuild.com/Reference-manual_builtin_host_machine.html).
-
-For historic reasons and backward-compatibility, some CPU and OS identifiers are translated from the GNU Autotools naming convention in [`meson.build`](https://git.lix.systems/lix-project/lix/blob/main/meson.build) as follows:
-
-| `host_machine.cpu_family()` | Nix |
-|----------------------------|---------------------|
-| `x86` | `i686` |
-| `i686` | `i686` |
-| `i686` | `i686` |
-| `arm6` | `arm6l` |
-| `arm7` | `arm7l` |
-| `linux-gnu*` | `linux` |
-| `linux-musl*` | `linux` |
-
-## Compilation environments
-
-Lix can be compiled using multiple environments:
-
-- `stdenv`: default;
-- `gccStdenv`: force the use of `gcc` compiler;
-- `clangStdenv`: force the use of `clang` compiler;
-- `ccacheStdenv`: enable [ccache], a compiler cache to speed up compilation.
-
-To build with one of those environments, you can use
-
-```console
-$ nix build .#nix-ccacheStdenv
-```
-
-for flake-enabled Nix, or
-
-```console
-$ nix-build --attr nix-ccacheStdenv
-```
-
-for classic Nix.
-
-You can use any of the other supported environments in place of `nix-ccacheStdenv`.
-
-## Editor integration
-
-The `clangd` LSP server is installed by default in each development shell.
-See [supported compilation environments](#compilation-environments) and instructions how to set up a shell [with flakes](#nix-with-flakes) or in [classic Nix](#classic-nix).
-
-Clangd requires a compilation database, which Meson generates by default. After running `meson setup`, there will already be a `compile_commands.json` file in the build directory.
-Some editor configurations may prefer that file to be in the root directory, which you can accomplish with a simple:
-
-```bash
-$ ln -sf ./build/compile_commands.json ./compile_commands.json
-```
-
-Configure your editor to use the `clangd` from the shell, either by running it inside the development shell, or by using [nix-direnv](https://github.com/nix-community/nix-direnv) and [the appropriate editor plugin](https://github.com/direnv/direnv/wiki#editor-integration).
-
-> **Note**
->
-> For some editors (e.g. Visual Studio Code), you may need to install a [special extension](https://open-vsx.org/extension/llvm-vs-code-extensions/vscode-clangd) for the editor to interact with `clangd`.
-> Some other editors (e.g. Emacs, Vim) need a plugin to support LSP servers in general (e.g. [lsp-mode](https://github.com/emacs-lsp/lsp-mode) for Emacs and [vim-lsp](https://github.com/prabirshrestha/vim-lsp) for vim).
-> Editor-specific setup is typically opinionated, so we will not cover it here in more detail.
-
-### Checking links in the manual
-
-The build checks for broken internal links.
-This happens late in the process, so `nix build` is not suitable for iterating.
-To build the manual incrementally, run:
-
-```console
-meson compile -C build manual
-```
-
-[`mdbook-linkcheck`] does not implement checking [URI fragments] yet.
-
-[`mdbook-linkcheck`]: https://github.com/Michael-F-Bryan/mdbook-linkcheck
-[URI fragments]: https://en.wikipedia.org/wiki/URI_fragment
-
-#### `@docroot@` variable
-
-`@docroot@` provides a base path for links that occur in reusable snippets or other documentation that doesn't have a base path of its own.
-
-If a broken link occurs in a snippet that was inserted into multiple generated files in different directories, use `@docroot@` to reference the `doc/manual/src` directory.
-
-If the `@docroot@` literal appears in an error message from the `mdbook-linkcheck` tool, the `@docroot@` replacement needs to be applied to the generated source file that mentions it.
-See existing `@docroot@` logic in the [Makefile].
-Regular markdown files used for the manual have a base path of their own and they can use relative paths instead of `@docroot@`.
-
-## 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:
-
-```console
-# nix build .#hydraJobs.internal-api-docs
-# xdg-open ./result/share/doc/nix/internal-api/html/index.html
-```
-
-or inside a `nix develop` shell by running:
-
-```bash
-$ 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:
-
-```
-# 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).
-
-## 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.
-
-### Add an entry
-
-Here's what a complete entry looks like. The file name is not incorporated in the document.
-
-```
----
-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
-prs: 1238
-# List of Lix Gerrit changelist numbers; if there is an associated Lix GitHub
-# PR, just put in the Gerrit CL number.
-cls: [123]
----
-
-Here's one or more paragraphs that describe the change.
-
-- It's markdown
-- Add references to the manual using @docroot@
-```
-
-Significant changes should add the following header, which moves them to the top.
-
-```
-significance: significant
-```
-
-### Build process
-
-Releases have a precomputed `rl-MAJOR.MINOR.md`, and no `rl-next.md`.
-Set `buildUnreleasedNotes = true;` in `flake.nix` to build the release notes on the fly.
diff --git a/doc/manual/src/contributing/meson.build b/doc/manual/src/contributing/meson.build
deleted file mode 100644
index 2929578c8..000000000
--- a/doc/manual/src/contributing/meson.build
+++ /dev/null
@@ -1,15 +0,0 @@
-# Intermediate step for experimental-feature-descriptions.md.
-# This splorks the output of generate-xp-features.nix as JSON,
-# which gets written as a directory tree below.
-experimental_feature_descriptions_md = custom_target(
- command : nix_eval_for_docs + [
- '--expr',
- 'import @INPUT0@ (builtins.fromJSON (builtins.readFile @INPUT1@))',
- ],
- input : [
- '../../generate-xp-features.nix',
- xp_features_json,
- ],
- capture : true,
- output : 'experimental-feature-descriptions.md',
-)
diff --git a/doc/manual/src/contributing/testing.md b/doc/manual/src/contributing/testing.md
deleted file mode 100644
index 0a844c662..000000000
--- a/doc/manual/src/contributing/testing.md
+++ /dev/null
@@ -1,322 +0,0 @@
-# Running tests
-
-## Unit-tests
-
-The unit tests are defined using the [googletest] and [rapidcheck] frameworks.
-
-[googletest]: https://google.github.io/googletest/
-[rapidcheck]: https://github.com/emil-e/rapidcheck
-
-### Source and header layout
-
-> An example of some files, demonstrating much of what is described below
->
-> ```
-> src
-> ├── libexpr
-> │ ├── value/context.hh
-> │ ├── value/context.cc
-> │ │
-> │ …
-> └── tests
-> │ ├── value/context.hh
-> │ ├── value/context.cc
-> │ │
-> │ …
-> │
-> ├── unit-test-data
-> │ ├── libstore
-> │ │ ├── worker-protocol/content-address.bin
-> │ │ …
-> │ …
-> …
-> ```
-
-
-
-The unit tests for each Lix library (`libnixexpr`, `libnixstore`, etc..) live inside a directory `src/${library_shortname}/tests` within the directory for the library (`src/${library_shortname}`).
-
-The data is in `unit-test-data`, with one subdir per library, with the same name as where the code goes.
-For example, `libnixstore` code is in `src/libstore`, and its test data is in `unit-test-data/libstore`.
-The path to the `unit-test-data` directory is passed to the unit test executable with the environment variable `_NIX_TEST_UNIT_DATA`.
-
-> **Note**
-> Due to the way googletest works, downstream unit test executables will actually include and re-run upstream library tests.
-> Therefore it is important that the same value for `_NIX_TEST_UNIT_DATA` be used with the tests for each library.
-> That is why we have the test data nested within a single `unit-test-data` directory.
-
-### Running tests
-
-You can run the whole testsuite with `just test` (see justfile for exact invocation of meson), and if you want to run just one test suite, use `just test --suite installcheck functional-init` where `installcheck` is the name of the test suite in this case and `functional-init` is the name of the test.
-
-To get a list of tests, use `meson test -C build --list`.
-
-For `installcheck` specifically, first run `just install` before running the test suite (this is due to meson limitations that don't let us put a dependency on installing before doing the test).
-
-Finer-grained filtering within a test suite is also possible using the [--gtest_filter](https://google.github.io/googletest/advanced.html#running-a-subset-of-the-tests) command-line option to a test suite executable, or the `GTEST_FILTER` environment variable.
-
-### Unit test support libraries
-
-There are headers and code which are not just used to test the library in question, but also downstream libraries.
-For example, we do [property testing] with the [rapidcheck] library.
-This requires writing `Arbitrary` "instances", which are used to describe how to generate values of a given type for the sake of running property tests.
-Because types contain other types, `Arbitrary` "instances" for some type are not just useful for testing that type, but also any other type that contains it.
-Downstream types frequently contain upstream types, so it is very important that we share arbitrary instances so that downstream libraries' property tests can also use them.
-
-It is important that these testing libraries don't contain any actual tests themselves.
-On some platforms they would be run as part of every test executable that uses them, which is redundant.
-On other platforms they wouldn't be run at all.
-
-### Characterization testing
-
-See [below](#characterization-testing-1) for a broader discussion of characterization testing.
-
-Like with the functional characterization, `_NIX_TEST_ACCEPT=1` is also used.
-For example:
-```shell-session
-$ _NIX_TEST_ACCEPT=1 make libstore-tests-exe_RUN
-...
-[ SKIPPED ] WorkerProtoTest.string_read
-[ SKIPPED ] WorkerProtoTest.string_write
-[ SKIPPED ] WorkerProtoTest.storePath_read
-[ SKIPPED ] WorkerProtoTest.storePath_write
-...
-```
-will regenerate the "golden master" expected result for the `libnixstore` characterization tests.
-The characterization tests will mark themselves "skipped" since they regenerated the expected result instead of actually testing anything.
-
-## Functional tests
-
-The functional tests reside under the `tests/functional` directory and are listed in `tests/functional/local.mk`.
-Each test is a bash script.
-
-### Running the whole test suite
-
-
-FIXME(meson): this section is wrong for meson and commented out accordingly. See "Running Tests" above, and ask the Lix team if you need further clarification.
-
-
-
-
-### Debugging failing functional tests
-
-When a functional test fails, it usually does so somewhere in the middle of the script.
-
-To figure out what's wrong, it is convenient to run the test regularly up to the failing `nix` command, and then run that command with a debugger like GDB.
-
-For example, if the script looks like:
-
-```bash
-foo
-nix blah blub
-bar
-```
-edit it like so:
-
-```diff
- foo
--nix blah blub
-+gdb --args nix blah blub
- bar
-```
-
-
-FIXME(meson): the command here may be incorrect for meson.
-
-
-Then, running the test with `./mk/debug-test.sh` will drop you into GDB once the script reaches that point:
-
-```shell-session
-$ ./mk/debug-test.sh tests/functional/${testName}.sh
-...
-+ gdb blash blub
-GNU gdb (GDB) 12.1
-...
-(gdb)
-```
-
-One can debug the Nix invocation in all the usual ways.
-For example, enter `run` to start the Nix invocation.
-
-### Characterization testing
-
-Occasionally, Lix utilizes a technique called [Characterization Testing](https://en.wikipedia.org/wiki/Characterization_test) as part of the functional tests.
-This technique is to include the exact output/behavior of a former version of Nix in a test in order to check that Lix continues to produce the same behavior going forward.
-
-For example, this technique is used for the language tests, to check both the printed final value if evaluation was successful, and any errors and warnings encountered.
-
-
-FIXME(meson): this is incorrect for meson. `_NIX_TEST_ACCEPT=1` is still valid but the test invocation needs to change.
-
-
-It is frequently useful to regenerate the expected output.
-To do that, rerun the failed test(s) with `_NIX_TEST_ACCEPT=1`.
-For example:
-```bash
-_NIX_TEST_ACCEPT=1 make tests/functional/lang.sh.test
-```
-
-An interesting situation to document is the case when these tests are "overfitted".
-The language tests are, again, an example of this.
-The expected successful output of evaluation is supposed to be highly stable – we do not intend to make breaking changes to (the stable parts of) the Nix language.
-However, the errors and warnings during evaluation (successful or not) are not stable in this way.
-We are free to change how they are displayed at any time.
-
-It may be surprising that we would test non-normative behavior like diagnostic outputs.
-Diagnostic outputs are indeed not a stable interface, but they still are important to users.
-By recording the expected output, the test suite guards against accidental changes, and ensure the *result* (not just the code that implements it) of the diagnostic code paths are under code review.
-Regressions are caught, and improvements always show up in code review.
-
-To ensure that characterization testing doesn't make it harder to intentionally change these interfaces, there always must be an easy way to regenerate the expected output, as we do with `_NIX_TEST_ACCEPT=1`.
-
-## Integration tests
-
-The integration tests are defined in the Nix flake under the `hydraJobs.tests` attribute.
-These tests include everything that needs to interact with external services or run Lix in a non-trivial distributed setup.
-Because these tests are expensive and require more than what the standard github-actions setup provides, they only run on the master branch (on ).
-
-You can run them manually with `nix build .#hydraJobs.tests.{testName}` or `nix-build -A hydraJobs.tests.{testName}`
-
-
-
-Installer tests section is outdated and commented out, see https://git.lix.systems/lix-project/lix/issues/33
-
-
-
-
diff --git a/doc/manual/src/figures/user-environments.png b/doc/manual/src/figures/user-environments.png
deleted file mode 100644
index 1f781cf23..000000000
Binary files a/doc/manual/src/figures/user-environments.png and /dev/null differ
diff --git a/doc/manual/src/figures/user-environments.sxd b/doc/manual/src/figures/user-environments.sxd
deleted file mode 100644
index bc661b640..000000000
Binary files a/doc/manual/src/figures/user-environments.sxd and /dev/null differ
diff --git a/doc/manual/src/glossary.md b/doc/manual/src/glossary.md
deleted file mode 100644
index caf740724..000000000
--- a/doc/manual/src/glossary.md
+++ /dev/null
@@ -1,275 +0,0 @@
-# Glossary
-
-- [derivation]{#gloss-derivation}
-
- A description of a build task. The result of a derivation is a
- store object. Derivations are typically specified in Nix expressions
- using the [`derivation` primitive](./language/derivations.md). These are
- translated into low-level *store derivations* (implicitly by
- `nix-env` and `nix-build`, or explicitly by `nix-instantiate`).
-
- [derivation]: #gloss-derivation
-
-- [store derivation]{#gloss-store-derivation}
-
- A [derivation] represented as a `.drv` file in the [store].
- It has a [store path], like any [store object].
-
- Example: `/nix/store/g946hcz4c8mdvq2g8vxx42z51qb71rvp-git-2.38.1.drv`
-
- See [`nix derivation show`](./command-ref/new-cli/nix3-derivation-show.md) (experimental) for displaying the contents of store derivations.
-
- [store derivation]: #gloss-store-derivation
-
-- [instantiate]{#gloss-instantiate}, instantiation
-
- Translate a [derivation] into a [store derivation].
-
- See [`nix-instantiate`](./command-ref/nix-instantiate.md).
-
- [instantiate]: #gloss-instantiate
-
-- [realise]{#gloss-realise}, realisation
-
- Ensure a [store path] is [valid][validity].
-
- This means either running the [`builder`](@docroot@/language/derivations.md#attr-builder) executable as specified in the corresponding [derivation], or fetching a pre-built [store object] from a [substituter], or delegating to a [remote builder](@docroot@/advanced-topics/distributed-builds.html) and retrieving the outputs.
-
- See [`nix-build`](./command-ref/nix-build.md) and [`nix-store --realise`](@docroot@/command-ref/nix-store/realise.md).
-
- See [`nix build`](./command-ref/new-cli/nix3-build.md) (experimental).
-
- [realise]: #gloss-realise
-
-- [content-addressed derivation]{#gloss-content-addressed-derivation}
-
- A derivation which has the
- [`__contentAddressed`](./language/advanced-attributes.md#adv-attr-__contentAddressed)
- attribute set to `true`.
-
-- [fixed-output derivation]{#gloss-fixed-output-derivation}
-
- A derivation which includes the
- [`outputHash`](./language/advanced-attributes.md#adv-attr-outputHash) attribute.
-
-- [store]{#gloss-store}
-
- The location in the file system where store objects live. Typically
- `/nix/store`.
-
- From the perspective of the location where Lix is
- invoked, the Nix store can be referred to
- as a "_local_" or a "_remote_" one:
-
- + A [local store]{#gloss-local-store} exists on the filesystem of
- the machine where Lix is invoked. You can use other
- local stores by passing the `--store` flag to the
- `nix` command. Local stores can be used for building derivations.
-
- + A *remote store* exists anywhere other than the
- local filesystem. One example is the `/nix/store`
- directory on another machine, accessed via `ssh` or
- served by the `nix-serve` Perl script.
-
- [store]: #gloss-store
- [local store]: #gloss-local-store
-
-- [chroot store]{#gloss-chroot-store}
-
- A [local store] whose canonical path is anything other than `/nix/store`.
-
-- [binary cache]{#gloss-binary-cache}
-
- A *binary cache* is a Nix store which uses a different format: its
- metadata and signatures are kept in `.narinfo` files rather than in a
- [Nix database]. This different format simplifies serving store objects
- over the network, but cannot host builds. Examples of binary caches
- include S3 buckets and the [NixOS binary cache](https://cache.nixos.org).
-
-- [store path]{#gloss-store-path}
-
- The location of a [store object] in the file system, i.e., an
- immediate child of the Nix store directory.
-
- Example: `/nix/store/a040m110amc4h71lds2jmr8qrkj2jhxd-git-2.38.1`
-
- [store path]: #gloss-store-path
-
-- [file system object]{#gloss-store-object}
-
- The Nix data model for representing simplified file system data.
-
- See [File System Object](@docroot@/architecture/file-system-object.md) for details.
-
- [file system object]: #gloss-file-system-object
-
-- [store object]{#gloss-store-object}
-
-
- A store object consists of a [file system object], [reference]s to other store objects, and other metadata.
- It can be referred to by a [store path].
-
- [store object]: #gloss-store-object
-
-- [input-addressed store object]{#gloss-input-addressed-store-object}
-
- A store object produced by building a
- non-[content-addressed](#gloss-content-addressed-derivation),
- non-[fixed-output](#gloss-fixed-output-derivation)
- derivation.
-
-- [output-addressed store object]{#gloss-output-addressed-store-object}
-
- A [store object] whose [store path] is determined by its contents.
- This includes derivations, the outputs of [content-addressed derivations](#gloss-content-addressed-derivation), and the outputs of [fixed-output derivations](#gloss-fixed-output-derivation).
-
-- [substitute]{#gloss-substitute}
-
- A substitute is a command invocation stored in the [Nix database] that
- describes how to build a store object, bypassing the normal build
- mechanism (i.e., derivations). Typically, the substitute builds the
- store object by downloading a pre-built version of the store object
- from some server.
-
-- [substituter]{#gloss-substituter}
-
- An additional [store]{#gloss-store} from which Lix can obtain store objects instead of building them.
- Often the substituter is a [binary cache](#gloss-binary-cache), but any store can serve as substituter.
-
- See the [`substituters` configuration option](./command-ref/conf-file.md#conf-substituters) for details.
-
- [substituter]: #gloss-substituter
-
-- [purity]{#gloss-purity}
-
- The assumption that equal Nix derivations when run always produce
- the same output. This cannot be guaranteed in general (e.g., a
- builder can rely on external inputs such as the network or the
- system time) but the Nix model assumes it.
-
-- [Nix database]{#gloss-nix-database}
-
- An SQlite database to track [reference]s between [store object]s.
- This is an implementation detail of the [local store].
-
- Default location: `/nix/var/nix/db`.
-
- [Nix database]: #gloss-nix-database
-
-- [Nix expression]{#gloss-nix-expression}
-
- A high-level description of software packages and compositions
- thereof. Deploying software using Lix entails writing Nix
- expressions for your packages. Nix expressions are translated to
- derivations that are stored in the Nix store. These derivations can
- then be built.
-
-- [reference]{#gloss-reference}
-
- A [store object] `O` is said to have a *reference* to a store object `P` if a [store path] to `P` appears in the contents of `O`.
-
- Store objects can refer to both other store objects and themselves.
- References from a store object to itself are called *self-references*.
- References other than a self-reference must not form a cycle.
-
- [reference]: #gloss-reference
-
-- [reachable]{#gloss-reachable}
-
- A store path `Q` is reachable from another store path `P` if `Q`
- is in the *closure* of the *references* relation.
-
-- [closure]{#gloss-closure}
-
- The closure of a store path is the set of store paths that are
- directly or indirectly “reachable” from that store path; that is,
- it’s the closure of the path under the *references* relation. For
- a package, the closure of its derivation is equivalent to the
- build-time dependencies, while the closure of its output path is
- equivalent to its runtime dependencies. For correct deployment it
- is necessary to deploy whole closures, since otherwise at runtime
- files could be missing. The command `nix-store --query --requisites ` prints out
- closures of store paths.
-
- As an example, if the [store object] at path `P` contains a [reference]
- to a store object at path `Q`, then `Q` is in the closure of `P`. Further, if `Q`
- references `R` then `R` is also in the closure of `P`.
-
- [closure]: #gloss-closure
-
-- [output]{#gloss-output}
-
- A [store object] produced by a [derivation].
-
- [output]: #gloss-output
-
-- [output path]{#gloss-output-path}
-
- The [store path] to the [output] of a [derivation].
-
- [output path]: #gloss-output-path
-
-- [deriver]{#gloss-deriver}
-
- The [store derivation] that produced an [output path].
-
-- [validity]{#gloss-validity}
-
- A store path is valid if all [store object]s in its [closure] can be read from the [store].
-
- For a [local store], this means:
- - The store path leads to an existing [store object] in that [store].
- - The store path is listed in the [Nix database] as being valid.
- - All paths in the store path's [closure] are valid.
-
- [validity]: #gloss-validity
-
-- [user environment]{#gloss-user-env}
-
- An automatically generated store object that consists of a set of
- symlinks to “active” applications, i.e., other store paths. These
- are generated automatically by
- [`nix-env`](./command-ref/nix-env.md). See *profiles*.
-
-- [profile]{#gloss-profile}
-
- A symlink to the current *user environment* of a user, e.g.,
- `/nix/var/nix/profiles/default`.
-
-- [installable]{#gloss-installable}
-
- Something that can be realised in the Nix store.
-
- See [installables](./command-ref/new-cli/nix.md#installables) for [`nix` commands](./command-ref/new-cli/nix.md) (experimental) for details.
-
-- [NAR]{#gloss-nar}
-
- A *N*ix *AR*chive. This is a serialisation of a path in the Nix
- store. It can contain regular files, directories and symbolic
- links. NARs are generated and unpacked using `nix-store --dump`
- and `nix-store --restore`.
-
-- [`∅`]{#gloss-emtpy-set}
-
- The empty set symbol. In the context of profile history, this denotes a package is not present in a particular version of the profile.
-
-- [`ε`]{#gloss-epsilon}
-
- The epsilon symbol. In the context of a package, this means the version is empty. More precisely, the derivation does not have a version attribute.
-
-- [string interpolation]{#gloss-string-interpolation}
-
- Expanding expressions enclosed in `${ }` within a [string], [path], or [attribute name].
-
- See [String interpolation](./language/string-interpolation.md) for details.
-
- [string]: ./language/values.md#type-string
- [path]: ./language/values.md#type-path
- [attribute name]: ./language/values.md#attribute-set
-
-- [experimental feature]{#gloss-experimental-feature}
-
- Not yet stabilized functionality guarded by named experimental feature flags.
- These flags are enabled or disabled with the [`experimental-features`](./command-ref/conf-file.html#conf-experimental-features) setting.
-
- See the contribution guide on the [purpose and lifecycle of experimental feaures](@docroot@/contributing/experimental-features.md).
diff --git a/doc/manual/src/installation/building-source.md b/doc/manual/src/installation/building-source.md
deleted file mode 100644
index 83c645ae7..000000000
--- a/doc/manual/src/installation/building-source.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# Building Lix from Source
-
-
-
-FIXME(meson): This section is outdated for meson and has been commented out. See https://git.lix.systems/lix-project/lix/issues/258
-
-
-
-
diff --git a/doc/manual/src/installation/env-variables.md b/doc/manual/src/installation/env-variables.md
deleted file mode 100644
index fb6f02e41..000000000
--- a/doc/manual/src/installation/env-variables.md
+++ /dev/null
@@ -1,71 +0,0 @@
-# Environment Variables
-
-To use Lix, some environment variables should be set. In particular,
-`PATH` should contain the directories `prefix/bin` and
-`~/.nix-profile/bin`. The first directory contains the Nix tools
-themselves, while `~/.nix-profile` is a symbolic link to the current
-*user environment* (an automatically generated package consisting of
-symlinks to installed packages). The simplest way to set the required
-environment variables is to include the file
-`prefix/etc/profile.d/nix.sh` in your `~/.profile` (or similar), like
-this:
-
-```bash
-source prefix/etc/profile.d/nix.sh
-```
-
-# `NIX_SSL_CERT_FILE`
-
-
-
-FIXME(Lix): This section is undoubtedly wrong due to the Lix installer being replaced. The definitely-wrong install section has been commented out.
-
-
-
-If you need to specify a custom certificate bundle to account for an
-HTTPS-intercepting man in the middle proxy, you must specify the path to
-the certificate bundle in the environment variable `NIX_SSL_CERT_FILE`.
-
-If you don't specify a `NIX_SSL_CERT_FILE` manually, Lix will install
-and use its own certificate bundle.
-
-
-
-In the shell profile and rc files (for example, `/etc/bashrc`,
-`/etc/zshrc`), add the following line:
-
-```bash
-export NIX_SSL_CERT_FILE=/etc/ssl/my-certificate-bundle.crt
-```
-
-> **Note**
->
-> You must not add the export and then do the install, as the Lix
-> installer will detect the presence of Nix configuration, and abort.
-
-If you use the Lix daemon, you should also add the following to
-`/etc/nix/nix.conf`:
-
-```
-ssl-cert-file = /etc/ssl/my-certificate-bundle.crt
-```
-
-## Proxy Environment Variables
-
-The Lix installer has special handling for these proxy-related
-environment variables: `http_proxy`, `https_proxy`, `ftp_proxy`,
-`no_proxy`, `HTTP_PROXY`, `HTTPS_PROXY`, `FTP_PROXY`, `NO_PROXY`.
-
-If any of these variables are set when running the Lix installer, then
-the installer will create an override file at
-`/etc/systemd/system/nix-daemon.service.d/override.conf` so `nix-daemon`
-will use them.
diff --git a/doc/manual/src/installation/installation.md b/doc/manual/src/installation/installation.md
deleted file mode 100644
index d05445eab..000000000
--- a/doc/manual/src/installation/installation.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Installation
-
-See https://lix.systems/install/ for more details.
-
-
diff --git a/doc/manual/src/installation/installing-binary.md b/doc/manual/src/installation/installing-binary.md
deleted file mode 100644
index c2edc0dc2..000000000
--- a/doc/manual/src/installation/installing-binary.md
+++ /dev/null
@@ -1,166 +0,0 @@
-# Installing a Binary Distribution
-
-See https://lix.systems/install/ for more details.
-
-
diff --git a/doc/manual/src/installation/installing-docker.md b/doc/manual/src/installation/installing-docker.md
deleted file mode 100644
index 2d7701024..000000000
--- a/doc/manual/src/installation/installing-docker.md
+++ /dev/null
@@ -1,64 +0,0 @@
-# Using Lix within Docker
-
-Currently the Lix project doesn't ship docker images. However, we have the infrastructure to do it, it's just not yet been done. See https://git.lix.systems/lix-project/lix/issues/252
-
-
diff --git a/doc/manual/src/installation/installing-source.md b/doc/manual/src/installation/installing-source.md
deleted file mode 100644
index 06d070610..000000000
--- a/doc/manual/src/installation/installing-source.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Installing Lix from Source
-
-If no binary package is available or if you want to hack on Lix, you
-can build Lix from its Git repository.
diff --git a/doc/manual/src/installation/multi-user.md b/doc/manual/src/installation/multi-user.md
deleted file mode 100644
index a4cdd928b..000000000
--- a/doc/manual/src/installation/multi-user.md
+++ /dev/null
@@ -1,77 +0,0 @@
-# Multi-User Mode
-
-To allow a Nix store to be shared safely among multiple users, it is
-important that users are not able to run builders that modify the Nix
-store or database in arbitrary ways, or that interfere with builds
-started by other users. If they could do so, they could install a Trojan
-horse in some package and compromise the accounts of other users.
-
-To prevent this, the Nix store and database are owned by some privileged
-user (usually `root`) and builders are executed under special user
-accounts (usually named `nixbld1`, `nixbld2`, etc.). When a unprivileged
-user runs a Nix command, actions that operate on the Nix store (such as
-builds) are forwarded to a *Nix daemon* running under the owner of the
-Nix store/database that performs the operation.
-
-> **Note**
->
-> Multi-user mode has one important limitation: only root and a set of
-> trusted users specified in `nix.conf` can specify arbitrary binary
-> caches. So while unprivileged users may install packages from
-> arbitrary Nix expressions, they may not get pre-built binaries.
-
-## Setting up the build users
-
-The *build users* are the special UIDs under which builds are performed.
-They should all be members of the *build users group* `nixbld`. This
-group should have no other members. The build users should not be
-members of any other group. On Linux, you can create the group and users
-as follows:
-
-```console
-$ groupadd -r nixbld
-$ for n in $(seq 1 10); do useradd -c "Nix build user $n" \
- -d /var/empty -g nixbld -G nixbld -M -N -r -s "$(which nologin)" \
- nixbld$n; done
-```
-
-This creates 10 build users. There can never be more concurrent builds
-than the number of build users, so you may want to increase this if you
-expect to do many builds at the same time.
-
-## Running the daemon
-
-The [Nix daemon](../command-ref/nix-daemon.md) should be started as
-follows (as `root`):
-
-```console
-$ nix-daemon
-```
-
-You’ll want to put that line somewhere in your system’s boot scripts.
-
-To let unprivileged users use the daemon, they should set the
-[`NIX_REMOTE` environment variable](../command-ref/env-common.md) to
-`daemon`. So you should put a line like
-
-```console
-export NIX_REMOTE=daemon
-```
-
-into the users’ login scripts.
-
-## Restricting access
-
-To limit which users can perform Nix operations, you can use the
-permissions on the directory `/nix/var/nix/daemon-socket`. For instance,
-if you want to restrict the use of Nix to the members of a group called
-`nix-users`, do
-
-```console
-$ chgrp nix-users /nix/var/nix/daemon-socket
-$ chmod ug=rwx,o= /nix/var/nix/daemon-socket
-```
-
-This way, users who are not in the `nix-users` group cannot connect to
-the Unix domain socket `/nix/var/nix/daemon-socket/socket`, so they
-cannot perform Nix operations.
diff --git a/doc/manual/src/installation/nix-security.md b/doc/manual/src/installation/nix-security.md
deleted file mode 100644
index d5ae7535d..000000000
--- a/doc/manual/src/installation/nix-security.md
+++ /dev/null
@@ -1,15 +0,0 @@
-# Security
-
-Lix has two basic security models. First, it can be used in “single-user
-mode”, which is similar to what most other package management tools do:
-there is a single user (typically root) who performs all package
-management operations. All other users can then use the installed
-packages, but they cannot perform package management operations
-themselves.
-
-Alternatively, you can configure Lix in “multi-user mode”. In this
-model, all users can perform package management operations — for
-instance, every user can install software without requiring root
-privileges. Lix ensures that this is secure. For instance, it’s not
-possible for one user to overwrite a package used by another user with a
-Trojan horse.
diff --git a/doc/manual/src/installation/obtaining-source.md b/doc/manual/src/installation/obtaining-source.md
deleted file mode 100644
index da05d243d..000000000
--- a/doc/manual/src/installation/obtaining-source.md
+++ /dev/null
@@ -1,13 +0,0 @@
-# Obtaining the Source
-
-The most recent sources of Nix can be obtained from its [Git
-repository](https://github.com/NixOS/nix). For example, the following
-command will check out the latest revision into a directory called
-`nix`:
-
-```console
-$ git clone https://github.com/NixOS/nix
-```
-
-Likewise, specific releases can be obtained from the
-[tags](https://github.com/NixOS/nix/tags) of the repository.
diff --git a/doc/manual/src/installation/prerequisites-source.md b/doc/manual/src/installation/prerequisites-source.md
deleted file mode 100644
index 8584f295a..000000000
--- a/doc/manual/src/installation/prerequisites-source.md
+++ /dev/null
@@ -1,90 +0,0 @@
-# Prerequisites
-
-
-
-FIXME(meson): This section is very wrong with respect to meson and we have commented it out.
-We are sorry.
-The most current alternative to this section is to read `package.nix` and see which things are being depended on.
-
-
-
-
diff --git a/doc/manual/src/installation/single-user.md b/doc/manual/src/installation/single-user.md
deleted file mode 100644
index f9a3b26ed..000000000
--- a/doc/manual/src/installation/single-user.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Single-User Mode
-
-In single-user mode, all Nix operations that access the database in
-`prefix/var/nix/db` or modify the Nix store in `prefix/store` must be
-performed under the user ID that owns those directories. This is
-typically root. (If you install from RPM packages, that’s in fact the
-default ownership.) However, on single-user machines, it is often
-convenient to `chown` those directories to your normal user account so
-that you don’t have to `su` to root all the time.
diff --git a/doc/manual/src/installation/supported-platforms.md b/doc/manual/src/installation/supported-platforms.md
deleted file mode 100644
index 3b07ce48a..000000000
--- a/doc/manual/src/installation/supported-platforms.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Supported Platforms
-
-Lix is currently supported on the following platforms:
-
- - Linux (i686 (tier 2), x86\_64 (tier 1), aarch64 (tier 1)).
-
- - macOS (x86\_64 (tier 2 [(issue to make tier 1)](https://git.lix.systems/lix-project/lix/issues/269)), aarch64 (tier 1)).
-
-
-Tier 2 platforms aren't checked in CI, so may break without notice; such breakage *is* however considered a bug.
-We would like for them to work but they are a secondary priority.
diff --git a/doc/manual/src/installation/uninstall.md b/doc/manual/src/installation/uninstall.md
deleted file mode 100644
index 5fb8b56e4..000000000
--- a/doc/manual/src/installation/uninstall.md
+++ /dev/null
@@ -1,158 +0,0 @@
-# Uninstalling Lix
-
-
-
-FIXME(Lix): This section is outdated and commented out due to the Lix installer being replaced such that it has an actual uninstaller.
-
-See https://git.lix.systems/lix-project/lix-installer#uninstalling for up-to-date uninstallation instructions using the installer.
-
-
-
-
diff --git a/doc/manual/src/installation/upgrading.md b/doc/manual/src/installation/upgrading.md
deleted file mode 100644
index 2cdbf9683..000000000
--- a/doc/manual/src/installation/upgrading.md
+++ /dev/null
@@ -1,23 +0,0 @@
-# Upgrading Lix
-
-
-
-FIXME(Lix): does Lix forward to the installer for `nix upgrade-nix`? Should it, if present? Lix *should* restart the daemon for you [but currently doesn't (issue)](https://git.lix.systems/lix-project/lix/issues/267).
-
-
-
-**For instructions to switch to Lix**, see .
-
-Lix may be upgraded by running `nix upgrade-nix` and then restarting the Nix daemon.
-
-## Restarting daemon on Linux
-
-`sudo systemctl daemon-reload && sudo systemctl restart nix-daemon`
-
-## Restarting daemon on macOS
-
-
-
-FIXME(Lix): Write instructions that, according to the [beta installation guide](https://wiki.lix.systems/link/1) do not sometimes crash macOS (?!)
-
-
diff --git a/doc/manual/src/introduction.md b/doc/manual/src/introduction.md
deleted file mode 100644
index 9fbc429f8..000000000
--- a/doc/manual/src/introduction.md
+++ /dev/null
@@ -1,186 +0,0 @@
-# Introduction
-
-Lix is an implementation of Nix, a powerful, _purely functional_ package management system.
-This means that it treats packages like values in purely functional programming languages such as Haskell — they are built by functions that don’t have side-effects, and they never change after they have been built.
-Lix stores packages in the _Nix store_, usually the directory `/nix/store`, where each package has its own unique subdirectory such as
-
- /nix/store/b6gvzjyb2pg0kjfwrjmg1vfhh54ad73z-firefox-33.1/
-
-where `b6gvzjyb2pg0…` is a unique identifier for the package that
-captures all its dependencies (it’s a cryptographic hash of the
-package’s build dependency graph). This enables many powerful
-features.
-
-## Multiple versions
-
-You can have multiple versions or variants of a package
-installed at the same time. This is especially important when
-different applications have dependencies on different versions of the
-same package — it prevents the “DLL hell”. Because of the hashing
-scheme, different versions of a package end up in different paths in
-the Nix store, so they don’t interfere with each other.
-
-An important consequence is that operations like upgrading or
-uninstalling an application cannot break other applications, since
-these operations never “destructively” update or delete files that are
-used by other packages.
-
-## Complete dependencies
-
-Lix helps you make sure that package dependency specifications are
-complete. In general, when you’re making a package for a package
-management system like RPM, you have to specify for each package what
-its dependencies are, but there are no guarantees that this
-specification is complete. If you forget a dependency, then the
-package will build and work correctly on _your_ machine if you have
-the dependency installed, but not on the end user's machine if it's
-not there.
-
-Since Lix on the other hand doesn’t install packages in “global”
-locations like `/usr/bin` but in package-specific directories, the
-risk of incomplete dependencies is greatly reduced. This is because
-tools such as compilers don’t search in per-packages directories such
-as `/nix/store/5lbfaxb722zp…-openssl-0.9.8d/include`, so if a package
-builds correctly on your system, this is because you specified the
-dependency explicitly. This takes care of the build-time dependencies.
-
-Once a package is built, runtime dependencies are found by scanning
-binaries for the hash parts of Nix store paths (such as `r8vvq9kq…`).
-This sounds risky, but it works extremely well.
-
-## Multi-user support
-
-Lix has multi-user support.
-This means that non-privileged users can securely install software, and it is considered a bug if users can trample on each other.
-Each user can have a different _profile_, a set of packages in the Nix store that appear in the user’s `PATH`.
-If a user installs a package that another user has already installed previously, the package won’t be built or downloaded a second time.
-At the same time, it is not possible for one user to inject a Trojan horse into a package that might be used by another user.
-
-## Atomic upgrades and rollbacks
-
-Since package management operations never overwrite packages in the
-Nix store but just add new versions in different paths, they are
-_atomic_. So during a package upgrade, there is no time window in
-which the package has some files from the old version and some files
-from the new version — which would be bad because a program might well
-crash if it’s started during that period.
-
-And since packages aren’t overwritten, the old versions are still
-there after an upgrade. This means that you can _roll back_ to the
-old version:
-
-```console
-$ nix-env --upgrade --attr nixpkgs.some-package
-$ nix-env --rollback
-```
-
-## Garbage collection
-
-When you uninstall a package like this…
-
-```console
-$ nix-env --uninstall firefox
-```
-
-the package isn’t deleted from the system right away (after all, you
-might want to do a rollback, or it might be in the profiles of other
-users). Instead, unused packages can be deleted safely by running the
-_garbage collector_:
-
-```console
-$ nix-collect-garbage
-```
-
-This deletes all packages that aren’t in use by any user profile or by
-a currently running program.
-
-## Functional package language
-
-Packages are built from _Nix expressions_, which is a simple
-functional language. A Nix expression describes everything that goes
-into a package build task (a “derivation”): other packages, sources,
-the build script, environment variables for the build script, etc.
-Lix tries very hard to ensure that Nix expressions are
-_deterministic_: building a Nix expression twice should yield the same
-result.
-
-Because it’s a functional language, it’s easy to support
-building variants of a package: turn the Nix expression into a
-function and call it any number of times with the appropriate
-arguments. Due to the hashing scheme, variants don’t conflict with
-each other in the Nix store.
-
-## Transparent source/binary deployment
-
-Nix expressions generally describe how to build a package from
-source, so an installation action like
-
-```console
-$ nix-env --install --attr nixpkgs.firefox
-```
-
-_could_ cause quite a bit of build activity, as not only Firefox but
-also all its dependencies (all the way up to the C library and the
-compiler) would have to be built, at least if they are not already in the
-Nix store. This is a _source deployment model_. For most users,
-building from source is not very pleasant as it takes far too long.
-However, Lix can automatically skip building from source and instead
-use a _binary cache_, a web server that provides pre-built
-binaries. For instance, when asked to build
-`/nix/store/b6gvzjyb2pg0…-firefox-33.1` from source, Lix would first
-check if the file `https://cache.nixos.org/b6gvzjyb2pg0….narinfo`
-exists, and if so, fetch the pre-built binary referenced from there;
-otherwise, it would fall back to building from source.
-
-## Nix Packages collection
-
-We provide a large set of Nix expressions containing tens of thousands of existing Unix packages, the _Nix Packages collection_ (Nixpkgs).
-
-## Managing build environments
-
-Lix is extremely useful for developers as it makes it easy to
-automatically set up the build environment for a package. Given a Nix
-expression that describes the dependencies of your package, the
-command `nix-shell` will build or download those dependencies if
-they’re not already in your Nix store, and then start a Bash shell in
-which all necessary environment variables (such as compiler search
-paths) are set.
-
-For example, the following command gets all dependencies of the
-Pan newsreader, as described by [its
-Nix expression](https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/networking/newsreaders/pan/default.nix):
-
-```console
-$ nix-shell '' --attr pan
-```
-
-You’re then dropped into a shell where you can edit, build and test
-the package:
-
-```console
-[nix-shell]$ unpackPhase
-[nix-shell]$ cd pan-*
-[nix-shell]$ configurePhase
-[nix-shell]$ buildPhase
-[nix-shell]$ ./pan/gui/pan
-```
-
-## Portability
-
-Lix runs on Linux and macOS.
-
-## NixOS
-
-NixOS is a Linux distribution based on Nix technology. It uses Nix not just for
-package management but also to manage the system configuration (e.g.,
-to build configuration files in `/etc`). This means, among other
-things, that it is easy to roll back the entire configuration of the
-system to an earlier state. Also, users can install software without
-root privileges. For more information and downloads, see the [NixOS
-homepage](https://nixos.org/).
-
-## License
-
-Lix is released under the terms of the [GNU LGPLv2.1 or (at your
-option) any later
-version](http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html).
diff --git a/doc/manual/src/language/advanced-attributes.md b/doc/manual/src/language/advanced-attributes.md
deleted file mode 100644
index ec21b9990..000000000
--- a/doc/manual/src/language/advanced-attributes.md
+++ /dev/null
@@ -1,343 +0,0 @@
-# Advanced Attributes
-
-Derivations can declare some infrequently used optional attributes.
-
- - [`allowedReferences`]{#adv-attr-allowedReferences}\
- The optional attribute `allowedReferences` specifies a list of legal
- references (dependencies) of the output of the builder. For example,
-
- ```nix
- allowedReferences = [];
- ```
-
- enforces that the output of a derivation cannot have any runtime
- dependencies on its inputs. To allow an output to have a runtime
- dependency on itself, use `"out"` as a list item. This is used in
- NixOS to check that generated files such as initial ramdisks for
- booting Linux don’t have accidental dependencies on other paths in
- the Nix store.
-
- - [`allowedRequisites`]{#adv-attr-allowedRequisites}\
- This attribute is similar to `allowedReferences`, but it specifies
- the legal requisites of the whole closure, so all the dependencies
- recursively. For example,
-
- ```nix
- allowedRequisites = [ foobar ];
- ```
-
- enforces that the output of a derivation cannot have any other
- runtime dependency than `foobar`, and in addition it enforces that
- `foobar` itself doesn't introduce any other dependency itself.
-
- - [`disallowedReferences`]{#adv-attr-disallowedReferences}\
- The optional attribute `disallowedReferences` specifies a list of
- illegal references (dependencies) of the output of the builder. For
- example,
-
- ```nix
- disallowedReferences = [ foo ];
- ```
-
- enforces that the output of a derivation cannot have a direct
- runtime dependencies on the derivation `foo`.
-
- - [`disallowedRequisites`]{#adv-attr-disallowedRequisites}\
- This attribute is similar to `disallowedReferences`, but it
- specifies illegal requisites for the whole closure, so all the
- dependencies recursively. For example,
-
- ```nix
- disallowedRequisites = [ foobar ];
- ```
-
- enforces that the output of a derivation cannot have any runtime
- dependency on `foobar` or any other derivation depending recursively
- on `foobar`.
-
- - [`exportReferencesGraph`]{#adv-attr-exportReferencesGraph}\
- This attribute allows builders access to the references graph of
- their inputs. The attribute is a list of inputs in the Nix store
- whose references graph the builder needs to know. The value of
- this attribute should be a list of pairs `[ name1 path1 name2
- path2 ... ]`. The references graph of each *pathN* will be stored
- in a text file *nameN* in the temporary build directory. The text
- files have the format used by `nix-store --register-validity`
- (with the deriver fields left empty). For example, when the
- following derivation is built:
-
- ```nix
- derivation {
- ...
- exportReferencesGraph = [ "libfoo-graph" libfoo ];
- };
- ```
-
- the references graph of `libfoo` is placed in the file
- `libfoo-graph` in the temporary build directory.
-
- `exportReferencesGraph` is useful for builders that want to do
- something with the closure of a store path. Examples include the
- builders in NixOS that generate the initial ramdisk for booting
- Linux (a `cpio` archive containing the closure of the boot script)
- and the ISO-9660 image for the installation CD (which is populated
- with a Nix store containing the closure of a bootable NixOS
- configuration).
-
- - [`impureEnvVars`]{#adv-attr-impureEnvVars}\
- This attribute allows you to specify a list of environment variables
- that should be passed from the environment of the calling user to
- the builder. Usually, the environment is cleared completely when the
- builder is executed, but with this attribute you can allow specific
- environment variables to be passed unmodified. For example,
- `fetchurl` in Nixpkgs has the line
-
- ```nix
- impureEnvVars = [ "http_proxy" "https_proxy" ... ];
- ```
-
- to make it use the proxy server configuration specified by the user
- in the environment variables `http_proxy` and friends.
-
- This attribute is only allowed in *fixed-output derivations* (see
- below), where impurities such as these are okay since (the hash
- of) the output is known in advance. It is ignored for all other
- derivations.
-
- > **Warning**
- >
- > `impureEnvVars` implementation takes environment variables from
- > the current builder process. When a daemon is building its
- > environmental variables are used. Without the daemon, the
- > environmental variables come from the environment of the
- > `nix-build`.
-
- - [`outputHash`]{#adv-attr-outputHash}; [`outputHashAlgo`]{#adv-attr-outputHashAlgo}; [`outputHashMode`]{#adv-attr-outputHashMode}\
- These attributes declare that the derivation is a so-called
- *fixed-output derivation*, which means that a cryptographic hash of
- the output is already known in advance. When the build of a
- fixed-output derivation finishes, Lix computes the cryptographic
- hash of the output and compares it to the hash declared with these
- attributes. If there is a mismatch, the build fails.
-
- The rationale for fixed-output derivations is derivations such as
- those produced by the `fetchurl` function. This function downloads a
- file from a given URL. To ensure that the downloaded file has not
- been modified, the caller must also specify a cryptographic hash of
- the file. For example,
-
- ```nix
- fetchurl {
- url = "http://ftp.gnu.org/pub/gnu/hello/hello-2.1.1.tar.gz";
- sha256 = "1md7jsfd8pa45z73bz1kszpp01yw6x5ljkjk2hx7wl800any6465";
- }
- ```
-
- It sometimes happens that the URL of the file changes, e.g., because
- servers are reorganised or no longer available. We then must update
- the call to `fetchurl`, e.g.,
-
- ```nix
- fetchurl {
- url = "ftp://ftp.nluug.nl/pub/gnu/hello/hello-2.1.1.tar.gz";
- sha256 = "1md7jsfd8pa45z73bz1kszpp01yw6x5ljkjk2hx7wl800any6465";
- }
- ```
-
- If a `fetchurl` derivation was treated like a normal derivation, the
- output paths of the derivation and *all derivations depending on it*
- would change. For instance, if we were to change the URL of the
- Glibc source distribution in Nixpkgs (a package on which almost all
- other packages depend) massive rebuilds would be needed. This is
- unfortunate for a change which we know cannot have a real effect as
- it propagates upwards through the dependency graph.
-
- For fixed-output derivations, on the other hand, the name of the
- output path only depends on the `outputHash*` and `name` attributes,
- while all other attributes are ignored for the purpose of computing
- the output path. (The `name` attribute is included because it is
- part of the path.)
-
- As an example, here is the (simplified) Nix expression for
- `fetchurl`:
-
- ```nix
- { stdenv, curl }: # The curl program is used for downloading.
-
- { url, sha256 }:
-
- stdenv.mkDerivation {
- name = baseNameOf (toString url);
- builder = ./builder.sh;
- buildInputs = [ curl ];
-
- # This is a fixed-output derivation; the output must be a regular
- # file with SHA256 hash sha256.
- outputHashMode = "flat";
- outputHashAlgo = "sha256";
- outputHash = sha256;
-
- inherit url;
- }
- ```
-
- The `outputHashAlgo` attribute specifies the hash algorithm used to
- compute the hash. It can currently be `"sha1"`, `"sha256"` or
- `"sha512"`.
-
- The `outputHashMode` attribute determines how the hash is computed.
- It must be one of the following two values:
-
- - `"flat"`\
- The output must be a non-executable regular file. If it isn’t,
- the build fails. The hash is simply computed over the contents
- of that file (so it’s equal to what Unix commands like
- `sha256sum` or `sha1sum` produce).
-
- This is the default.
-
- - `"recursive"`\
- The hash is computed over the NAR archive dump of the output
- (i.e., the result of [`nix-store --dump`](@docroot@/command-ref/nix-store/dump.md)). In
- this case, the output can be anything, including a directory
- tree.
-
- The `outputHash` attribute, finally, must be a string containing
- the hash in either hexadecimal or base-32 notation. (See the
- [`nix-hash` command](../command-ref/nix-hash.md) for information
- about converting to and from base-32 notation.)
-
- - [`__contentAddressed`]{#adv-attr-__contentAddressed}
- > **Warning**
- > This attribute is part of an [experimental feature](@docroot@/contributing/experimental-features.md).
- >
- > To use this attribute, you must enable the
- > [`ca-derivations`](@docroot@/contributing/experimental-features.md#xp-feature-ca-derivations) experimental feature.
- > For example, in [nix.conf](../command-ref/conf-file.md) you could add:
- >
- > ```
- > extra-experimental-features = ca-derivations
- > ```
-
- If this attribute is set to `true`, then the derivation
- outputs will be stored in a content-addressed location rather than the
- traditional input-addressed one.
-
- Setting this attribute also requires setting
- [`outputHashMode`](#adv-attr-outputHashMode)
- and
- [`outputHashAlgo`](#adv-attr-outputHashAlgo)
- like for *fixed-output derivations* (see above).
-
- - [`passAsFile`]{#adv-attr-passAsFile}\
- A list of names of attributes that should be passed via files rather
- than environment variables. For example, if you have
-
- ```nix
- passAsFile = ["big"];
- big = "a very long string";
- ```
-
- then when the builder runs, the environment variable `bigPath`
- will contain the absolute path to a temporary file containing `a
- very long string`. That is, for any attribute *x* listed in
- `passAsFile`, Lix will pass an environment variable `xPath`
- holding the path of the file containing the value of attribute
- *x*. This is useful when you need to pass large strings to a
- builder, since most operating systems impose a limit on the size
- of the environment (typically, a few hundred kilobyte).
-
- - [`preferLocalBuild`]{#adv-attr-preferLocalBuild}\
- If this attribute is set to `true` and [distributed building is
- enabled](../advanced-topics/distributed-builds.md), then, if
- possible, the derivation will be built locally instead of forwarded
- to a remote machine. This is appropriate for trivial builders
- where the cost of doing a download or remote build would exceed
- the cost of building locally.
-
- - [`allowSubstitutes`]{#adv-attr-allowSubstitutes}\
- If this attribute is set to `false`, then Lix will always build this
- derivation; it will not try to substitute its outputs. This is
- useful for very trivial derivations (such as `writeText` in Nixpkgs)
- that are cheaper to build than to substitute from a binary cache.
-
- You may disable the effects of this attibute by enabling the
- `always-allow-substitutes` configuration option in Lix.
-
- > **Note**
- >
- > You need to have a builder configured which satisfies the
- > derivation’s `system` attribute, since the derivation cannot be
- > substituted. Thus it is usually a good idea to align `system` with
- > `builtins.currentSystem` when setting `allowSubstitutes` to
- > `false`. For most trivial derivations this should be the case.
-
- - [`__structuredAttrs`]{#adv-attr-structuredAttrs}\
- If the special attribute `__structuredAttrs` is set to `true`, the other derivation
- attributes are serialised into a file in JSON format. The environment variable
- `NIX_ATTRS_JSON_FILE` points to the exact location of that file both in a build
- and a [`nix-shell`](../command-ref/nix-shell.md). This obviates the need for
- [`passAsFile`](#adv-attr-passAsFile) since JSON files have no size restrictions,
- unlike process environments.
-
- It also makes it possible to tweak derivation settings in a structured way; see
- [`outputChecks`](#adv-attr-outputChecks) for example.
-
- As a convenience to Bash builders,
- Lix writes a script that initialises shell variables
- corresponding to all attributes that are representable in Bash. The
- environment variable `NIX_ATTRS_SH_FILE` points to the exact
- location of the script, both in a build and a
- [`nix-shell`](../command-ref/nix-shell.md). This includes non-nested
- (associative) arrays. For example, the attribute `hardening.format = true`
- ends up as the Bash associative array element `${hardening[format]}`.
-
- - [`outputChecks`]{#adv-attr-outputChecks}\
- When using [structured attributes](#adv-attr-structuredAttrs), the `outputChecks`
- attribute allows defining checks per-output.
-
- In addition to
- [`allowedReferences`](#adv-attr-allowedReferences), [`allowedRequisites`](#adv-attr-allowedRequisites),
- [`disallowedReferences`](#adv-attr-disallowedReferences) and [`disallowedRequisites`](#adv-attr-disallowedRequisites),
- the following attributes are available:
-
- - `maxSize` defines the maximum size of the resulting [store object](../glossary.md#gloss-store-object).
- - `maxClosureSize` defines the maximum size of the output's closure.
- - `ignoreSelfRefs` controls whether self-references should be considered when
- checking for allowed references/requisites.
-
- Example:
-
- ```nix
- __structuredAttrs = true;
-
- outputChecks.out = {
- # The closure of 'out' must not be larger than 256 MiB.
- maxClosureSize = 256 * 1024 * 1024;
-
- # It must not refer to the C compiler or to the 'dev' output.
- disallowedRequisites = [ stdenv.cc "dev" ];
- };
-
- outputChecks.dev = {
- # The 'dev' output must not be larger than 128 KiB.
- maxSize = 128 * 1024;
- };
- ```
-
- - [`unsafeDiscardReferences`]{#adv-attr-unsafeDiscardReferences}\
-
- When using [structured attributes](#adv-attr-structuredAttrs), the
- attribute `unsafeDiscardReferences` is an attribute set with a boolean value for each output name.
- If set to `true`, it disables scanning the output for runtime dependencies.
-
- Example:
-
- ```nix
- __structuredAttrs = true;
- unsafeDiscardReferences.out = true;
- ```
-
- This is useful, for example, when generating self-contained filesystem images with
- their own embedded Nix store: hashes found inside such an image refer
- to the embedded store and not to the host's Nix store.
diff --git a/doc/manual/src/language/builtin-constants.md b/doc/manual/src/language/builtin-constants.md
deleted file mode 100644
index 74e87146f..000000000
--- a/doc/manual/src/language/builtin-constants.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Built-in Constants
-
-These constants are built into the Nix language evaluator:
-
-
-
-{{#include @generated@/language/builtin-constants.md}}
-
-
diff --git a/doc/manual/src/language/builtins.md b/doc/manual/src/language/builtins.md
deleted file mode 100644
index 2a3972f05..000000000
--- a/doc/manual/src/language/builtins.md
+++ /dev/null
@@ -1,20 +0,0 @@
-# Built-in Functions
-
-This section lists the functions built into the Nix language evaluator.
-All built-in functions are available through the global [`builtins`](./builtin-constants.md#builtins-builtins) constant.
-
-For convenience, some built-ins can be accessed directly:
-
-- [`derivation`](#builtins-derivation)
-- [`import`](#builtins-import)
-- [`abort`](#builtins-abort)
-- [`throw`](#builtins-throw)
-
-
- derivation attrsderivation is described in
- its own section.
diff --git a/doc/manual/src/language/constructs.md b/doc/manual/src/language/constructs.md
deleted file mode 100644
index 2a527770a..000000000
--- a/doc/manual/src/language/constructs.md
+++ /dev/null
@@ -1,382 +0,0 @@
-# Language Constructs
-
-## Recursive sets
-
-Recursive sets are like normal [attribute sets](./values.md#attribute-set), but the attributes can refer to each other.
-
-> *rec-attrset* = `rec {` [ *name* `=` *expr* `;` `]`... `}`
-
-Example:
-
-```nix
-rec {
- x = y;
- y = 123;
-}.x
-```
-
-This evaluates to `123`.
-
-Note that without `rec` the binding `x = y;` would
-refer to the variable `y` in the surrounding scope, if one exists, and
-would be invalid if no such variable exists. That is, in a normal
-(non-recursive) set, attributes are not added to the lexical scope; in a
-recursive set, they are.
-
-Recursive sets of course introduce the danger of infinite recursion. For
-example, the expression
-
-```nix
-rec {
- x = y;
- y = x;
-}.x
-```
-
-will crash with an `infinite recursion encountered` error message.
-
-## Let-expressions
-
-A let-expression allows you to define local variables for an expression.
-
-> *let-in* = `let` [ *identifier* = *expr* ]... `in` *expr*
-
-Example:
-
-```nix
-let
- x = "foo";
- y = "bar";
-in x + y
-```
-
-This evaluates to `"foobar"`.
-
-## Inheriting attributes
-
-When defining an [attribute set](./values.md#attribute-set) or in a [let-expression](#let-expressions) it is often convenient to copy variables from the surrounding lexical scope (e.g., when you want to propagate attributes).
-This can be shortened using the `inherit` keyword.
-
-Example:
-
-```nix
-let x = 123; in
-{
- inherit x;
- y = 456;
-}
-```
-
-is equivalent to
-
-```nix
-let x = 123; in
-{
- x = x;
- y = 456;
-}
-```
-
-and both evaluate to `{ x = 123; y = 456; }`.
-
-> **Note**
->
-> This works because `x` is added to the lexical scope by the `let` construct.
-
-It is also possible to inherit attributes from another attribute set.
-
-Example:
-
-In this fragment from `all-packages.nix`,
-
-```nix
-graphviz = (import ../tools/graphics/graphviz) {
- inherit fetchurl stdenv libpng libjpeg expat x11 yacc;
- inherit (xorg) libXaw;
-};
-
-xorg = {
- libX11 = ...;
- libXaw = ...;
- ...
-}
-
-libpng = ...;
-libjpg = ...;
-...
-```
-
-the set used in the function call to the function defined in
-`../tools/graphics/graphviz` inherits a number of variables from the
-surrounding scope (`fetchurl` ... `yacc`), but also inherits `libXaw`
-(the X Athena Widgets) from the `xorg` set.
-
-Summarizing the fragment
-
-```nix
-...
-inherit x y z;
-inherit (src-set) a b c;
-...
-```
-
-is equivalent to
-
-```nix
-...
-x = x; y = y; z = z;
-a = src-set.a; b = src-set.b; c = src-set.c;
-...
-```
-
-when used while defining local variables in a let-expression or while
-defining a set.
-
-## Functions
-
-Functions have the following form:
-
-```nix
-pattern: body
-```
-
-The pattern specifies what the argument of the function must look like,
-and binds variables in the body to (parts of) the argument. There are
-three kinds of patterns:
-
- - If a pattern is a single identifier, then the function matches any
- argument. Example:
-
- ```nix
- let negate = x: !x;
- concat = x: y: x + y;
- in if negate true then concat "foo" "bar" else ""
- ```
-
- Note that `concat` is a function that takes one argument and returns
- a function that takes another argument. This allows partial
- parameterisation (i.e., only filling some of the arguments of a
- function); e.g.,
-
- ```nix
- map (concat "foo") [ "bar" "bla" "abc" ]
- ```
-
- evaluates to `[ "foobar" "foobla" "fooabc" ]`.
-
- - A *set pattern* of the form `{ name1, name2, …, nameN }` matches a
- set containing the listed attributes, and binds the values of those
- attributes to variables in the function body. For example, the
- function
-
- ```nix
- { x, y, z }: z + y + x
- ```
-
- can only be called with a set containing exactly the attributes `x`,
- `y` and `z`. No other attributes are allowed. If you want to allow
- additional arguments, you can use an ellipsis (`...`):
-
- ```nix
- { x, y, z, ... }: z + y + x
- ```
-
- This works on any set that contains at least the three named
- attributes.
-
- It is possible to provide *default values* for attributes, in
- which case they are allowed to be missing. A default value is
- specified by writing `name ? e`, where *e* is an arbitrary
- expression. For example,
-
- ```nix
- { x, y ? "foo", z ? "bar" }: z + y + x
- ```
-
- specifies a function that only requires an attribute named `x`, but
- optionally accepts `y` and `z`.
-
- - An `@`-pattern provides a means of referring to the whole value
- being matched:
-
- ```nix
- args@{ x, y, z, ... }: z + y + x + args.a
- ```
-
- but can also be written as:
-
- ```nix
- { x, y, z, ... } @ args: z + y + x + args.a
- ```
-
- Here `args` is bound to the argument *as passed*, which is further
- matched against the pattern `{ x, y, z, ... }`.
- The `@`-pattern makes mainly sense with an ellipsis(`...`) as
- you can access attribute names as `a`, using `args.a`, which was
- given as an additional attribute to the function.
-
- > **Warning**
- >
- > `args@` binds the name `args` to the attribute set that is passed to the function.
- > In particular, `args` does *not* include any default values specified with `?` in the function's set pattern.
- >
- > For instance
- >
- > ```nix
- > let
- > f = args@{ a ? 23, ... }: [ a args ];
- > in
- > f {}
- > ```
- >
- > is equivalent to
- >
- > ```nix
- > let
- > f = args @ { ... }: [ (args.a or 23) args ];
- > in
- > f {}
- > ```
- >
- > and both expressions will evaluate to:
- >
- > ```nix
- > [ 23 {} ]
- > ```
-
-Note that functions do not have names. If you want to give them a name,
-you can bind them to an attribute, e.g.,
-
-```nix
-let concat = { x, y }: x + y;
-in concat { x = "foo"; y = "bar"; }
-```
-
-## Conditionals
-
-Conditionals look like this:
-
-```nix
-if e1 then e2 else e3
-```
-
-where *e1* is an expression that should evaluate to a Boolean value
-(`true` or `false`).
-
-## Assertions
-
-Assertions are generally used to check that certain requirements on or
-between features and dependencies hold. They look like this:
-
-```nix
-assert e1; e2
-```
-
-where *e1* is an expression that should evaluate to a Boolean value. If
-it evaluates to `true`, *e2* is returned; otherwise expression
-evaluation is aborted and a backtrace is printed.
-
-Here is a Nix expression for the Subversion package that shows how
-assertions can be used:.
-
-```nix
-{ localServer ? false
-, httpServer ? false
-, sslSupport ? false
-, pythonBindings ? false
-, javaSwigBindings ? false
-, javahlBindings ? false
-, stdenv, fetchurl
-, openssl ? null, httpd ? null, db4 ? null, expat, swig ? null, j2sdk ? null
-}:
-
-assert localServer -> db4 != null; ①
-assert httpServer -> httpd != null && httpd.expat == expat; ②
-assert sslSupport -> openssl != null && (httpServer -> httpd.openssl == openssl); ③
-assert pythonBindings -> swig != null && swig.pythonSupport;
-assert javaSwigBindings -> swig != null && swig.javaSupport;
-assert javahlBindings -> j2sdk != null;
-
-stdenv.mkDerivation {
- name = "subversion-1.1.1";
- ...
- openssl = if sslSupport then openssl else null; ④
- ...
-}
-```
-
-The points of interest are:
-
-1. This assertion states that if Subversion is to have support for
- local repositories, then Berkeley DB is needed. So if the Subversion
- function is called with the `localServer` argument set to `true` but
- the `db4` argument set to `null`, then the evaluation fails.
-
- Note that `->` is the [logical
- implication](https://en.wikipedia.org/wiki/Truth_table#Logical_implication)
- Boolean operation.
-
-2. This is a more subtle condition: if Subversion is built with Apache
- (`httpServer`) support, then the Expat library (an XML library) used
- by Subversion should be same as the one used by Apache. This is
- because in this configuration Subversion code ends up being linked
- with Apache code, and if the Expat libraries do not match, a build-
- or runtime link error or incompatibility might occur.
-
-3. This assertion says that in order for Subversion to have SSL support
- (so that it can access `https` URLs), an OpenSSL library must be
- passed. Additionally, it says that *if* Apache support is enabled,
- then Apache's OpenSSL should match Subversion's. (Note that if
- Apache support is not enabled, we don't care about Apache's
- OpenSSL.)
-
-4. The conditional here is not really related to assertions, but is
- worth pointing out: it ensures that if SSL support is disabled, then
- the Subversion derivation is not dependent on OpenSSL, even if a
- non-`null` value was passed. This prevents an unnecessary rebuild of
- Subversion if OpenSSL changes.
-
-## With-expressions
-
-A *with-expression*,
-
-```nix
-with e1; e2
-```
-
-introduces the set *e1* into the lexical scope of the expression *e2*.
-For instance,
-
-```nix
-let as = { x = "foo"; y = "bar"; };
-in with as; x + y
-```
-
-evaluates to `"foobar"` since the `with` adds the `x` and `y` attributes
-of `as` to the lexical scope in the expression `x + y`. The most common
-use of `with` is in conjunction with the `import` function. E.g.,
-
-```nix
-with (import ./definitions.nix); ...
-```
-
-makes all attributes defined in the file `definitions.nix` available as
-if they were defined locally in a `let`-expression.
-
-The bindings introduced by `with` do not shadow bindings introduced by
-other means, e.g.
-
-```nix
-let a = 3; in with { a = 1; }; let a = 4; in with { a = 2; }; ...
-```
-
-establishes the same scope as
-
-```nix
-let a = 1; in let a = 2; in let a = 3; in let a = 4; in ...
-```
-
-## Comments
-
-Comments can be single-line, started with a `#` character, or
-inline/multi-line, enclosed within `/* ... */`.
diff --git a/doc/manual/src/language/derivations.md b/doc/manual/src/language/derivations.md
deleted file mode 100644
index c10e8149d..000000000
--- a/doc/manual/src/language/derivations.md
+++ /dev/null
@@ -1,166 +0,0 @@
-# Derivations
-
-The most important built-in function is `derivation`, which is used to
-describe a single derivation (a build task). It takes as input a set,
-the attributes of which specify the inputs of the build.
-
- - There must be an attribute named [`system`]{#attr-system} whose value must be a
- string specifying a Nix system type, such as `"i686-linux"` or
- `"x86_64-darwin"`. (To figure out your system type, run `nix -vv
- --version`.) The build can only be performed on a machine and
- operating system matching the system type. (Nix can automatically
- [forward builds for other
- platforms](../advanced-topics/distributed-builds.md) by forwarding
- them to other machines.)
-
- - There must be an attribute named `name` whose value must be a
- string. This is used as a symbolic name for the package by
- `nix-env`, and it is appended to the output paths of the derivation.
-
- - There must be an attribute named [`builder`]{#attr-builder} that identifies the
- program that is executed to perform the build. It can be either a
- derivation or a source (a local file reference, e.g.,
- `./builder.sh`).
-
- - Every attribute is passed as an environment variable to the builder.
- Attribute values are translated to environment variables as follows:
-
- - Strings and numbers are just passed verbatim.
-
- - A *path* (e.g., `../foo/sources.tar`) causes the referenced file
- to be copied to the store; its location in the store is put in
- the environment variable. The idea is that all sources should
- reside in the Nix store, since all inputs to a derivation should
- reside in the Nix store.
-
- - A *derivation* causes that derivation to be built prior to the
- present derivation; its default output path is put in the
- environment variable.
-
- - Lists of the previous types are also allowed. They are simply
- concatenated, separated by spaces.
-
- - `true` is passed as the string `1`, `false` and `null` are
- passed as an empty string.
-
- - The optional attribute `args` specifies command-line arguments to be
- passed to the builder. It should be a list.
-
- - The optional attribute `outputs` specifies a list of symbolic
- outputs of the derivation. By default, a derivation produces a
- single output path, denoted as `out`. However, derivations can
- produce multiple output paths. This is useful because it allows
- outputs to be downloaded or garbage-collected separately. For
- instance, imagine a library package that provides a dynamic library,
- header files, and documentation. A program that links against the
- library doesn’t need the header files and documentation at runtime,
- and it doesn’t need the documentation at build time. Thus, the
- library package could specify:
-
- ```nix
- outputs = [ "lib" "headers" "doc" ];
- ```
-
- This will cause Lix to pass environment variables `lib`, `headers`
- and `doc` to the builder containing the intended store paths of each
- output. The builder would typically do something like
-
- ```bash
- ./configure \
- --libdir=$lib/lib \
- --includedir=$headers/include \
- --docdir=$doc/share/doc
- ```
-
- for an Autoconf-style package. You can refer to each output of a
- derivation by selecting it as an attribute, e.g.
-
- ```nix
- buildInputs = [ pkg.lib pkg.headers ];
- ```
-
- The first element of `outputs` determines the *default output*.
- Thus, you could also write
-
- ```nix
- buildInputs = [ pkg pkg.headers ];
- ```
-
- since `pkg` is equivalent to `pkg.lib`.
-
-The function `mkDerivation` in the Nixpkgs standard environment is a
-wrapper around `derivation` that adds a default value for `system` and
-always uses Bash as the builder, to which the supplied builder is passed
-as a command-line argument. See the Nixpkgs manual for details.
-
-The builder is executed as follows:
-
- - A temporary directory is created under the directory specified by
- `TMPDIR` (default `/tmp`) where the build will take place. The
- current directory is changed to this directory.
-
- - The environment is cleared and set to the derivation attributes, as
- specified above.
-
- - In addition, the following variables are set:
-
- - `NIX_BUILD_TOP` contains the path of the temporary directory for
- this build.
-
- - Also, `TMPDIR`, `TEMPDIR`, `TMP`, `TEMP` are set to point to the
- temporary directory. This is to prevent the builder from
- accidentally writing temporary files anywhere else. Doing so
- might cause interference by other processes.
-
- - `PATH` is set to `/path-not-set` to prevent shells from
- initialising it to their built-in default value.
-
- - `HOME` is set to `/homeless-shelter` to prevent programs from
- using `/etc/passwd` or the like to find the user's home
- directory, which could cause impurity. Usually, when `HOME` is
- set, it is used as the location of the home directory, even if
- it points to a non-existent path.
-
- - `NIX_STORE` is set to the path of the top-level Nix store
- directory (typically, `/nix/store`).
-
- - `NIX_ATTRS_JSON_FILE` & `NIX_ATTRS_SH_FILE` if `__structuredAttrs`
- is set to `true` for the dervation. A detailed explanation of this
- behavior can be found in the
- [section about structured attrs](./advanced-attributes.md#adv-attr-structuredAttrs).
-
- - For each output declared in `outputs`, the corresponding
- environment variable is set to point to the intended path in the
- Nix store for that output. Each output path is a concatenation
- of the cryptographic hash of all build inputs, the `name`
- attribute and the output name. (The output name is omitted if
- it’s `out`.)
-
- - If an output path already exists, it is removed. Also, locks are
- acquired to prevent multiple Lix instances from performing the same
- build at the same time.
-
- - A log of the combined standard output and error is written to
- `/nix/var/log/nix`.
-
- - The builder is executed with the arguments specified by the
- attribute `args`. If it exits with exit code 0, it is considered to
- have succeeded.
-
- - The temporary directory is removed (unless the `-K` option was
- specified).
-
- - If the build was successful, Lix scans each output path for
- references to input paths by looking for the hash parts of the input
- paths. Since these are potential runtime dependencies, Lix registers
- them as dependencies of the output paths.
-
- - After the build, Lix sets the last-modified timestamp on all files
- in the build result to 1 (00:00:01 1/1/1970 UTC), sets the group to
- the default group, and sets the mode of the file to 0444 or 0555
- (i.e., read-only, with execute permission enabled if the file was
- originally executable). Note that possible `setuid` and `setgid`
- bits are cleared. Setuid and setgid programs are not currently
- supported by Lix. This is because the Lix archives used in
- deployment have no concept of ownership information, and because it
- makes the build result dependent on the user performing the build.
diff --git a/doc/manual/src/language/index.md b/doc/manual/src/language/index.md
deleted file mode 100644
index 29950a52d..000000000
--- a/doc/manual/src/language/index.md
+++ /dev/null
@@ -1,580 +0,0 @@
-# Nix Language
-
-The Nix language is designed for conveniently creating and composing *derivations* – precise descriptions of how contents of existing files are used to derive new files.
-It is:
-
-- *domain-specific*
-
- It comes with [built-in functions](@docroot@/language/builtins.md) to integrate with the Nix store, which manages files and performs the derivations declared in the Nix language.
-
-- *declarative*
-
- There is no notion of executing sequential steps.
- Dependencies between operations are established only through data.
-
-- *pure*
-
- Values cannot change during computation.
- Functions always produce the same output if their input does not change.
-
-- *functional*
-
- Functions are like any other value.
- Functions can be assigned to names, taken as arguments, or returned by functions.
-
-- *lazy*
-
- Values are only computed when they are needed.
-
-- *dynamically typed*
-
- Type errors are only detected when expressions are evaluated.
-
-# Overview
-
-This is an incomplete overview of language features, by example.
-
-
-
-
- Example
-
-
- Description
-
-
-
-
-
-
- *Basic values*
-
-
-
-
-
-
-
-
-
-
-
-
- `"hello world"`
-
-
-
-
- A string
-
-
-
-
-
-
- ```
- ''
- multi
- line
- string
- ''
- ```
-
-
-
-
- A multi-line string. Strips common prefixed whitespace. Evaluates to `"multi\n line\n string"`.
-
-
-
-
-
-
- `"hello ${ { a = "world"; }.a }"`
-
- `"1 2 ${toString 3}"`
-
- `"${pkgs.bash}/bin/sh"`
-
-
-
-
- String interpolation (expands to `"hello world"`, `"1 2 3"`, `"/nix/store/-bash-/bin/sh"`)
-
-
-
-
-
-
- `true`, `false`
-
-
-
-
- Booleans
-
-
-
-
-
-
- `null`
-
-
-
-
- Null value
-
-
-
-
-
-
- `123`
-
-
-
-
- An integer
-
-
-
-
-
-
- `3.141`
-
-
-
-
- A floating point number
-
-
-
-
-
-
- `/etc`
-
-
-
-
- An absolute path
-
-
-
-
-
-
- `./foo.png`
-
-
-
-
- A path relative to the file containing this Nix expression
-
-
-
-
-
-
- `~/.config`
-
-
-
-
- A home path. Evaluates to the `"/.config"`.
-
-
-
-
-
-
- ``
-
-
-
-
- Search path for Nix files. Value determined by [`$NIX_PATH` environment variable](../command-ref/env-common.md#env-NIX_PATH).
-
-
-
-
-
-
- *Compound values*
-
-
-
-
-
-
-
-
-
-
-
- `{ x = 1; y = 2; }`
-
-
-
-
- A set with attributes named `x` and `y`
-
-
-
-
-
-
- `{ foo.bar = 1; }`
-
-
-
-
- A nested set, equivalent to `{ foo = { bar = 1; }; }`
-
-
-
-
-
-
- `rec { x = "foo"; y = x + "bar"; }`
-
-
-
-
- A recursive set, equivalent to `{ x = "foo"; y = "foobar"; }`
-
-
-
-
-
-
- `[ "foo" "bar" "baz" ]`
-
- `[ 1 2 3 ]`
-
- `[ (f 1) { a = 1; b = 2; } [ "c" ] ]`
-
-
-
-
- Lists with three elements.
-
-
-
-
-
-
- *Operators*
-
-
-
-
-
-
-
-
-
-
-
- `"foo" + "bar"`
-
-
-
-
- String concatenation
-
-
-
-
-
-
- `1 + 2`
-
-
-
-
- Integer addition
-
-
-
-
-
-
- `"foo" == "f" + "oo"`
-
-
-
-
- Equality test (evaluates to `true`)
-
-
-
-
-
-
- `"foo" != "bar"`
-
-
-
-
- Inequality test (evaluates to `true`)
-
-
-
-
-
-
- `!true`
-
-
-
-
- Boolean negation
-
-
-
-
-
-
- `{ x = 1; y = 2; }.x`
-
-
-
-
- Attribute selection (evaluates to `1`)
-
-
-
-
-
-
- `{ x = 1; y = 2; }.z or 3`
-
-
-
-
- Attribute selection with default (evaluates to `3`)
-
-
-
-
-
-
- `{ x = 1; y = 2; } // { z = 3; }`
-
-
-
-
- Merge two sets (attributes in the right-hand set taking precedence)
-
-
-
-
-
-
- *Control structures*
-
-
-
-
-
-
-
-
-
-
-
- `if 1 + 1 == 2 then "yes!" else "no!"`
-
-
-
-
- Conditional expression
-
-
-
-
-
-
- `assert 1 + 1 == 2; "yes!"`
-
-
-
-
- Assertion check (evaluates to `"yes!"`).
-
-
-
-
-
-
- `let x = "foo"; y = "bar"; in x + y`
-
-
-
-
- Variable definition
-
-
-
-
-
-
- `with builtins; head [ 1 2 3 ]`
-
-
-
-
- Add all attributes from the given set to the scope (evaluates to `1`)
-
-
-
-
-
-
- *Functions (lambdas)*
-
-
-
-
-
-
-
-
-
-
-
- `x: x + 1`
-
-
-
-
- A function that expects an integer and returns it increased by 1
-
-
-
-
-
-
- `x: y: x + y`
-
-
-
-
- Curried function, equivalent to `x: (y: x + y)`. Can be used like a function that takes two arguments and returns their sum.
-
-
-
-
-
-
- `(x: x + 1) 100`
-
-
-
-
- A function call (evaluates to 101)
-
-
-
-
-
-
- `let inc = x: x + 1; in inc (inc (inc 100))`
-
-
-
-
- A function bound to a variable and subsequently called by name (evaluates to 103)
-
-
-
-
-
-
- `{ x, y }: x + y`
-
-
-
-
- A function that expects a set with required attributes `x` and `y` and concatenates them
-
-
-
-
-
-
- `{ x, y ? "bar" }: x + y`
-
-
-
-
- A function that expects a set with required attribute `x` and optional `y`, using `"bar"` as default value for `y`
-
-
-
-
-
-
- `{ x, y, ... }: x + y`
-
-
-
-
- A function that expects a set with required attributes `x` and `y` and ignores any other attributes
-
-
-
-
-
-
- `{ x, y } @ args: x + y`
-
- `args @ { x, y }: x + y`
-
-
-
-
- A function that expects a set with required attributes `x` and `y`, and binds the whole set to `args`
-
-
-
-
-
-
- *Built-in functions*
-
-
-
-
-
-
-
-
-
-
-
- `import ./foo.nix`
-
-
-
-
- Load and return Nix expression in given file
-
-
-
-
-
-
- `map (x: x + x) [ 1 2 3 ]`
-
-
-
-
- Apply a function to every element of a list (evaluates to `[ 2 4 6 ]`)
-
-
-
-
diff --git a/doc/manual/src/language/meson.build b/doc/manual/src/language/meson.build
deleted file mode 100644
index bc0d147f3..000000000
--- a/doc/manual/src/language/meson.build
+++ /dev/null
@@ -1,27 +0,0 @@
-builtins_md = custom_target(
- command : nix_eval_for_docs + [
- '--expr',
- 'import @INPUT0@ (builtins.fromJSON (builtins.readFile @INPUT1@)).builtins',
- ],
- capture : true,
- input : [
- '../../generate-builtins.nix',
- language_json,
- ],
- output : 'builtins.md',
- env : nix_env_for_docs,
-)
-
-builtin_constants_md = custom_target(
- command : nix_eval_for_docs + [
- '--expr',
- 'import @INPUT0@ (builtins.fromJSON (builtins.readFile @INPUT1@)).constants',
- ],
- capture : true,
- input : [
- '../../generate-builtin-constants.nix',
- language_json,
- ],
- output : 'builtin-constants.md',
- env : nix_env_for_docs,
-)
diff --git a/doc/manual/src/language/operators.md b/doc/manual/src/language/operators.md
deleted file mode 100644
index 418d0349f..000000000
--- a/doc/manual/src/language/operators.md
+++ /dev/null
@@ -1,163 +0,0 @@
-# Operators
-
-| Name | Syntax | Associativity | Precedence |
-|----------------------------------------|--------------------------------------------|---------------|------------|
-| [Attribute selection] | *attrset* `.` *attrpath* \[ `or` *expr* \] | none | 1 |
-| Function application | *func* *expr* | left | 2 |
-| [Arithmetic negation][arithmetic] | `-` *number* | none | 3 |
-| [Has attribute] | *attrset* `?` *attrpath* | none | 4 |
-| List concatenation | *list* `++` *list* | right | 5 |
-| [Multiplication][arithmetic] | *number* `*` *number* | left | 6 |
-| [Division][arithmetic] | *number* `/` *number* | left | 6 |
-| [Subtraction][arithmetic] | *number* `-` *number* | left | 7 |
-| [Addition][arithmetic] | *number* `+` *number* | left | 7 |
-| [String concatenation] | *string* `+` *string* | left | 7 |
-| [Path concatenation] | *path* `+` *path* | left | 7 |
-| [Path and string concatenation] | *path* `+` *string* | left | 7 |
-| [String and path concatenation] | *string* `+` *path* | left | 7 |
-| Logical negation (`NOT`) | `!` *bool* | none | 8 |
-| [Update] | *attrset* `//` *attrset* | right | 9 |
-| [Less than][Comparison] | *expr* `<` *expr* | none | 10 |
-| [Less than or equal to][Comparison] | *expr* `<=` *expr* | none | 10 |
-| [Greater than][Comparison] | *expr* `>` *expr* | none | 10 |
-| [Greater than or equal to][Comparison] | *expr* `>=` *expr* | none | 10 |
-| [Equality] | *expr* `==` *expr* | none | 11 |
-| Inequality | *expr* `!=` *expr* | none | 11 |
-| Logical conjunction (`AND`) | *bool* `&&` *bool* | left | 12 |
-| Logical disjunction (`OR`) | *bool* \|\| *bool* | left | 13 |
-| [Logical implication] | *bool* `->` *bool* | none | 14 |
-
-[string]: ./values.md#type-string
-[path]: ./values.md#type-path
-[number]: ./values.md#type-number
-[list]: ./values.md#list
-[attribute set]: ./values.md#attribute-set
-
-## Attribute selection
-
-> *attrset* `.` *attrpath* \[ `or` *expr* \]
-
-Select the attribute denoted by attribute path *attrpath* from [attribute set] *attrset*.
-If the attribute doesn’t exist, return the *expr* after `or` if provided, otherwise abort evaluation.
-
-An attribute path is a dot-separated list of [attribute names](./values.md#attribute-set).
-
-> *attrpath* = *name* [ `.` *name* ]...
-
-[Attribute selection]: #attribute-selection
-
-## Has attribute
-
-> *attrset* `?` *attrpath*
-
-Test whether [attribute set] *attrset* contains the attribute denoted by *attrpath*.
-The result is a [Boolean] value.
-
-[Boolean]: ./values.md#type-boolean
-
-[Has attribute]: #has-attribute
-
-## Arithmetic
-
-Numbers are type-compatible:
-Pure integer operations will always return integers, whereas any operation involving at least one floating point number return a floating point number.
-
-See also [Comparison] and [Equality].
-
-The `+` operator is overloaded to also work on strings and paths.
-
-[arithmetic]: #arithmetic
-
-## String concatenation
-
-> *string* `+` *string*
-
-Concatenate two [string]s and merge their string contexts.
-
-[String concatenation]: #string-concatenation
-
-## Path concatenation
-
-> *path* `+` *path*
-
-Concatenate two [path]s.
-The result is a path.
-
-[Path concatenation]: #path-concatenation
-
-## Path and string concatenation
-
-> *path* + *string*
-
-Concatenate *[path]* with *[string]*.
-The result is a path.
-
-> **Note**
->
-> The string must not have a string context that refers to a [store path].
-
-[Path and string concatenation]: #path-and-string-concatenation
-
-## String and path concatenation
-
-> *string* + *path*
-
-Concatenate *[string]* with *[path]*.
-The result is a string.
-
-> **Important**
->
-> The file or directory at *path* must exist and is copied to the [store].
-> The path appears in the result as the corresponding [store path].
-
-[store path]: ../glossary.md#gloss-store-path
-[store]: ../glossary.md#gloss-store
-
-[String and path concatenation]: #string-and-path-concatenation
-
-## Update
-
-> *attrset1* // *attrset2*
-
-Update [attribute set] *attrset1* with names and values from *attrset2*.
-
-The returned attribute set will have of all the attributes in *attrset1* and *attrset2*.
-If an attribute name is present in both, the attribute value from the latter is taken.
-
-[Update]: #update
-
-## Comparison
-
-Comparison is
-
-- [arithmetic] for [number]s
-- lexicographic for [string]s and [path]s
-- item-wise lexicographic for [list]s:
- elements at the same index in both lists are compared according to their type and skipped if they are equal.
-
-All comparison operators are implemented in terms of `<`, and the following equivalencies hold:
-
-| comparison | implementation |
-|--------------|-----------------------|
-| *a* `<=` *b* | `! (` *b* `<` *a* `)` |
-| *a* `>` *b* | *b* `<` *a* |
-| *a* `>=` *b* | `! (` *a* `<` *b* `)` |
-
-[Comparison]: #comparison-operators
-
-## Equality
-
-- [Attribute sets][attribute set] and [list]s are compared recursively, and therefore are fully evaluated.
-- Comparison of [function]s always returns `false`.
-- Numbers are type-compatible, see [arithmetic] operators.
-- Floating point numbers only differ up to a limited precision.
-
-[function]: ./constructs.md#functions
-
-[Equality]: #equality
-
-## Logical implication
-
-Equivalent to `!`*b1* `||` *b2*.
-
-[Logical implication]: #logical-implication
diff --git a/doc/manual/src/language/string-interpolation.md b/doc/manual/src/language/string-interpolation.md
deleted file mode 100644
index ddc6b8230..000000000
--- a/doc/manual/src/language/string-interpolation.md
+++ /dev/null
@@ -1,82 +0,0 @@
-# String interpolation
-
-String interpolation is a language feature where a [string], [path], or [attribute name] can contain expressions enclosed in `${ }` (dollar-sign with curly brackets).
-
-Such a string is an *interpolated string*, and an expression inside is an *interpolated expression*.
-
-Interpolated expressions must evaluate to one of the following:
-
-- a [string]
-- a [path]
-- a [derivation]
-
-[string]: ./values.md#type-string
-[path]: ./values.md#type-path
-[attribute name]: ./values.md#attribute-set
-[derivation]: ../glossary.md#gloss-derivation
-
-## Examples
-
-### String
-
-Rather than writing
-
-```nix
-"--with-freetype2-library=" + freetype + "/lib"
-```
-
-(where `freetype` is a [derivation]), you can instead write
-
-```nix
-"--with-freetype2-library=${freetype}/lib"
-```
-
-The latter is automatically translated to the former.
-
-A more complicated example (from the Nix expression for [Qt](http://www.trolltech.com/products/qt)):
-
-```nix
-configureFlags = "
- -system-zlib -system-libpng -system-libjpeg
- ${if openglSupport then "-dlopen-opengl
- -L${mesa}/lib -I${mesa}/include
- -L${libXmu}/lib -I${libXmu}/include" else ""}
- ${if threadSupport then "-thread" else "-no-thread"}
-";
-```
-
-Note that Nix expressions and strings can be arbitrarily nested;
-in this case the outer string contains various interpolated expressions that themselves contain strings (e.g., `"-thread"`), some of which in turn contain interpolated expressions (e.g., `${mesa}`).
-
-### Path
-
-Rather than writing
-
-```nix
-./. + "/" + foo + "-" + bar + ".nix"
-```
-
-or
-
-```nix
-./. + "/${foo}-${bar}.nix"
-```
-
-you can instead write
-
-```nix
-./${foo}-${bar}.nix
-```
-
-### Attribute name
-
-Attribute names can be created dynamically with string interpolation:
-
-```nix
-let name = "foo"; in
-{
- ${name} = "bar";
-}
-```
-
- { foo = "bar"; }
diff --git a/doc/manual/src/language/values.md b/doc/manual/src/language/values.md
deleted file mode 100644
index 2ae3e143a..000000000
--- a/doc/manual/src/language/values.md
+++ /dev/null
@@ -1,267 +0,0 @@
-# Data Types
-
-## Primitives
-
-- String
-
- *Strings* can be written in three ways.
-
- The most common way is to enclose the string between double quotes,
- e.g., `"foo bar"`. Strings can span multiple lines. The special
- characters `"` and `\` and the character sequence `${` must be
- escaped by prefixing them with a backslash (`\`). Newlines, carriage
- returns and tabs can be written as `\n`, `\r` and `\t`,
- respectively.
-
- You can include the results of other expressions into a string by enclosing them in `${ }`, a feature known as [string interpolation].
-
- [string interpolation]: ./string-interpolation.md
-
- The second way to write string literals is as an *indented string*,
- which is enclosed between pairs of *double single-quotes*, like so:
-
- ```nix
- ''
- This is the first line.
- This is the second line.
- This is the third line.
- ''
- ```
-
- This kind of string literal intelligently strips indentation from
- the start of each line. To be precise, it strips from each line a
- number of spaces equal to the minimal indentation of the string as a
- whole (disregarding the indentation of empty lines). For instance,
- the first and second line are indented two spaces, while the third
- line is indented four spaces. Thus, two spaces are stripped from
- each line, so the resulting string is
-
- ```nix
- "This is the first line.\nThis is the second line.\n This is the third line.\n"
- ```
-
- Note that the whitespace and newline following the opening `''` is
- ignored if there is no non-whitespace text on the initial line.
-
- Indented strings support [string interpolation].
-
- Since `${` and `''` have special meaning in indented strings, you
- need a way to quote them. `$` can be escaped by prefixing it with
- `''` (that is, two single quotes), i.e., `''$`. `''` can be escaped
- by prefixing it with `'`, i.e., `'''`. `$` removes any special
- meaning from the following `$`. Linefeed, carriage-return and tab
- characters can be written as `''\n`, `''\r`, `''\t`, and `''\`
- escapes any other character.
-
- Indented strings are primarily useful in that they allow multi-line
- string literals to follow the indentation of the enclosing Nix
- expression, and that less escaping is typically necessary for
- strings representing languages such as shell scripts and
- configuration files because `''` is much less common than `"`.
- Example:
-
- ```nix
- stdenv.mkDerivation {
- ...
- postInstall =
- ''
- mkdir $out/bin $out/etc
- cp foo $out/bin
- echo "Hello World" > $out/etc/foo.conf
- ${if enableBar then "cp bar $out/bin" else ""}
- '';
- ...
- }
- ```
-
- Finally, as a convenience, *URIs* as defined in appendix B of
- [RFC 2396](http://www.ietf.org/rfc/rfc2396.txt) can be written *as
- is*, without quotes. For instance, the string
- `"http://example.org/foo.tar.bz2"` can also be written as
- `http://example.org/foo.tar.bz2`.
-
-- Number
-
- Numbers, which can be *integers* (like `123`) or *floating point*
- (like `123.43` or `.27e13`).
-
- See [arithmetic] and [comparison] operators for semantics.
-
- [arithmetic]: ./operators.md#arithmetic
- [comparison]: ./operators.md#comparison
-
-- Path
-
- *Paths*, e.g., `/bin/sh` or `./builder.sh`. A path must contain at
- least one slash to be recognised as such. For instance, `builder.sh`
- is not a path: it's parsed as an expression that selects the
- attribute `sh` from the variable `builder`. If the file name is
- relative, i.e., if it does not begin with a slash, it is made
- absolute at parse time relative to the directory of the Nix
- expression that contained it. For instance, if a Nix expression in
- `/foo/bar/bla.nix` refers to `../xyzzy/fnord.nix`, the absolute path
- is `/foo/xyzzy/fnord.nix`.
-
- If the first component of a path is a `~`, it is interpreted as if
- the rest of the path were relative to the user's home directory.
- e.g. `~/foo` would be equivalent to `/home/edolstra/foo` for a user
- whose home directory is `/home/edolstra`.
-
- Paths can also be specified between angle brackets, e.g.
- ``. This means that the directories listed in the
- environment variable `NIX_PATH` will be searched for the given file
- or directory name.
-
- When an [interpolated string][string interpolation] evaluates to a path, the path is first copied into the Nix store and the resulting string is the [store path] of the newly created [store object].
-
- [store path]: ../glossary.md#gloss-store-path
- [store object]: ../glossary.md#gloss-store-object
-
- For instance, evaluating `"${./foo.txt}"` will cause `foo.txt` in the current directory to be copied into the Nix store and result in the string `"/nix/store/-foo.txt"`.
-
- Note that the Nix language assumes that all input files will remain _unchanged_ while evaluating a Nix expression.
- For example, assume you used a file path in an interpolated string during a `nix repl` session.
- Later in the same session, after having changed the file contents, evaluating the interpolated string with the file path again might not return a new store path, since Nix might not re-read the file contents.
-
- Paths themselves, except those in angle brackets (`< >`), support [string interpolation].
-
- At least one slash (`/`) must appear *before* any interpolated expression for the result to be recognized as a path.
-
- `a.${foo}/b.${bar}` is a syntactically valid division operation.
- `./a.${foo}/b.${bar}` is a path.
-
-- Boolean
-
- *Booleans* with values `true` and `false`.
-
-- Null
-
- The null value, denoted as `null`.
-
-## List
-
-Lists are formed by enclosing a whitespace-separated list of values
-between square brackets. For example,
-
-```nix
-[ 123 ./foo.nix "abc" (f { x = y; }) ]
-```
-
-defines a list of four elements, the last being the result of a call to
-the function `f`. Note that function calls have to be enclosed in
-parentheses. If they had been omitted, e.g.,
-
-```nix
-[ 123 ./foo.nix "abc" f { x = y; } ]
-```
-
-the result would be a list of five elements, the fourth one being a
-function and the fifth being a set.
-
-Note that lists are only lazy in values, and they are strict in length.
-
-## Attribute Set
-
-An attribute set is a collection of name-value-pairs (called *attributes*) enclosed in curly brackets (`{ }`).
-
-An attribute name can be an identifier or a [string](#string).
-An identifier must start with a letter (`a-z`, `A-Z`) or underscore (`_`), and can otherwise contain letters (`a-z`, `A-Z`), numbers (`0-9`), underscores (`_`), apostrophes (`'`), or dashes (`-`).
-
-> *name* = *identifier* | *string* \
-> *identifier* ~ `[a-zA-Z_][a-zA-Z0-9_'-]*`
-
-Names and values are separated by an equal sign (`=`).
-Each value is an arbitrary expression terminated by a semicolon (`;`).
-
-> *attrset* = `{` [ *name* `=` *expr* `;` `]`... `}`
-
-Attributes can appear in any order.
-An attribute name may only occur once.
-
-Example:
-
-```nix
-{
- x = 123;
- text = "Hello";
- y = f { bla = 456; };
-}
-```
-
-This defines a set with attributes named `x`, `text`, `y`.
-
-Attributes can be accessed with the [`.` operator](./operators.md#attribute-selection).
-
-Example:
-
-```nix
-{ a = "Foo"; b = "Bar"; }.a
-```
-
-This evaluates to `"Foo"`.
-
-It is possible to provide a default value in an attribute selection using the `or` keyword.
-
-Example:
-
-```nix
-{ a = "Foo"; b = "Bar"; }.c or "Xyzzy"
-```
-
-```nix
-{ a = "Foo"; b = "Bar"; }.c.d.e.f.g or "Xyzzy"
-```
-
-will both evaluate to `"Xyzzy"` because there is no `c` attribute in the set.
-
-You can use arbitrary double-quoted strings as attribute names:
-
-```nix
-{ "$!@#?" = 123; }."$!@#?"
-```
-
-```nix
-let bar = "bar"; in
-{ "foo ${bar}" = 123; }."foo ${bar}"
-```
-
-Both will evaluate to `123`.
-
-Attribute names support [string interpolation]:
-
-```nix
-let bar = "foo"; in
-{ foo = 123; }.${bar}
-```
-
-```nix
-let bar = "foo"; in
-{ ${bar} = 123; }.foo
-```
-
-Both will evaluate to `123`.
-
-In the special case where an attribute name inside of a set declaration
-evaluates to `null` (which is normally an error, as `null` cannot be coerced to
-a string), that attribute is simply not added to the set:
-
-```nix
-{ ${if foo then "bar" else null} = true; }
-```
-
-This will evaluate to `{}` if `foo` evaluates to `false`.
-
-A set that has a `__functor` attribute whose value is callable (i.e. is
-itself a function or a set with a `__functor` attribute whose value is
-callable) can be applied as if it were a function, with the set itself
-passed in first , e.g.,
-
-```nix
-let add = { __functor = self: x: x + self.x; };
- inc = add // { x = 1; };
-in inc 1
-```
-
-evaluates to `2`. This can be used to attach metadata to a function
-without the caller needing to treat it specially, or to implement a form
-of object-oriented programming, for example.
diff --git a/doc/manual/src/package-management/basic-package-mgmt.md b/doc/manual/src/package-management/basic-package-mgmt.md
deleted file mode 100644
index 0d94ea231..000000000
--- a/doc/manual/src/package-management/basic-package-mgmt.md
+++ /dev/null
@@ -1,188 +0,0 @@
-# Basic Package Management
-
-
-
-FIXME(Lix): This section does not document the most common modern practices in terms of avoiding channels, pinning, declarative software installation (see flakey-profile or home-manager or NixOS), or using flakes, etc.
-It is, however, likely correct at a technical level.
-
-For more information on modern practices, see the [resources](https://lix.systems/resources) page on the Lix site.
-
-
-
-The main command for package management is
-[`nix-env`](../command-ref/nix-env.md). You can use it to install,
-upgrade, and erase packages, and to query what packages are installed
-or are available for installation.
-
-In Nix systems, different users can have different “views” on the set of
-installed applications. That is, there might be lots of applications
-present on the system (possibly in many different versions), but users
-can have a specific selection of those active — where “active” just
-means that it appears in a directory in the user’s `PATH`. Such a view
-on the set of installed applications is called a *user environment*,
-which is just a directory tree consisting of symlinks to the files of
-the active applications.
-
-Components are installed from a set of *Nix expressions* that tell Lix
-how to build those packages, including, if necessary, their
-dependencies. There is a very large collection of Nix expressions called the
-Nixpkgs package collection that contains packages ranging from basic
-development stuff such as GCC and Glibc, to end-user applications like
-Mozilla Firefox. (Lix is however not tied to the Nixpkgs package
-collection; you could write your own Nix expressions based on Nixpkgs,
-or completely new ones.)
-
-You can manually download the latest version of Nixpkgs from
-. However, it’s much more
-convenient to use the Nixpkgs [*channel*](../command-ref/nix-channel.md), since it makes
-it easy to stay up to date with new versions of Nixpkgs. Nixpkgs is
-automatically added to your list of “subscribed” channels when you
-install Lix. If this is not the case for some reason, you can add it
-as follows:
-
-```console
-$ nix-channel --add https://nixos.org/channels/nixpkgs-unstable
-$ nix-channel --update
-```
-
-> **Note**
->
-> On NixOS, you’re automatically subscribed to a NixOS channel
-> corresponding to your NixOS major release (e.g.
-> ). A NixOS channel is identical
-> to the Nixpkgs channel, except that it contains only Linux binaries
-> and is updated only if a set of regression tests succeed.
-
-You can view the set of available packages in Nixpkgs:
-
-```console
-$ nix-env --query --available --attr-path
-nixpkgs.aterm aterm-2.2
-nixpkgs.bash bash-3.0
-nixpkgs.binutils binutils-2.15
-nixpkgs.bison bison-1.875d
-nixpkgs.blackdown blackdown-1.4.2
-nixpkgs.bzip2 bzip2-1.0.2
-…
-```
-
-The flag `-q` specifies a query operation, `-a` means that you want
-to show the “available” (i.e., installable) packages, as opposed to the
-installed packages, and `-P` prints the attribute paths that can be used
-to unambiguously select a package for installation (listed in the first column).
-If you downloaded Nixpkgs yourself, or if you checked it out from GitHub,
-then you need to pass the path to your Nixpkgs tree using the `-f` flag:
-
-```console
-$ nix-env --query --available --attr-path --file /path/to/nixpkgs
-aterm aterm-2.2
-bash bash-3.0
-…
-```
-
-where */path/to/nixpkgs* is where you’ve unpacked or checked out
-Nixpkgs.
-
-You can filter the packages by name:
-
-```console
-$ nix-env --query --available --attr-path firefox
-nixpkgs.firefox-esr firefox-91.3.0esr
-nixpkgs.firefox firefox-94.0.1
-```
-
-and using regular expressions:
-
-```console
-$ nix-env --query --available --attr-path 'firefox.*'
-```
-
-It is also possible to see the *status* of available packages, i.e.,
-whether they are installed into the user environment and/or present in
-the system:
-
-```console
-$ nix-env --query --available --attr-path --status
-…
--PS nixpkgs.bash bash-3.0
---S nixpkgs.binutils binutils-2.15
-IPS nixpkgs.bison bison-1.875d
-…
-```
-
-The first character (`I`) indicates whether the package is installed in
-your current user environment. The second (`P`) indicates whether it is
-present on your system (in which case installing it into your user
-environment would be a very quick operation). The last one (`S`)
-indicates whether there is a so-called *substitute* for the package,
-which is Nix’s mechanism for doing binary deployment. It just means that
-Lix knows that it can fetch a pre-built package from somewhere
-(typically a network server) instead of building it locally.
-
-You can install a package using `nix-env --install --attr `. For instance,
-
-```console
-$ nix-env --install --attr nixpkgs.subversion
-```
-
-will install the package called `subversion` from `nixpkgs` channel (which is, of course, the
-[Subversion version management system](http://subversion.tigris.org/)).
-
-> **Note**
->
-> When you ask Lix to install a package, it will first try to get it in
-> pre-compiled form from a *binary cache*. By default, Lix will use the
-> binary cache ; it contains binaries for most
-> packages in Nixpkgs. Only if no binary is available in the binary
-> cache, Lix will build the package from source. So if `nix-env
-> -iA nixpkgs.subversion` results in Lix building stuff from source, then either
-> the package is not built for your platform by the Nixpkgs build
-> servers, or your version of Nixpkgs is too old or too new. For
-> instance, if you have a very recent checkout of Nixpkgs, then the
-> Nixpkgs build servers may not have had a chance to build everything
-> and upload the resulting binaries to . The
-> Nixpkgs channel is only updated after all binaries have been uploaded
-> to the cache, so if you stick to the Nixpkgs channel (rather than
-> using a Git checkout of the Nixpkgs tree), you will get binaries for
-> most packages.
-
-Naturally, packages can also be uninstalled. Unlike when installing, you will
-need to use the derivation name (though the version part can be omitted),
-instead of the attribute path, as `nix-env` does not record which attribute
-was used for installing:
-
-```console
-$ nix-env --uninstall subversion
-```
-
-Upgrading to a new version is just as easy. If you have a new release of
-nixpkgs, you can do:
-
-```console
-$ nix-env --upgrade --attr nixpkgs.subversion
-```
-
-This will *only* upgrade Subversion if there is a “newer” version in the
-new set of Nix expressions, as defined by some pretty arbitrary rules
-regarding ordering of version numbers (which generally do what you’d
-expect of them). To just unconditionally replace Subversion with
-whatever version is in the Nix expressions, use `-i` instead of `-u`;
-`-i` will remove whatever version is already installed.
-
-You can also upgrade all packages for which there are newer versions:
-
-```console
-$ nix-env --upgrade
-```
-
-Sometimes it’s useful to be able to ask what `nix-env` would do, without
-actually doing it. For instance, to find out what packages would be
-upgraded by `nix-env --upgrade `, you can do
-
-```console
-$ nix-env --upgrade --dry-run
-(dry run; not doing anything)
-upgrading `libxslt-1.1.0' to `libxslt-1.1.10'
-upgrading `graphviz-1.10' to `graphviz-1.12'
-upgrading `coreutils-5.0' to `coreutils-5.2.1'
-```
diff --git a/doc/manual/src/package-management/binary-cache-substituter.md b/doc/manual/src/package-management/binary-cache-substituter.md
deleted file mode 100644
index 4dcf2ca3f..000000000
--- a/doc/manual/src/package-management/binary-cache-substituter.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Serving a Nix store via HTTP
-
-
-
-FIXME(Lix): This section documents outdated practices.
-
-In particular, the Lix developers would *not* recommend using `nix-serve` as it is relatively-unmaintained Perl.
-The Lix developers would recommend instead using an s3 based cache (which is what https://cache.nixos.org is), and if it is desired to self-host it, use something like [garage](https://garagehq.deuxfleurs.fr/).
-
-See the following projects:
-- [attic](https://github.com/zhaofengli/attic) - multi-tenant cache for larger deployments, using s3 as a backend.
-- [harmonia](https://github.com/nix-community/harmonia) - closer to a drop in replacement for use cases served by nix-serve
-
-
-
-You can easily share the Nix store of a machine via HTTP. This allows
-other machines to fetch store paths from that machine to speed up
-installations. It uses the same *binary cache* mechanism that Lix
-usually uses to fetch pre-built binaries from .
-
-The daemon that handles binary cache requests via HTTP, `nix-serve`, is
-not part of the Nix distribution, but you can install it from Nixpkgs:
-
-```console
-$ nix-env --install --attr nixpkgs.nix-serve
-```
-
-You can then start the server, listening for HTTP connections on
-whatever port you like:
-
-```console
-$ nix-serve -p 8080
-```
-
-To check whether it works, try the following on the client:
-
-```console
-$ curl http://avalon:8080/nix-cache-info
-```
-
-which should print something like:
-
- StoreDir: /nix/store
- WantMassQuery: 1
- Priority: 30
-
-On the client side, you can tell Lix to use your binary cache using `--substituters` (assuming you are a trusted user, see `trusted-users` in nix.conf), e.g.:
-
-```console
-$ nix-env --install --attr nixpkgs.firefox --substituters http://avalon:8080/
-```
-
-The option `substituters` tells Lix to use this binary cache in
-addition to your default caches, such as .
-Thus, for any path in the closure of Firefox, Lix will first check if
-the path is available on the server `avalon` or another binary caches.
-If not, it will fall back to building from source.
-
-You can also tell Lix to always use your binary cache by adding a line
-to the `nix.conf` configuration file like this:
-
- substituters = http://avalon:8080/ https://cache.nixos.org/
diff --git a/doc/manual/src/package-management/copy-closure.md b/doc/manual/src/package-management/copy-closure.md
deleted file mode 100644
index 14326298b..000000000
--- a/doc/manual/src/package-management/copy-closure.md
+++ /dev/null
@@ -1,34 +0,0 @@
-# Copying Closures via SSH
-
-The command `nix-copy-closure` copies a Nix store path along with all
-its dependencies to or from another machine via the SSH protocol. It
-doesn’t copy store paths that are already present on the target machine.
-For example, the following command copies Firefox with all its
-dependencies:
-
- $ nix-copy-closure --to alice@itchy.example.org $(type -p firefox)
-
-See the [manpage for `nix-copy-closure`](../command-ref/nix-copy-closure.md) for details.
-
-With `nix-store
---export` and `nix-store --import` you can write the closure of a store
-path (that is, the path and all its dependencies) to a file, and then
-unpack that file into another Nix store. For example,
-
- $ nix-store --export $(nix-store --query --requisites $(type -p firefox)) > firefox.closure
-
-writes the closure of Firefox to a file. You can then copy this file to
-another machine and install the closure:
-
- $ nix-store --import < firefox.closure
-
-Any store paths in the closure that are already present in the target
-store are ignored. It is also possible to pipe the export into another
-command, e.g. to copy and install a closure directly to/on another
-machine:
-
- $ nix-store --export $(nix-store --query --requisites $(type -p firefox)) | bzip2 | \
- ssh alice@itchy.example.org "bunzip2 | nix-store --import"
-
-However, `nix-copy-closure` is generally more efficient because it only
-copies paths that are not already present in the target Nix store.
diff --git a/doc/manual/src/package-management/garbage-collection.md b/doc/manual/src/package-management/garbage-collection.md
deleted file mode 100644
index 07ca29365..000000000
--- a/doc/manual/src/package-management/garbage-collection.md
+++ /dev/null
@@ -1,73 +0,0 @@
-# Garbage Collection
-
-`nix-env` operations such as upgrades (`-u`) and uninstall (`-e`) never
-actually delete packages from the system. All they do (as shown above)
-is to create a new user environment that no longer contains symlinks to
-the “deleted” packages.
-
-Of course, since disk space is not infinite, unused packages should be
-removed at some point. You can do this by running the Lix garbage
-collector. It will remove from the Nix store any package not used
-(directly or indirectly) by any generation of any profile.
-
-Note however that as long as old generations reference a package, it
-will not be deleted. After all, we wouldn’t be able to do a rollback
-otherwise. So in order for garbage collection to be effective, you
-should also delete (some) old generations. Of course, this should only
-be done if you are certain that you will not need to roll back.
-
-To delete all old (non-current) generations of your current profile:
-
-```console
-$ nix-env --delete-generations old
-```
-
-Instead of `old` you can also specify a list of generations, e.g.,
-
-```console
-$ nix-env --delete-generations 10 11 14
-```
-
-To delete all generations older than a specified number of days (except
-the current generation), use the `d` suffix. For example,
-
-```console
-$ nix-env --delete-generations 14d
-```
-
-deletes all generations older than two weeks.
-
-After removing appropriate old generations you can run the garbage
-collector as follows:
-
-```console
-$ nix-store --gc
-```
-
-The behaviour of the garbage collector is affected by the
-`keep-derivations` (default: true) and `keep-outputs` (default: false)
-options in the Nix configuration file. The defaults will ensure that all
-derivations that are build-time dependencies of garbage collector roots
-will be kept and that all output paths that are runtime dependencies
-will be kept as well. All other derivations or paths will be collected.
-(This is usually what you want, but while you are developing it may make
-sense to keep outputs to ensure that rebuild times are quick.) If you
-are feeling uncertain, you can also first view what files would be
-deleted:
-
-```console
-$ nix-store --gc --print-dead
-```
-
-Likewise, the option `--print-live` will show the paths that *won’t* be
-deleted.
-
-There is also a convenient little utility `nix-collect-garbage`, which
-when invoked with the `-d` (`--delete-old`) switch deletes all old
-generations of all profiles in `/nix/var/nix/profiles`. So
-
-```console
-$ nix-collect-garbage -d
-```
-
-is a quick and easy way to clean up your system.
diff --git a/doc/manual/src/package-management/garbage-collector-roots.md b/doc/manual/src/package-management/garbage-collector-roots.md
deleted file mode 100644
index 30c5b7f8d..000000000
--- a/doc/manual/src/package-management/garbage-collector-roots.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Garbage Collector Roots
-
-The roots of the garbage collector are all store paths to which there
-are symlinks in the directory `prefix/nix/var/nix/gcroots`. For
-instance, the following command makes the path
-`/nix/store/d718ef...-foo` a root of the collector:
-
-```console
-$ ln -s /nix/store/d718ef...-foo /nix/var/nix/gcroots/bar
-```
-
-That is, after this command, the garbage collector will not remove
-`/nix/store/d718ef...-foo` or any of its dependencies.
-
-Subdirectories of `prefix/nix/var/nix/gcroots` are also searched for
-symlinks. Symlinks to non-store paths are followed and searched for
-roots, but symlinks to non-store paths *inside* the paths reached in
-that way are not followed to prevent infinite recursion.
diff --git a/doc/manual/src/package-management/package-management.md b/doc/manual/src/package-management/package-management.md
deleted file mode 100644
index 274986663..000000000
--- a/doc/manual/src/package-management/package-management.md
+++ /dev/null
@@ -1,4 +0,0 @@
-This chapter discusses how to do package management with Lix, i.e.,
-how to obtain, install, upgrade, and erase packages. This is the
-“user’s” perspective of the Nix system — people who want to *create*
-packages should consult the chapter on the [Nix language](../language/index.md).
diff --git a/doc/manual/src/package-management/profiles.md b/doc/manual/src/package-management/profiles.md
deleted file mode 100644
index 1d9e672a8..000000000
--- a/doc/manual/src/package-management/profiles.md
+++ /dev/null
@@ -1,133 +0,0 @@
-# Profiles
-
-Profiles and user environments are Nix’s mechanism for implementing the
-ability to allow different users to have different configurations, and
-to do atomic upgrades and rollbacks. To understand how they work, it’s
-useful to know a bit about how Nix works. In Nix, packages are stored in
-unique locations in the *Nix store* (typically, `/nix/store`). For
-instance, a particular version of the Subversion package might be stored
-in a directory
-`/nix/store/dpmvp969yhdqs7lm2r1a3gng7pyq6vy4-subversion-1.1.3/`, while
-another version might be stored in
-`/nix/store/5mq2jcn36ldlmh93yj1n8s9c95pj7c5s-subversion-1.1.2`. The long
-strings prefixed to the directory names are cryptographic hashes (to be
-precise, 160-bit truncations of SHA-256 hashes encoded in a base-32
-notation) of *all* inputs involved in building the package — sources,
-dependencies, compiler flags, and so on. So if two packages differ in
-any way, they end up in different locations in the file system, so they
-don’t interfere with each other. Here is what a part of a typical Nix
-store looks like:
-
-
-
-Of course, you wouldn’t want to type
-
-```console
-$ /nix/store/dpmvp969yhdq...-subversion-1.1.3/bin/svn
-```
-
-every time you want to run Subversion. Of course we could set up the
-`PATH` environment variable to include the `bin` directory of every
-package we want to use, but this is not very convenient since changing
-`PATH` doesn’t take effect for already existing processes. The solution
-Nix uses is to create directory trees of symlinks to *activated*
-packages. These are called *user environments* and they are packages
-themselves (though automatically generated by `nix-env`), so they too
-reside in the Nix store. For instance, in the figure above, the user
-environment `/nix/store/0c1p5z4kda11...-user-env` contains a symlink to
-just Subversion 1.1.2 (arrows in the figure indicate symlinks). This
-would be what we would obtain if we had done
-
-```console
-$ nix-env --install --attr nixpkgs.subversion
-```
-
-on a set of Nix expressions that contained Subversion 1.1.2.
-
-This doesn’t in itself solve the problem, of course; you wouldn’t want
-to type `/nix/store/0c1p5z4kda11...-user-env/bin/svn` either. That’s why
-there are symlinks outside of the store that point to the user
-environments in the store; for instance, the symlinks `default-42-link`
-and `default-43-link` in the example. These are called *generations*
-since every time you perform a `nix-env` operation, a new user
-environment is generated based on the current one. For instance,
-generation 43 was created from generation 42 when we did
-
-```console
-$ nix-env --install --attr nixpkgs.subversion nixpkgs.firefox
-```
-
-on a set of Nix expressions that contained Firefox and a new version of
-Subversion.
-
-Generations are grouped together into *profiles* so that different users
-don’t interfere with each other if they don’t want to. For example:
-
-```console
-$ ls -l /nix/var/nix/profiles/
-...
-lrwxrwxrwx 1 eelco ... default-42-link -> /nix/store/0c1p5z4kda11...-user-env
-lrwxrwxrwx 1 eelco ... default-43-link -> /nix/store/3aw2pdyx2jfc...-user-env
-lrwxrwxrwx 1 eelco ... default -> default-43-link
-```
-
-This shows a profile called `default`. The file `default` itself is
-actually a symlink that points to the current generation. When we do a
-`nix-env` operation, a new user environment and generation link are
-created based on the current one, and finally the `default` symlink is
-made to point at the new generation. This last step is atomic on Unix,
-which explains how we can do atomic upgrades. (Note that the
-building/installing of new packages doesn’t interfere in any way with
-old packages, since they are stored in different locations in the Nix
-store.)
-
-If you find that you want to undo a `nix-env` operation, you can just do
-
-```console
-$ nix-env --rollback
-```
-
-which will just make the current generation link point at the previous
-link. E.g., `default` would be made to point at `default-42-link`. You
-can also switch to a specific generation:
-
-```console
-$ nix-env --switch-generation 43
-```
-
-which in this example would roll forward to generation 43 again. You can
-also see all available generations:
-
-```console
-$ nix-env --list-generations
-```
-
-You generally wouldn’t have `/nix/var/nix/profiles/some-profile/bin` in
-your `PATH`. Rather, there is a symlink `~/.nix-profile` that points to
-your current profile. This means that you should put
-`~/.nix-profile/bin` in your `PATH` (and indeed, that’s what the
-initialisation script `/nix/etc/profile.d/nix.sh` does). This makes it
-easier to switch to a different profile. You can do that using the
-command `nix-env --switch-profile`:
-
-```console
-$ nix-env --switch-profile /nix/var/nix/profiles/my-profile
-
-$ nix-env --switch-profile /nix/var/nix/profiles/default
-```
-
-These commands switch to the `my-profile` and default profile,
-respectively. If the profile doesn’t exist, it will be created
-automatically. You should be careful about storing a profile in another
-location than the `profiles` directory, since otherwise it might not be
-used as a root of the [garbage collector](garbage-collection.md).
-
-All `nix-env` operations work on the profile pointed to by
-`~/.nix-profile`, but you can override this using the `--profile` option
-(abbreviation `-p`):
-
-```console
-$ nix-env --profile /nix/var/nix/profiles/other-profile --install --attr nixpkgs.subversion
-```
-
-This will *not* change the `~/.nix-profile` symlink.
diff --git a/doc/manual/src/package-management/s3-substituter.md b/doc/manual/src/package-management/s3-substituter.md
deleted file mode 100644
index 55182128b..000000000
--- a/doc/manual/src/package-management/s3-substituter.md
+++ /dev/null
@@ -1,126 +0,0 @@
-# Serving a Nix store via S3
-
-Lix has [built-in support](@docroot@/command-ref/new-cli/nix3-help-stores.md#s3-binary-cache-store)
-for storing and fetching store paths from Amazon S3 and S3-compatible services.
-
-
-
-FIXME(Lix): document the correct setup to fetch from a s3 cache via HTTP rather than just through `s3://` (which works, but forces you to remain s3-like on the client side)
-
-
-
-
-
-In this example we will use the bucket named `example-nix-cache`.
-
-## Anonymous Reads to your S3-compatible binary cache
-
-If your binary cache is publicly accessible and does not require
-authentication, the simplest and easiest way to use Lix with your S3
-compatible binary cache is to use the HTTP URL for that cache.
-
-For AWS S3 the binary cache URL for example bucket will be exactly
- or
-. For S3 compatible binary caches, consult that
-cache's documentation.
-
-Your bucket will need the following bucket policy:
-
-```json
-{
- "Id": "DirectReads",
- "Version": "2012-10-17",
- "Statement": [
- {
- "Sid": "AllowDirectReads",
- "Action": [
- "s3:GetObject",
- "s3:GetBucketLocation"
- ],
- "Effect": "Allow",
- "Resource": [
- "arn:aws:s3:::example-nix-cache",
- "arn:aws:s3:::example-nix-cache/*"
- ],
- "Principal": "*"
- }
- ]
-}
-```
-
-## Authenticated Reads to your S3 binary cache
-
-For AWS S3 the binary cache URL for example bucket will be exactly
-.
-
-Lix will use the [default credential provider
-chain](https://docs.aws.amazon.com/sdk-for-cpp/v1/developer-guide/credentials.html)
-for authenticating requests to Amazon S3.
-
-Lix supports authenticated reads from Amazon S3 and S3 compatible binary
-caches.
-
-Your bucket will need a bucket policy allowing the desired users to
-perform the `s3:GetObject` and `s3:GetBucketLocation` action on all
-objects in the bucket. The [anonymous policy given
-above](#anonymous-reads-to-your-s3-compatible-binary-cache) can be
-updated to have a restricted `Principal` to support this.
-
-## Authenticated Writes to your S3-compatible binary cache
-
-Lix support fully supports writing to Amazon S3 and S3 compatible
-buckets. The binary cache URL for our example bucket will be
-.
-
-Lix will use the [default credential provider
-chain](https://docs.aws.amazon.com/sdk-for-cpp/v1/developer-guide/credentials.html)
-for authenticating requests to Amazon S3.
-
-Your account will need the following IAM policy to upload to the cache:
-
-```json
-{
- "Version": "2012-10-17",
- "Statement": [
- {
- "Sid": "UploadToCache",
- "Effect": "Allow",
- "Action": [
- "s3:AbortMultipartUpload",
- "s3:GetBucketLocation",
- "s3:GetObject",
- "s3:ListBucket",
- "s3:ListBucketMultipartUploads",
- "s3:ListMultipartUploadParts",
- "s3:PutObject"
- ],
- "Resource": [
- "arn:aws:s3:::example-nix-cache",
- "arn:aws:s3:::example-nix-cache/*"
- ]
- }
- ]
-}
-```
-
-## Examples
-
-To upload with a specific credential profile for Amazon S3:
-
-```console
-$ nix copy nixpkgs.hello \
- --to 's3://example-nix-cache?profile=cache-upload®ion=eu-west-2'
-```
-
-To upload to an S3-compatible binary cache:
-
-```console
-$ nix copy nixpkgs.hello --to \
- 's3://example-nix-cache?profile=cache-upload&scheme=https&endpoint=minio.example.com'
-```
diff --git a/doc/manual/src/package-management/sharing-packages.md b/doc/manual/src/package-management/sharing-packages.md
deleted file mode 100644
index 846ca6934..000000000
--- a/doc/manual/src/package-management/sharing-packages.md
+++ /dev/null
@@ -1,6 +0,0 @@
-# Sharing Packages Between Machines
-
-Sometimes you want to copy a package from one machine to another. Or,
-you want to install some packages and you know that another machine
-already has some or all of those packages or their dependencies. In that
-case there are mechanisms to quickly copy packages between machines.
diff --git a/doc/manual/src/package-management/ssh-substituter.md b/doc/manual/src/package-management/ssh-substituter.md
deleted file mode 100644
index 44dc3ef84..000000000
--- a/doc/manual/src/package-management/ssh-substituter.md
+++ /dev/null
@@ -1,62 +0,0 @@
-# Serving a Nix store via SSH
-
-You can tell Lix to automatically fetch needed binaries from a remote
-Nix store via SSH. For example, the following installs Firefox,
-automatically fetching any store paths in Firefox’s closure if they are
-available on the server `avalon`:
-
-```console
-$ nix-env --install --attr nixpkgs.firefox --substituters ssh://alice@avalon
-```
-
-This works similar to the binary cache substituter that Lix usually
-uses, only using SSH instead of HTTP: if a store path `P` is needed, Lix
-will first check if it’s available in the Nix store on `avalon`. If not,
-it will fall back to using the binary cache substituter, and then to
-building from source.
-
-> **Note**
->
-> The SSH substituter currently does not allow you to enter an SSH
-> passphrase interactively. Therefore, you should use `ssh-add` to load
-> the decrypted private key into `ssh-agent`.
-
-You can also copy the closure of some store path, without installing it
-into your profile, e.g.
-
-```console
-$ nix-store --realise /nix/store/m85bxg…-firefox-34.0.5 --substituters
-ssh://alice@avalon
-```
-
-This is essentially equivalent to doing
-
-```console
-$ nix-copy-closure --from alice@avalon
-/nix/store/m85bxg…-firefox-34.0.5
-```
-
-You can use SSH’s *forced command* feature to set up a restricted user
-account for SSH substituter access, allowing read-only access to the
-local Nix store, but nothing more. For example, add the following lines
-to `sshd_config` to restrict the user `nix-ssh`:
-
- Match User nix-ssh
- AllowAgentForwarding no
- AllowTcpForwarding no
- PermitTTY no
- PermitTunnel no
- X11Forwarding no
- ForceCommand nix-store --serve
- Match All
-
-On NixOS, you can accomplish the same by adding the following to your
-`configuration.nix`:
-
-```nix
-nix.sshServe.enable = true;
-nix.sshServe.keys = [ "ssh-dss AAAAB3NzaC1k... bob@example.org" ];
-```
-
-where the latter line lists the public keys of users that are allowed to
-connect.
diff --git a/doc/manual/src/protocols/derivation-aterm.md b/doc/manual/src/protocols/derivation-aterm.md
deleted file mode 100644
index e58b602a3..000000000
--- a/doc/manual/src/protocols/derivation-aterm.md
+++ /dev/null
@@ -1,19 +0,0 @@
-# Derivation "ATerm" file format
-
-For historical reasons, [derivations](@docroot@/glossary.md#gloss-store-derivation) are stored on-disk in [ATerm](https://homepages.cwi.nl/~daybuild/daily-books/technology/aterm-guide/aterm-guide.html) format.
-
-Derivations are serialised in one of the following formats:
-
-- ```
- Derive(...)
- ```
-
- For all stable derivations.
-
-- ```
- DrvWithVersion(, ...)
- ```
-
- The only `version-string`s that are in use today are for [experimental features](@docroot@/contributing/experimental-features.md):
-
- - `"xp-dyn-drv"` for the [`dynamic-derivations`](@docroot@/contributing/experimental-features.md#xp-feature-dynamic-derivations) experimental feature.
diff --git a/doc/manual/src/protocols/protocols.md b/doc/manual/src/protocols/protocols.md
deleted file mode 100644
index 1f77f98a2..000000000
--- a/doc/manual/src/protocols/protocols.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Protocols
-
-This chapter documents various developer-facing interfaces provided by
-Lix.
diff --git a/doc/manual/src/protocols/tarball-fetcher.md b/doc/manual/src/protocols/tarball-fetcher.md
deleted file mode 100644
index 3527333f2..000000000
--- a/doc/manual/src/protocols/tarball-fetcher.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Lockable HTTP Tarball Protocol
-
-Tarball flakes can be served as regular tarballs via HTTP or the file
-system (for `file://` URLs). Unless the server implements the Lockable
-HTTP Tarball protocol, it is the responsibility of the user to make sure that
-the URL always produces the same tarball contents.
-
-An HTTP server can return an "immutable" HTTP URL appropriate for lock
-files. This allows users to specify a tarball flake input in
-`flake.nix` that requests the latest version of a flake
-(e.g. `https://example.org/hello/latest.tar.gz`), while `flake.lock`
-will record a URL whose contents will not change
-(e.g. `https://example.org/hello/.tar.gz`). To do so, the
-server must return an [HTTP `Link` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Link) with the `rel` attribute set to
-`immutable`, as follows:
-
-```
-Link: ; rel="immutable"
-```
-
-(Note the required `<` and `>` characters around *flakeref*.)
-
-*flakeref* must be a tarball flakeref. It can contain the tarball flake attributes
-`narHash`, `rev`, `revCount` and `lastModified`. If `narHash` is included, its
-value must be the NAR hash of the unpacked tarball (as computed via
-`nix hash path`). Lix checks the contents of the returned tarball
-against the `narHash` attribute. The `rev` and `revCount` attributes
-are useful when the tarball flake is a mirror of a fetcher type that
-has those attributes, such as Git or GitHub. They are not checked by
-Lix.
-
-```
-Link: ; rel="immutable"
-```
-
-(The linebreaks in this example are for clarity and must not be included in the actual response.)
-
-For tarball flakes, the value of the `lastModified` flake attribute is
-defined as the timestamp of the newest file inside the tarball.
diff --git a/doc/manual/src/quick-start.md b/doc/manual/src/quick-start.md
deleted file mode 100644
index 862eed432..000000000
--- a/doc/manual/src/quick-start.md
+++ /dev/null
@@ -1,114 +0,0 @@
-# Quick Start
-
-
-
-FIXME(Lix): This chapter is quite outdated with respect to recommended practices in 2024 and needs updating.
-The commands in here will work, however, and the installation section is up to date.
-
-For more updated guidance, see the links on ).
-
-Nix 0.8 has the following improvements:
-
- - The cryptographic hashes used in store paths are now 160 bits long,
- but encoded in base-32 so that they are still only 32 characters
- long (e.g.,
- `/nix/store/csw87wag8bqlqk7ipllbwypb14xainap-atk-1.9.0`). (This is
- actually a 160 bit truncation of a SHA-256 hash.)
-
- - Big cleanups and simplifications of the basic store semantics. The
- notion of “closure store expressions” is gone (and so is the notion
- of “successors”); the file system references of a store path are now
- just stored in the database.
-
- For instance, given any store path, you can query its closure:
-
- $ nix-store -qR $(which firefox)
- ... lots of paths ...
-
- Also, Nix now remembers for each store path the derivation that
- built it (the “deriver”):
-
- $ nix-store -qR $(which firefox)
- /nix/store/4b0jx7vq80l9aqcnkszxhymsf1ffa5jd-firefox-1.0.1.drv
-
- So to see the build-time dependencies, you can do
-
- $ nix-store -qR $(nix-store -qd $(which firefox))
-
- or, in a nicer format:
-
- $ nix-store -q --tree $(nix-store -qd $(which firefox))
-
- File system references are also stored in reverse. For instance, you
- can query all paths that directly or indirectly use a certain Glibc:
-
- $ nix-store -q --referrers-closure \
- /nix/store/8lz9yc6zgmc0vlqmn2ipcpkjlmbi51vv-glibc-2.3.4
-
- - The concept of fixed-output derivations has been formalised.
- Previously, functions such as `fetchurl` in Nixpkgs used a hack
- (namely, explicitly specifying a store path hash) to prevent changes
- to, say, the URL of the file from propagating upwards through the
- dependency graph, causing rebuilds of everything. This can now be
- done cleanly by specifying the `outputHash` and `outputHashAlgo`
- attributes. Nix itself checks that the content of the output has the
- specified hash. (This is important for maintaining certain
- invariants necessary for future work on secure shared stores.)
-
- - One-click installation :-) It is now possible to install any
- top-level component in Nixpkgs directly, through the web — see,
- e.g., ` looks for a file
- `nixpkgs/default.nix` relative to every element in the search path.
-
- - The new command `nix-build --run-env` builds all dependencies of a
- derivation, then starts a shell in an environment containing all
- variables from the derivation. This is useful for reproducing the
- environment of a derivation for development.
-
- - The new command `nix-store --verify-path` verifies that the contents
- of a store path have not changed.
-
- - The new command `nix-store --print-env` prints out the environment
- of a derivation in a format that can be evaluated by a shell.
-
- - Attribute names can now be arbitrary strings. For instance, you can
- write `{ "foo-1.2" = …; "bla bla" = …; }."bla
- bla"`.
-
- - Attribute selection can now provide a default value using the `or`
- operator. For instance, the expression `x.y.z or e` evaluates to the
- attribute `x.y.z` if it exists, and `e` otherwise.
-
- - The right-hand side of the `?` operator can now be an attribute
- path, e.g., `attrs ?
- a.b.c`.
-
- - On Linux, Nix will now make files in the Nix store immutable on
- filesystems that support it. This prevents accidental modification
- of files in the store by the root user.
-
- - Nix has preliminary support for derivations with multiple outputs.
- This is useful because it allows parts of a package to be deployed
- and garbage-collected separately. For instance, development parts of
- a package such as header files or static libraries would typically
- not be part of the closure of an application, resulting in reduced
- disk usage and installation time.
-
- - The Nix store garbage collector is faster and holds the global lock
- for a shorter amount of time.
-
- - The option `--timeout` (corresponding to the configuration setting
- `build-timeout`) allows you to set an absolute timeout on builds —
- if a build runs for more than the given number of seconds, it is
- terminated. This is useful for recovering automatically from builds
- that are stuck in an infinite loop but keep producing output, and
- for which `--max-silent-time` is ineffective.
-
- - Nix development has moved to GitHub
- ().
diff --git a/doc/manual/src/release-notes/rl-1.1.md b/doc/manual/src/release-notes/rl-1.1.md
deleted file mode 100644
index 665dd92a2..000000000
--- a/doc/manual/src/release-notes/rl-1.1.md
+++ /dev/null
@@ -1,61 +0,0 @@
-# Release 1.1 (2012-07-18)
-
-This release has the following improvements:
-
- - On Linux, when doing a chroot build, Nix now uses various namespace
- features provided by the Linux kernel to improve build isolation.
- Namely:
-
- - The private network namespace ensures that builders cannot talk
- to the outside world (or vice versa): each build only sees a
- private loopback interface. This also means that two concurrent
- builds can listen on the same port (e.g. as part of a test)
- without conflicting with each other.
-
- - The PID namespace causes each build to start as PID 1. Processes
- outside of the chroot are not visible to those on the inside. On
- the other hand, processes inside the chroot *are* visible from
- the outside (though with different PIDs).
-
- - The IPC namespace prevents the builder from communicating with
- outside processes using SysV IPC mechanisms (shared memory,
- message queues, semaphores). It also ensures that all IPC
- objects are destroyed when the builder exits.
-
- - The UTS namespace ensures that builders see a hostname of
- `localhost` rather than the actual hostname.
-
- - The private mount namespace was already used by Nix to ensure
- that the bind-mounts used to set up the chroot are cleaned up
- automatically.
-
- - Build logs are now compressed using `bzip2`. The command `nix-store
- -l` decompresses them on the fly. This can be disabled by setting
- the option `build-compress-log` to `false`.
-
- - The creation of build logs in `/nix/var/log/nix/drvs` can be
- disabled by setting the new option `build-keep-log` to `false`. This
- is useful, for instance, for Hydra build machines.
-
- - Nix now reserves some space in `/nix/var/nix/db/reserved` to ensure
- that the garbage collector can run successfully if the disk is full.
- This is necessary because SQLite transactions fail if the disk is
- full.
-
- - Added a basic `fetchurl` function. This is not intended to replace
- the `fetchurl` in Nixpkgs, but is useful for bootstrapping; e.g., it
- will allow us to get rid of the bootstrap binaries in the Nixpkgs
- source tree and download them instead. You can use it by doing
- `import { url =
- url; sha256 =
- "hash"; }`. (Shea Levy)
-
- - Improved RPM spec file. (Michel Alexandre Salim)
-
- - Support for on-demand socket-based activation in the Nix daemon with
- `systemd`.
-
- - Added a manpage for nix.conf5.
-
- - When using the Nix daemon, the `-s` flag in `nix-env -qa` is now
- much faster.
diff --git a/doc/manual/src/release-notes/rl-1.10.md b/doc/manual/src/release-notes/rl-1.10.md
deleted file mode 100644
index 2bb859536..000000000
--- a/doc/manual/src/release-notes/rl-1.10.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# Release 1.10 (2015-09-03)
-
-This is primarily a bug fix release. It also has a number of new
-features:
-
- - A number of builtin functions have been added to reduce
- Nixpkgs/NixOS evaluation time and memory consumption: `all`, `any`,
- `concatStringsSep`, `foldl’`, `genList`, `replaceStrings`, `sort`.
-
- - The garbage collector is more robust when the disk is full.
-
- - Nix supports a new API for building derivations that doesn’t require
- a `.drv` file to be present on disk; it only requires an in-memory
- representation of the derivation. This is used by the Hydra
- continuous build system to make remote builds more efficient.
-
- - The function `` now uses a *builtin* builder (i.e.
- it doesn’t require starting an external process; the download is
- performed by Nix itself). This ensures that derivation paths don’t
- change when Nix is upgraded, and obviates the need for ugly hacks to
- support chroot execution.
-
- - `--version -v` now prints some configuration information, in
- particular what compile-time optional features are enabled, and the
- paths of various directories.
-
- - Build users have their supplementary groups set correctly.
-
-This release has contributions from Eelco Dolstra, Guillaume Maudoux,
-Iwan Aucamp, Jaka Hudoklin, Kirill Elagin, Ludovic Courtès, Manolis
-Ragkousis, Nicolas B. Pierron and Shea Levy.
diff --git a/doc/manual/src/release-notes/rl-1.11.10.md b/doc/manual/src/release-notes/rl-1.11.10.md
deleted file mode 100644
index d1efe1d0b..000000000
--- a/doc/manual/src/release-notes/rl-1.11.10.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Release 1.11.10 (2017-06-12)
-
-This release fixes a security bug in Nix’s “build user” build isolation
-mechanism. Previously, Nix builders had the ability to create setuid
-binaries owned by a `nixbld` user. Such a binary could then be used by
-an attacker to assume a `nixbld` identity and interfere with subsequent
-builds running under the same UID.
-
-To prevent this issue, Nix now disallows builders to create setuid and
-setgid binaries. On Linux, this is done using a seccomp BPF filter. Note
-that this imposes a small performance penalty (e.g. 1% when building GNU
-Hello). Using seccomp, we now also prevent the creation of extended
-attributes and POSIX ACLs since these cannot be represented in the NAR
-format and (in the case of POSIX ACLs) allow bypassing regular Nix store
-permissions. On macOS, the restriction is implemented using the existing
-sandbox mechanism, which now uses a minimal “allow all except the
-creation of setuid/setgid binaries” profile when regular sandboxing is
-disabled. On other platforms, the “build user” mechanism is now
-disabled.
-
-Thanks go to Linus Heckemann for discovering and reporting this bug.
diff --git a/doc/manual/src/release-notes/rl-1.11.md b/doc/manual/src/release-notes/rl-1.11.md
deleted file mode 100644
index 8108114b8..000000000
--- a/doc/manual/src/release-notes/rl-1.11.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Release 1.11 (2016-01-19)
-
-This is primarily a bug fix release. It also has a number of new
-features:
-
- - `nix-prefetch-url` can now download URLs specified in a Nix
- expression. For example,
-
- $ nix-prefetch-url -A hello.src
-
- will prefetch the file specified by the `fetchurl` call in the
- attribute `hello.src` from the Nix expression in the current
- directory, and print the cryptographic hash of the resulting file on
- stdout. This differs from `nix-build -A
- hello.src` in that it doesn't verify the hash, and is thus useful
- when you’re updating a Nix expression.
-
- You can also prefetch the result of functions that unpack a tarball,
- such as `fetchFromGitHub`. For example:
-
- $ nix-prefetch-url --unpack https://github.com/NixOS/patchelf/archive/0.8.tar.gz
-
- or from a Nix expression:
-
- $ nix-prefetch-url -A nix-repl.src
-
- - The builtin function `` now supports downloading
- and unpacking NARs. This removes the need to have multiple downloads
- in the Nixpkgs stdenv bootstrap process (like a separate busybox
- binary for Linux, or curl/mkdir/sh/bzip2 for Darwin). Now all those
- files can be combined into a single NAR, optionally compressed using
- `xz`.
-
- - Nix now supports SHA-512 hashes for verifying fixed-output
- derivations, and in `builtins.hashString`.
-
- - The new flag `--option build-repeat
- N` will cause every build to be executed *N*+1 times. If the build
- output differs between any round, the build is rejected, and the
- output paths are not registered as valid. This is primarily useful
- to verify build determinism. (We already had a `--check` option to
- repeat a previously succeeded build. However, with `--check`,
- non-deterministic builds are registered in the DB. Preventing that
- is useful for Hydra to ensure that non-deterministic builds don't
- end up getting published to the binary cache.)
-
- - The options `--check` and `--option
- build-repeat N`, if they detect a difference between two runs of the
- same derivation and `-K` is given, will make the output of the other
- run available under `store-path-check`. This makes it easier to
- investigate the non-determinism using tools like `diffoscope`, e.g.,
-
- $ nix-build pkgs/stdenv/linux -A stage1.pkgs.zlib --check -K
- error: derivation ‘/nix/store/l54i8wlw2265…-zlib-1.2.8.drv’ may not
- be deterministic: output ‘/nix/store/11a27shh6n2i…-zlib-1.2.8’
- differs from ‘/nix/store/11a27shh6n2i…-zlib-1.2.8-check’
-
- $ diffoscope /nix/store/11a27shh6n2i…-zlib-1.2.8 /nix/store/11a27shh6n2i…-zlib-1.2.8-check
- …
- ├── lib/libz.a
- │ ├── metadata
- │ │ @@ -1,15 +1,15 @@
- │ │ -rw-r--r-- 30001/30000 3096 Jan 12 15:20 2016 adler32.o
- …
- │ │ +rw-r--r-- 30001/30000 3096 Jan 12 15:28 2016 adler32.o
- …
-
- - Improved FreeBSD support.
-
- - `nix-env -qa --xml --meta` now prints license information.
-
- - The maximum number of parallel TCP connections that the binary cache
- substituter will use has been decreased from 150 to 25. This should
- prevent upsetting some broken NAT routers, and also improves
- performance.
-
- - All "chroot"-containing strings got renamed to "sandbox". In
- particular, some Nix options got renamed, but the old names are
- still accepted as lower-priority aliases.
-
-This release has contributions from Anders Claesson, Anthony Cowley,
-Bjørn Forsman, Brian McKenna, Danny Wilson, davidak, Eelco Dolstra,
-Fabian Schmitthenner, FrankHB, Ilya Novoselov, janus, Jim Garrison, John
-Ericson, Jude Taylor, Ludovic Courtès, Manuel Jacob, Mathnerd314, Pascal
-Wittmann, Peter Simons, Philip Potter, Preston Bennes, Rommel M.
-Martinez, Sander van der Burg, Shea Levy, Tim Cuthbertson, Tuomas
-Tynkkynen, Utku Demir and Vladimír Čunát.
diff --git a/doc/manual/src/release-notes/rl-1.2.md b/doc/manual/src/release-notes/rl-1.2.md
deleted file mode 100644
index 0a30e8909..000000000
--- a/doc/manual/src/release-notes/rl-1.2.md
+++ /dev/null
@@ -1,97 +0,0 @@
-# Release 1.2 (2012-12-06)
-
-This release has the following improvements and changes:
-
- - Nix has a new binary substituter mechanism: the *binary cache*. A
- binary cache contains pre-built binaries of Nix packages. Whenever
- Nix wants to build a missing Nix store path, it will check a set of
- binary caches to see if any of them has a pre-built binary of that
- path. The configuration setting `binary-caches` contains a list of
- URLs of binary caches. For instance, doing
-
- $ nix-env -i thunderbird --option binary-caches http://cache.nixos.org
-
- will install Thunderbird and its dependencies, using the available
- pre-built binaries in . The main advantage
- over the old “manifest”-based method of getting pre-built binaries
- is that you don’t have to worry about your manifest being in sync
- with the Nix expressions you’re installing from; i.e., you don’t
- need to run `nix-pull` to update your manifest. It’s also more
- scalable because you don’t need to redownload a giant manifest file
- every time.
-
- A Nix channel can provide a binary cache URL that will be used
- automatically if you subscribe to that channel. If you use the
- Nixpkgs or NixOS channels () you
- automatically get the cache .
-
- Binary caches are created using `nix-push`. For details on the
- operation and format of binary caches, see the `nix-push` manpage.
- More details are provided in [this nix-dev
- posting](https://nixos.org/nix-dev/2012-September/009826.html).
-
- - Multiple output support should now be usable. A derivation can
- declare that it wants to produce multiple store paths by saying
- something like
-
- outputs = [ "lib" "headers" "doc" ];
-
- This will cause Nix to pass the intended store path of each output
- to the builder through the environment variables `lib`, `headers`
- and `doc`. Other packages can refer to a specific output by
- referring to `pkg.output`, e.g.
-
- buildInputs = [ pkg.lib pkg.headers ];
-
- If you install a package with multiple outputs using `nix-env`, each
- output path will be symlinked into the user environment.
-
- - Dashes are now valid as part of identifiers and attribute names.
-
- - The new operation `nix-store --repair-path` allows corrupted or
- missing store paths to be repaired by redownloading them. `nix-store
- --verify --check-contents
- --repair` will scan and repair all paths in the Nix store.
- Similarly, `nix-env`, `nix-build`, `nix-instantiate` and `nix-store
- --realise` have a `--repair` flag to detect and fix bad paths by
- rebuilding or redownloading them.
-
- - Nix no longer sets the immutable bit on files in the Nix store.
- Instead, the recommended way to guard the Nix store against
- accidental modification on Linux is to make it a read-only bind
- mount, like this:
-
- $ mount --bind /nix/store /nix/store
- $ mount -o remount,ro,bind /nix/store
-
- Nix will automatically make `/nix/store` writable as needed (using a
- private mount namespace) to allow modifications.
-
- - Store optimisation (replacing identical files in the store with hard
- links) can now be done automatically every time a path is added to
- the store. This is enabled by setting the configuration option
- `auto-optimise-store` to `true` (disabled by default).
-
- - Nix now supports `xz` compression for NARs in addition to `bzip2`.
- It compresses about 30% better on typical archives and decompresses
- about twice as fast.
-
- - Basic Nix expression evaluation profiling: setting the environment
- variable `NIX_COUNT_CALLS` to `1` will cause Nix to print how many
- times each primop or function was executed.
-
- - New primops: `concatLists`, `elem`, `elemAt` and `filter`.
-
- - The command `nix-copy-closure` has a new flag `--use-substitutes`
- (`-s`) to download missing paths on the target machine using the
- substitute mechanism.
-
- - The command `nix-worker` has been renamed to `nix-daemon`. Support
- for running the Nix worker in “slave” mode has been removed.
-
- - The `--help` flag of every Nix command now invokes `man`.
-
- - Chroot builds are now supported on systemd machines.
-
-This release has contributions from Eelco Dolstra, Florian Friesdorf,
-Mats Erik Andersson and Shea Levy.
diff --git a/doc/manual/src/release-notes/rl-1.3.md b/doc/manual/src/release-notes/rl-1.3.md
deleted file mode 100644
index 0c7b48380..000000000
--- a/doc/manual/src/release-notes/rl-1.3.md
+++ /dev/null
@@ -1,10 +0,0 @@
-# Release 1.3 (2013-01-04)
-
-This is primarily a bug fix release. When this version is first run on
-Linux, it removes any immutable bits from the Nix store and increases
-the schema version of the Nix store. (The previous release removed
-support for setting the immutable bit; this release clears any remaining
-immutable bits to make certain operations more efficient.)
-
-This release has contributions from Eelco Dolstra and Stuart
-Pernsteiner.
diff --git a/doc/manual/src/release-notes/rl-1.4.md b/doc/manual/src/release-notes/rl-1.4.md
deleted file mode 100644
index d23de71ad..000000000
--- a/doc/manual/src/release-notes/rl-1.4.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# Release 1.4 (2013-02-26)
-
-This release fixes a security bug in multi-user operation. It was
-possible for derivations to cause the mode of files outside of the Nix
-store to be changed to 444 (read-only but world-readable) by creating
-hard links to those files
-([details](https://github.com/NixOS/nix/commit/5526a282b5b44e9296e61e07d7d2626a79141ac4)).
-
-There are also the following improvements:
-
- - New built-in function: `builtins.hashString`.
-
- - Build logs are now stored in `/nix/var/log/nix/drvs/XX/`, where *XX*
- is the first two characters of the derivation. This is useful on
- machines that keep a lot of build logs (such as Hydra servers).
-
- - The function `corepkgs/fetchurl` can now make the downloaded file
- executable. This will allow getting rid of all bootstrap binaries in
- the Nixpkgs source tree.
-
- - Language change: The expression `"${./path}
- ..."` now evaluates to a string instead of a path.
diff --git a/doc/manual/src/release-notes/rl-1.5.1.md b/doc/manual/src/release-notes/rl-1.5.1.md
deleted file mode 100644
index 72b29518e..000000000
--- a/doc/manual/src/release-notes/rl-1.5.1.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Release 1.5.1 (2013-02-28)
-
-The bug fix to the bug fix had a bug itself, of course. But this time it
-will work for sure\!
diff --git a/doc/manual/src/release-notes/rl-1.5.2.md b/doc/manual/src/release-notes/rl-1.5.2.md
deleted file mode 100644
index 508580554..000000000
--- a/doc/manual/src/release-notes/rl-1.5.2.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Release 1.5.2 (2013-05-13)
-
-This is primarily a bug fix release. It has contributions from Eelco
-Dolstra, Lluís Batlle i Rossell and Shea Levy.
diff --git a/doc/manual/src/release-notes/rl-1.5.md b/doc/manual/src/release-notes/rl-1.5.md
deleted file mode 100644
index d2ccf8a5d..000000000
--- a/doc/manual/src/release-notes/rl-1.5.md
+++ /dev/null
@@ -1,4 +0,0 @@
-# Release 1.5 (2013-02-27)
-
-This is a brown paper bag release to fix a regression introduced by the
-hard link security fix in 1.4.
diff --git a/doc/manual/src/release-notes/rl-1.6.1.md b/doc/manual/src/release-notes/rl-1.6.1.md
deleted file mode 100644
index 9bb9bb1f8..000000000
--- a/doc/manual/src/release-notes/rl-1.6.1.md
+++ /dev/null
@@ -1,32 +0,0 @@
-# Release 1.6.1 (2013-10-28)
-
-This is primarily a bug fix release. Changes of interest are:
-
- - Nix 1.6 accidentally changed the semantics of antiquoted paths in
- strings, such as `"${/foo}/bar"`. This release reverts to the Nix
- 1.5.3 behaviour.
-
- - Previously, Nix optimised expressions such as `"${expr}"` to *expr*.
- Thus it neither checked whether *expr* could be coerced to a string,
- nor applied such coercions. This meant that `"${123}"` evaluatued to
- `123`, and `"${./foo}"` evaluated to `./foo` (even though `"${./foo}
- "` evaluates to `"/nix/store/hash-foo "`). Nix now checks the type
- of antiquoted expressions and applies coercions.
-
- - Nix now shows the exact position of undefined variables. In
- particular, undefined variable errors in a `with` previously didn't
- show *any* position information, so this makes it a lot easier to
- fix such errors.
-
- - Undefined variables are now treated consistently. Previously, the
- `tryEval` function would catch undefined variables inside a `with`
- but not outside. Now `tryEval` never catches undefined variables.
-
- - Bash completion in `nix-shell` now works correctly.
-
- - Stack traces are less verbose: they no longer show calls to builtin
- functions and only show a single line for each derivation on the
- call stack.
-
- - New built-in function: `builtins.typeOf`, which returns the type of
- its argument as a string.
diff --git a/doc/manual/src/release-notes/rl-1.6.md b/doc/manual/src/release-notes/rl-1.6.md
deleted file mode 100644
index 1d517ce1a..000000000
--- a/doc/manual/src/release-notes/rl-1.6.md
+++ /dev/null
@@ -1,72 +0,0 @@
-# Release 1.6 (2013-09-10)
-
-In addition to the usual bug fixes, this release has several new
-features:
-
- - The command `nix-build --run-env` has been renamed to `nix-shell`.
-
- - `nix-shell` now sources `$stdenv/setup` *inside* the interactive
- shell, rather than in a parent shell. This ensures that shell
- functions defined by `stdenv` can be used in the interactive shell.
-
- - `nix-shell` has a new flag `--pure` to clear the environment, so you
- get an environment that more closely corresponds to the “real” Nix
- build.
-
- - `nix-shell` now sets the shell prompt (`PS1`) to ensure that Nix
- shells are distinguishable from your regular shells.
-
- - `nix-env` no longer requires a `*` argument to match all packages,
- so `nix-env -qa` is equivalent to `nix-env
- -qa '*'`.
-
- - `nix-env -i` has a new flag `--remove-all` (`-r`) to remove all
- previous packages from the profile. This makes it easier to do
- declarative package management similar to NixOS’s
- `environment.systemPackages`. For instance, if you have a
- specification `my-packages.nix` like this:
-
- with import {};
- [ thunderbird
- geeqie
- ...
- ]
-
- then after any change to this file, you can run:
-
- $ nix-env -f my-packages.nix -ir
-
- to update your profile to match the specification.
-
- - The ‘`with`’ language construct is now more lazy. It only evaluates
- its argument if a variable might actually refer to an attribute in
- the argument. For instance, this now works:
-
- let
- pkgs = with pkgs; { foo = "old"; bar = foo; } // overrides;
- overrides = { foo = "new"; };
- in pkgs.bar
-
- This evaluates to `"new"`, while previously it gave an “infinite
- recursion” error.
-
- - Nix now has proper integer arithmetic operators. For instance, you
- can write `x + y` instead of `builtins.add x y`, or `x <
- y` instead of `builtins.lessThan x y`. The comparison operators also
- work on strings.
-
- - On 64-bit systems, Nix integers are now 64 bits rather than 32 bits.
-
- - When using the Nix daemon, the `nix-daemon` worker process now runs
- on the same CPU as the client, on systems that support setting CPU
- affinity. This gives a significant speedup on some systems.
-
- - If a stack overflow occurs in the Nix evaluator, you now get a
- proper error message (rather than “Segmentation fault”) on some
- systems.
-
- - In addition to directories, you can now bind-mount regular files in
- chroots through the (now misnamed) option `build-chroot-dirs`.
-
-This release has contributions from Domen Kožar, Eelco Dolstra, Florian
-Friesdorf, Gergely Risko, Ivan Kozik, Ludovic Courtès and Shea Levy.
diff --git a/doc/manual/src/release-notes/rl-1.7.md b/doc/manual/src/release-notes/rl-1.7.md
deleted file mode 100644
index 8c3a9f357..000000000
--- a/doc/manual/src/release-notes/rl-1.7.md
+++ /dev/null
@@ -1,140 +0,0 @@
-# Release 1.7 (2014-04-11)
-
-In addition to the usual bug fixes, this release has the following new
-features:
-
- - Antiquotation is now allowed inside of quoted attribute names (e.g.
- `set."${foo}"`). In the case where the attribute name is just a
- single antiquotation, the quotes can be dropped (e.g. the above
- example can be written `set.${foo}`). If an attribute name inside of
- a set declaration evaluates to `null` (e.g. `{ ${null} = false; }`),
- then that attribute is not added to the set.
-
- - Experimental support for cryptographically signed binary caches. See
- [the commit for
- details](https://github.com/NixOS/nix/commit/0fdf4da0e979f992db75cc17376e455ddc5a96d8).
-
- - An experimental new substituter, `download-via-ssh`, that fetches
- binaries from remote machines via SSH. Specifying the flags
- `--option
- use-ssh-substituter true --option ssh-substituter-hosts
- user@hostname` will cause Nix to download binaries from the
- specified machine, if it has them.
-
- - `nix-store -r` and `nix-build` have a new flag, `--check`, that
- builds a previously built derivation again, and prints an error
- message if the output is not exactly the same. This helps to verify
- whether a derivation is truly deterministic. For example:
-
- $ nix-build '' -A patchelf
- …
- $ nix-build '' -A patchelf --check
- …
- error: derivation `/nix/store/1ipvxs…-patchelf-0.6' may not be deterministic:
- hash mismatch in output `/nix/store/4pc1dm…-patchelf-0.6.drv'
-
- - The `nix-instantiate` flags `--eval-only` and `--parse-only` have
- been renamed to `--eval` and `--parse`, respectively.
-
- - `nix-instantiate`, `nix-build` and `nix-shell` now have a flag
- `--expr` (or `-E`) that allows you to specify the expression to be
- evaluated as a command line argument. For instance, `nix-instantiate
- --eval -E
- '1 + 2'` will print `3`.
-
- - `nix-shell` improvements:
-
- - It has a new flag, `--packages` (or `-p`), that sets up a build
- environment containing the specified packages from Nixpkgs. For
- example, the command
-
- $ nix-shell -p sqlite xorg.libX11 hello
-
- will start a shell in which the given packages are present.
-
- - It now uses `shell.nix` as the default expression, falling back
- to `default.nix` if the former doesn’t exist. This makes it
- convenient to have a `shell.nix` in your project to set up a
- nice development environment.
-
- - It evaluates the derivation attribute `shellHook`, if set. Since
- `stdenv` does not normally execute this hook, it allows you to
- do `nix-shell`-specific setup.
-
- - It preserves the user’s timezone setting.
-
- - In chroots, Nix now sets up a `/dev` containing only a minimal set
- of devices (such as `/dev/null`). Note that it only does this if you
- *don’t* have `/dev` listed in your `build-chroot-dirs` setting;
- otherwise, it will bind-mount the `/dev` from outside the chroot.
-
- Similarly, if you don’t have `/dev/pts` listed in
- `build-chroot-dirs`, Nix will mount a private `devpts` filesystem on
- the chroot’s `/dev/pts`.
-
- - New built-in function: `builtins.toJSON`, which returns a JSON
- representation of a value.
-
- - `nix-env -q` has a new flag `--json` to print a JSON representation
- of the installed or available packages.
-
- - `nix-env` now supports meta attributes with more complex values,
- such as attribute sets.
-
- - The `-A` flag now allows attribute names with dots in them, e.g.
-
- $ nix-instantiate --eval '' -A 'config.systemd.units."nscd.service".text'
-
- - The `--max-freed` option to `nix-store --gc` now accepts a unit
- specifier. For example, `nix-store --gc --max-freed
- 1G` will free up to 1 gigabyte of disk space.
-
- - `nix-collect-garbage` has a new flag `--delete-older-than` *N*`d`,
- which deletes all user environment generations older than *N* days.
- Likewise, `nix-env
- --delete-generations` accepts a *N*`d` age limit.
-
- - Nix now heuristically detects whether a build failure was due to a
- disk-full condition. In that case, the build is not flagged as
- “permanently failed”. This is mostly useful for Hydra, which needs
- to distinguish between permanent and transient build failures.
-
- - There is a new symbol `__curPos` that expands to an attribute set
- containing its file name and line and column numbers, e.g. `{ file =
- "foo.nix"; line = 10;
- column = 5; }`. There also is a new builtin function,
- `unsafeGetAttrPos`, that returns the position of an attribute. This
- is used by Nixpkgs to provide location information in error
- messages, e.g.
-
- $ nix-build '' -A libreoffice --argstr system x86_64-darwin
- error: the package ‘libreoffice-4.0.5.2’ in ‘.../applications/office/libreoffice/default.nix:263’
- is not supported on ‘x86_64-darwin’
-
- - The garbage collector is now more concurrent with other Nix
- processes because it releases certain locks earlier.
-
- - The binary tarball installer has been improved. You can now install
- Nix by running:
-
- $ bash <(curl -L https://nixos.org/nix/install)
-
- - More evaluation errors include position information. For instance,
- selecting a missing attribute will print something like
-
- error: attribute `nixUnstabl' missing, at /etc/nixos/configurations/misc/eelco/mandark.nix:216:15
-
- - The command `nix-setuid-helper` is gone.
-
- - Nix no longer uses Automake, but instead has a non-recursive, GNU
- Make-based build system.
-
- - All installed libraries now have the prefix `libnix`. In particular,
- this gets rid of `libutil`, which could clash with libraries with
- the same name from other packages.
-
- - Nix now requires a compiler that supports C++11.
-
-This release has contributions from Danny Wilson, Domen Kožar, Eelco
-Dolstra, Ian-Woo Kim, Ludovic Courtès, Maxim Ivanov, Petr Rockai,
-Ricardo M. Correia and Shea Levy.
diff --git a/doc/manual/src/release-notes/rl-1.8.md b/doc/manual/src/release-notes/rl-1.8.md
deleted file mode 100644
index 242ab380b..000000000
--- a/doc/manual/src/release-notes/rl-1.8.md
+++ /dev/null
@@ -1,88 +0,0 @@
-# Release 1.8 (2014-12-14)
-
- - Breaking change: to address a race condition, the remote build hook
- mechanism now uses `nix-store
- --serve` on the remote machine. This requires build slaves to be
- updated to Nix 1.8.
-
- - Nix now uses HTTPS instead of HTTP to access the default binary
- cache, `cache.nixos.org`.
-
- - `nix-env` selectors are now regular expressions. For instance, you
- can do
-
- $ nix-env -qa '.*zip.*'
-
- to query all packages with a name containing `zip`.
-
- - `nix-store --read-log` can now fetch remote build logs. If a build
- log is not available locally, then ‘nix-store -l’ will now try to
- download it from the servers listed in the ‘log-servers’ option in
- nix.conf. For instance, if you have the configuration option
-
- log-servers = http://hydra.nixos.org/log
-
- then it will try to get logs from `http://hydra.nixos.org/log/base
- name of the
- store path`. This allows you to do things like:
-
- $ nix-store -l $(which xterm)
-
- and get a log even if `xterm` wasn't built locally.
-
- - New builtin functions: `attrValues`, `deepSeq`, `fromJSON`,
- `readDir`, `seq`.
-
- - `nix-instantiate --eval` now has a `--json` flag to print the
- resulting value in JSON format.
-
- - `nix-copy-closure` now uses `nix-store --serve` on the remote side
- to send or receive closures. This fixes a race condition between
- `nix-copy-closure` and the garbage collector.
-
- - Derivations can specify the new special attribute
- `allowedRequisites`, which has a similar meaning to
- `allowedReferences`. But instead of only enforcing to explicitly
- specify the immediate references, it requires the derivation to
- specify all the dependencies recursively (hence the name,
- requisites) that are used by the resulting output.
-
- - On Mac OS X, Nix now handles case collisions when importing closures
- from case-sensitive file systems. This is mostly useful for running
- NixOps on Mac OS X.
-
- - The Nix daemon has new configuration options `allowed-users`
- (specifying the users and groups that are allowed to connect to the
- daemon) and `trusted-users` (specifying the users and groups that
- can perform privileged operations like specifying untrusted binary
- caches).
-
- - The configuration option `build-cores` now defaults to the number of
- available CPU cores.
-
- - Build users are now used by default when Nix is invoked as root.
- This prevents builds from accidentally running as root.
-
- - Nix now includes systemd units and Upstart jobs.
-
- - Speed improvements to `nix-store
- --optimise`.
-
- - Language change: the `==` operator now ignores string contexts (the
- “dependencies” of a string).
-
- - Nix now filters out Nix-specific ANSI escape sequences on standard
- error. They are supposed to be invisible, but some terminals show
- them anyway.
-
- - Various commands now automatically pipe their output into the pager
- as specified by the `PAGER` environment variable.
-
- - Several improvements to reduce memory consumption in the evaluator.
-
-This release has contributions from Adam Szkoda, Aristid Breitkreuz, Bob
-van der Linden, Charles Strahan, darealshinji, Eelco Dolstra, Gergely
-Risko, Joel Taylor, Ludovic Courtès, Marko Durkovic, Mikey Ariel, Paul
-Colomiets, Ricardo M. Correia, Ricky Elrod, Robert Helgesson, Rob
-Vermaas, Russell O'Connor, Shea Levy, Shell Turner, Sönke Hahn, Steve
-Purcell, Vladimír Čunát and Wout Mertens.
diff --git a/doc/manual/src/release-notes/rl-1.9.md b/doc/manual/src/release-notes/rl-1.9.md
deleted file mode 100644
index b56e3a9fc..000000000
--- a/doc/manual/src/release-notes/rl-1.9.md
+++ /dev/null
@@ -1,143 +0,0 @@
-# Release 1.9 (2015-06-12)
-
-In addition to the usual bug fixes, this release has the following new
-features:
-
- - Signed binary cache support. You can enable signature checking by
- adding the following to `nix.conf`:
-
- signed-binary-caches = *
- binary-cache-public-keys = cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
-
- This will prevent Nix from downloading any binary from the cache
- that is not signed by one of the keys listed in
- `binary-cache-public-keys`.
-
- Signature checking is only supported if you built Nix with the
- `libsodium` package.
-
- Note that while Nix has had experimental support for signed binary
- caches since version 1.7, this release changes the signature format
- in a backwards-incompatible way.
-
- - Automatic downloading of Nix expression tarballs. In various places,
- you can now specify the URL of a tarball containing Nix expressions
- (such as Nixpkgs), which will be downloaded and unpacked
- automatically. For example:
-
- - In `nix-env`:
-
- $ nix-env -f https://github.com/NixOS/nixpkgs-channels/archive/nixos-14.12.tar.gz -iA firefox
-
- This installs Firefox from the latest tested and built revision
- of the NixOS 14.12 channel.
-
- - In `nix-build` and `nix-shell`:
-
- $ nix-build https://github.com/NixOS/nixpkgs/archive/master.tar.gz -A hello
-
- This builds GNU Hello from the latest revision of the Nixpkgs
- master branch.
-
- - In the Nix search path (as specified via `NIX_PATH` or `-I`).
- For example, to start a shell containing the Pan package from a
- specific version of Nixpkgs:
-
- $ nix-shell -p pan -I nixpkgs=https://github.com/NixOS/nixpkgs-channels/archive/8a3eea054838b55aca962c3fbde9c83c102b8bf2.tar.gz
-
- - In `nixos-rebuild` (on NixOS):
-
- $ nixos-rebuild test -I nixpkgs=https://github.com/NixOS/nixpkgs-channels/archive/nixos-unstable.tar.gz
-
- - In Nix expressions, via the new builtin function `fetchTarball`:
-
- with import (fetchTarball https://github.com/NixOS/nixpkgs-channels/archive/nixos-14.12.tar.gz) {}; …
-
- (This is not allowed in restricted mode.)
-
- - `nix-shell` improvements:
-
- - `nix-shell` now has a flag `--run` to execute a command in the
- `nix-shell` environment, e.g. `nix-shell --run make`. This is
- like the existing `--command` flag, except that it uses a
- non-interactive shell (ensuring that hitting Ctrl-C won’t drop
- you into the child shell).
-
- - `nix-shell` can now be used as a `#!`-interpreter. This allows
- you to write scripts that dynamically fetch their own
- dependencies. For example, here is a Haskell script that, when
- invoked, first downloads GHC and the Haskell packages on which
- it depends:
-
- #! /usr/bin/env nix-shell
- #! nix-shell -i runghc -p haskellPackages.ghc haskellPackages.HTTP
-
- import Network.HTTP
-
- main = do
- resp <- Network.HTTP.simpleHTTP (getRequest "http://nixos.org/")
- body <- getResponseBody resp
- print (take 100 body)
-
- Of course, the dependencies are cached in the Nix store, so the
- second invocation of this script will be much faster.
-
- - Chroot improvements:
-
- - Chroot builds are now supported on Mac OS X (using its sandbox
- mechanism).
-
- - If chroots are enabled, they are now used for all derivations,
- including fixed-output derivations (such as `fetchurl`). The
- latter do have network access, but can no longer access the host
- filesystem. If you need the old behaviour, you can set the
- option `build-use-chroot` to `relaxed`.
-
- - On Linux, if chroots are enabled, builds are performed in a
- private PID namespace once again. (This functionality was lost
- in Nix 1.8.)
-
- - Store paths listed in `build-chroot-dirs` are now automatically
- expanded to their closure. For instance, if you want
- `/nix/store/…-bash/bin/sh` mounted in your chroot as `/bin/sh`,
- you only need to say `build-chroot-dirs =
- /bin/sh=/nix/store/…-bash/bin/sh`; it is no longer necessary to
- specify the dependencies of Bash.
-
- - The new derivation attribute `passAsFile` allows you to specify that
- the contents of derivation attributes should be passed via files
- rather than environment variables. This is useful if you need to
- pass very long strings that exceed the size limit of the
- environment. The Nixpkgs function `writeTextFile` uses this.
-
- - You can now use `~` in Nix file names to refer to your home
- directory, e.g. `import
- ~/.nixpkgs/config.nix`.
-
- - Nix has a new option `restrict-eval` that allows limiting what paths
- the Nix evaluator has access to. By passing `--option restrict-eval
- true` to Nix, the evaluator will throw an exception if an attempt is
- made to access any file outside of the Nix search path. This is
- primarily intended for Hydra to ensure that a Hydra jobset only
- refers to its declared inputs (and is therefore reproducible).
-
- - `nix-env` now only creates a new “generation” symlink in
- `/nix/var/nix/profiles` if something actually changed.
-
- - The environment variable `NIX_PAGER` can now be set to override
- `PAGER`. You can set it to `cat` to disable paging for Nix commands
- only.
-
- - Failing `<...>` lookups now show position information.
-
- - Improved Boehm GC use: we disabled scanning for interior pointers,
- which should reduce the “`Repeated
- allocation of very large block`” warnings and associated retention
- of memory.
-
-This release has contributions from aszlig, Benjamin Staffin, Charles
-Strahan, Christian Theune, Daniel Hahler, Danylo Hlynskyi Daniel
-Peebles, Dan Peebles, Domen Kožar, Eelco Dolstra, Harald van Dijk, Hoang
-Xuan Phu, Jaka Hudoklin, Jeff Ramnani, j-keck, Linquize, Luca Bruno,
-Michael Merickel, Oliver Dunkl, Rob Vermaas, Rok Garbas, Shea Levy,
-Tobias Geerinckx-Rice and William A. Kennington III.
diff --git a/doc/manual/src/release-notes/rl-2.0.md b/doc/manual/src/release-notes/rl-2.0.md
deleted file mode 100644
index aad0de211..000000000
--- a/doc/manual/src/release-notes/rl-2.0.md
+++ /dev/null
@@ -1,558 +0,0 @@
-# Release 2.0 (2018-02-22)
-
-The following incompatible changes have been made:
-
- - The manifest-based substituter mechanism
- (`download-using-manifests`) has been
- [removed](https://github.com/NixOS/nix/commit/867967265b80946dfe1db72d40324b4f9af988ed).
- It has been superseded by the binary cache substituter mechanism
- since several years. As a result, the following programs have been
- removed:
-
- - `nix-pull`
-
- - `nix-generate-patches`
-
- - `bsdiff`
-
- - `bspatch`
-
- - The “copy from other stores” substituter mechanism
- (`copy-from-other-stores` and the `NIX_OTHER_STORES` environment
- variable) has been removed. It was primarily used by the NixOS
- installer to copy available paths from the installation medium. The
- replacement is to use a chroot store as a substituter (e.g.
- `--substituters /mnt`), or to build into a chroot store (e.g.
- `--store /mnt --substituters /`).
-
- - The command `nix-push` has been removed as part of the effort to
- eliminate Nix's dependency on Perl. You can use `nix copy` instead,
- e.g. `nix copy
- --to file:///tmp/my-binary-cache paths…`
-
- - The “nested” log output feature (`--log-type
- pretty`) has been removed. As a result, `nix-log2xml` was also
- removed.
-
- - OpenSSL-based signing has been
- [removed](https://github.com/NixOS/nix/commit/f435f8247553656774dd1b2c88e9de5d59cab203).
- This feature was never well-supported. A better alternative is
- provided by the `secret-key-files` and `trusted-public-keys`
- options.
-
- - Failed build caching has been
- [removed](https://github.com/NixOS/nix/commit/8cffec84859cec8b610a2a22ab0c4d462a9351ff).
- This feature was introduced to support the Hydra continuous build
- system, but Hydra no longer uses it.
-
- - `nix-mode.el` has been removed from Nix. It is now [a separate
- repository](https://github.com/NixOS/nix-mode) and can be installed
- through the MELPA package repository.
-
-This release has the following new features:
-
- - It introduces a new command named `nix`, which is intended to
- eventually replace all `nix-*` commands with a more consistent and
- better designed user interface. It currently provides replacements
- for some (but not all) of the functionality provided by `nix-store`,
- `nix-build`, `nix-shell -p`, `nix-env -qa`, `nix-instantiate
- --eval`, `nix-push` and `nix-copy-closure`. It has the following
- major features:
-
- - Unlike the legacy commands, it has a consistent way to refer to
- packages and package-like arguments (like store paths). For
- example, the following commands all copy the GNU Hello package
- to a remote machine:
-
- nix copy --to ssh://machine nixpkgs.hello
-
- nix copy --to ssh://machine /nix/store/0i2jd68mp5g6h2sa5k9c85rb80sn8hi9-hello-2.10
-
- nix copy --to ssh://machine '(with import {}; hello)'
-
- By contrast, `nix-copy-closure` only accepted store paths as
- arguments.
-
- - It is self-documenting: `--help` shows all available
- command-line arguments. If `--help` is given after a subcommand,
- it shows examples for that subcommand. `nix
- --help-config` shows all configuration options.
-
- - It is much less verbose. By default, it displays a single-line
- progress indicator that shows how many packages are left to be
- built or downloaded, and (if there are running builds) the most
- recent line of builder output. If a build fails, it shows the
- last few lines of builder output. The full build log can be
- retrieved using `nix
- log`.
-
- - It
- [provides](https://github.com/NixOS/nix/commit/b8283773bd64d7da6859ed520ee19867742a03ba)
- all `nix.conf` configuration options as command line flags. For
- example, instead of `--option
- http-connections 100` you can write `--http-connections 100`.
- Boolean options can be written as `--foo` or `--no-foo` (e.g.
- `--no-auto-optimise-store`).
-
- - Many subcommands have a `--json` flag to write results to stdout
- in JSON format.
-
- > **Warning**
- >
- > Please note that the `nix` command is a work in progress and the
- > interface is subject to change.
-
- It provides the following high-level (“porcelain”) subcommands:
-
- - `nix build` is a replacement for `nix-build`.
-
- - `nix run` executes a command in an environment in which the
- specified packages are available. It is (roughly) a replacement
- for `nix-shell
- -p`. Unlike that command, it does not execute the command in a
- shell, and has a flag (`-c`) that specifies the unquoted command
- line to be executed.
-
- It is particularly useful in conjunction with chroot stores,
- allowing Linux users who do not have permission to install Nix
- in `/nix/store` to still use binary substitutes that assume
- `/nix/store`. For example,
-
- nix run --store ~/my-nix nixpkgs.hello -c hello --greeting 'Hi everybody!'
-
- downloads (or if not substitutes are available, builds) the GNU
- Hello package into `~/my-nix/nix/store`, then runs `hello` in a
- mount namespace where `~/my-nix/nix/store` is mounted onto
- `/nix/store`.
-
- - `nix search` replaces `nix-env
- -qa`. It searches the available packages for occurrences of a
- search string in the attribute name, package name or
- description. Unlike `nix-env -qa`, it has a cache to speed up
- subsequent searches.
-
- - `nix copy` copies paths between arbitrary Nix stores,
- generalising `nix-copy-closure` and `nix-push`.
-
- - `nix repl` replaces the external program `nix-repl`. It provides
- an interactive environment for evaluating and building Nix
- expressions. Note that it uses `linenoise-ng` instead of GNU
- Readline.
-
- - `nix upgrade-nix` upgrades Nix to the latest stable version.
- This requires that Nix is installed in a profile. (Thus it won’t
- work on NixOS, or if it’s installed outside of the Nix store.)
-
- - `nix verify` checks whether store paths are unmodified and/or
- “trusted” (see below). It replaces `nix-store --verify` and
- `nix-store
- --verify-path`.
-
- - `nix log` shows the build log of a package or path. If the
- build log is not available locally, it will try to obtain it
- from the configured substituters (such as
- [cache.nixos.org](https://cache.nixos.org/), which now
- provides build logs).
-
- - `nix edit` opens the source code of a package in your editor.
-
- - `nix eval` replaces `nix-instantiate --eval`.
-
- - `nix
- why-depends` shows why one store path has another in its
- closure. This is primarily useful to finding the causes of
- closure bloat. For example,
-
- nix why-depends nixpkgs.vlc nixpkgs.libdrm.dev
-
- shows a chain of files and fragments of file contents that cause
- the VLC package to have the “dev” output of `libdrm` in its
- closure — an undesirable situation.
-
- - `nix path-info` shows information about store paths, replacing
- `nix-store -q`. A useful feature is the option `--closure-size`
- (`-S`). For example, the following command show the closure
- sizes of every path in the current NixOS system closure, sorted
- by size:
-
- nix path-info -rS /run/current-system | sort -nk2
-
- - `nix optimise-store` replaces `nix-store --optimise`. The main
- difference is that it has a progress indicator.
-
- A number of low-level (“plumbing”) commands are also available:
-
- - `nix ls-store` and `nix
- ls-nar` list the contents of a store path or NAR file. The
- former is primarily useful in conjunction with remote stores,
- e.g.
-
- nix ls-store --store https://cache.nixos.org/ -lR /nix/store/0i2jd68mp5g6h2sa5k9c85rb80sn8hi9-hello-2.10
-
- lists the contents of path in a binary cache.
-
- - `nix cat-store` and `nix
- cat-nar` allow extracting a file from a store path or NAR file.
-
- - `nix dump-path` writes the contents of a store path to stdout in
- NAR format. This replaces `nix-store --dump`.
-
- - `nix
- show-derivation` displays a store derivation in JSON format.
- This is an alternative to `pp-aterm`.
-
- - `nix
- add-to-store` replaces `nix-store
- --add`.
-
- - `nix sign-paths` signs store paths.
-
- - `nix copy-sigs` copies signatures from one store to another.
-
- - `nix show-config` shows all configuration options and their
- current values.
-
- - The store abstraction that Nix has had for a long time to support
- store access via the Nix daemon has been extended
- significantly. In particular, substituters (which used to be
- external programs such as `download-from-binary-cache`) are now
- subclasses of the abstract `Store` class. This allows many Nix
- commands to operate on such store types. For example, `nix
- path-info` shows information about paths in your local Nix store,
- while `nix path-info --store https://cache.nixos.org/` shows
- information about paths in the specified binary cache. Similarly,
- `nix-copy-closure`, `nix-push` and substitution are all instances
- of the general notion of copying paths between different kinds of
- Nix stores.
-
- Stores are specified using an URI-like syntax, e.g.
- . The following store
- types are supported:
-
- - `LocalStore` (stori URI `local` or an absolute path) and the
- misnamed `RemoteStore` (`daemon`) provide access to a local Nix
- store, the latter via the Nix daemon. You can use `auto` or the
- empty string to auto-select a local or daemon store depending on
- whether you have write permission to the Nix store. It is no
- longer necessary to set the `NIX_REMOTE` environment variable to
- use the Nix daemon.
-
- As noted above, `LocalStore` now supports chroot builds,
- allowing the “physical” location of the Nix store (e.g.
- `/home/alice/nix/store`) to differ from its “logical” location
- (typically `/nix/store`). This allows non-root users to use Nix
- while still getting the benefits from prebuilt binaries from
- [cache.nixos.org](https://cache.nixos.org/).
-
- - `BinaryCacheStore` is the abstract superclass of all binary
- cache stores. It supports writing build logs and NAR content
- listings in JSON format.
-
- - `HttpBinaryCacheStore` (`http://`, `https://`) supports binary
- caches via HTTP or HTTPS. If the server supports `PUT` requests,
- it supports uploading store paths via commands such as `nix
- copy`.
-
- - `LocalBinaryCacheStore` (`file://`) supports binary caches in
- the local filesystem.
-
- - `S3BinaryCacheStore` (`s3://`) supports binary caches stored in
- Amazon S3, if enabled at compile time.
-
- - `LegacySSHStore` (`ssh://`) is used to implement remote builds
- and `nix-copy-closure`.
-
- - `SSHStore` (`ssh-ng://`) supports arbitrary Nix operations on a
- remote machine via the same protocol used by `nix-daemon`.
-
- - Security has been improved in various ways:
-
- - Nix now stores signatures for local store paths. When paths are
- copied between stores (e.g., copied from a binary cache to a
- local store), signatures are propagated.
-
- Locally-built paths are signed automatically using the secret
- keys specified by the `secret-key-files` store option.
- Secret/public key pairs can be generated using `nix-store
- --generate-binary-cache-key`.
-
- In addition, locally-built store paths are marked as “ultimately
- trusted”, but this bit is not propagated when paths are copied
- between stores.
-
- - Content-addressable store paths no longer require signatures —
- they can be imported into a store by unprivileged users even if
- they lack signatures.
-
- - The command `nix verify` checks whether the specified paths are
- trusted, i.e., have a certain number of trusted signatures, are
- ultimately trusted, or are content-addressed.
-
- - Substitutions from binary caches
- [now](https://github.com/NixOS/nix/commit/ecbc3fedd3d5bdc5a0e1a0a51b29062f2874ac8b)
- require signatures by default. This was already the case on
- NixOS.
-
- - In Linux sandbox builds, we
- [now](https://github.com/NixOS/nix/commit/eba840c8a13b465ace90172ff76a0db2899ab11b)
- use `/build` instead of `/tmp` as the temporary build directory.
- This fixes potential security problems when a build accidentally
- stores its `TMPDIR` in some security-sensitive place, such as an
- RPATH.
-
- - *Pure evaluation mode*. With the `--pure-eval` flag, Nix enables a
- variant of the existing restricted evaluation mode that forbids
- access to anything that could cause different evaluations of the
- same command line arguments to produce a different result. This
- includes builtin functions such as `builtins.getEnv`, but more
- importantly, *all* filesystem or network access unless a content
- hash or commit hash is specified. For example, calls to
- `builtins.fetchGit` are only allowed if a `rev` attribute is
- specified.
-
- The goal of this feature is to enable true reproducibility and
- traceability of builds (including NixOS system configurations) at
- the evaluation level. For example, in the future, `nixos-rebuild`
- might build configurations from a Nix expression in a Git repository
- in pure mode. That expression might fetch other repositories such as
- Nixpkgs via `builtins.fetchGit`. The commit hash of the top-level
- repository then uniquely identifies a running system, and, in
- conjunction with that repository, allows it to be reproduced or
- modified.
-
- - There are several new features to support binary reproducibility
- (i.e. to help ensure that multiple builds of the same derivation
- produce exactly the same output). When `enforce-determinism` is set
- to `false`, it’s [no
- longer](https://github.com/NixOS/nix/commit/8bdf83f936adae6f2c907a6d2541e80d4120f051)
- a fatal error if build rounds produce different output. Also, a hook
- named `diff-hook` is
- [provided](https://github.com/NixOS/nix/commit/9a313469a4bdea2d1e8df24d16289dc2a172a169)
- to allow you to run tools such as `diffoscope` when build rounds
- produce different output.
-
- - Configuring remote builds is a lot easier now. Provided you are not
- using the Nix daemon, you can now just specify a remote build
- machine on the command line, e.g. `--option builders
- 'ssh://my-mac x86_64-darwin'`. The environment variable
- `NIX_BUILD_HOOK` has been removed and is no longer needed. The
- environment variable `NIX_REMOTE_SYSTEMS` is still supported for
- compatibility, but it is also possible to specify builders in
- `nix.conf` by setting the option `builders =
- @path`.
-
- - If a fixed-output derivation produces a result with an incorrect
- hash, the output path is moved to the location corresponding to the
- actual hash and registered as valid. Thus, a subsequent build of the
- fixed-output derivation with the correct hash is unnecessary.
-
- - `nix-shell`
- [now](https://github.com/NixOS/nix/commit/ea59f39326c8e9dc42dfed4bcbf597fbce58797c)
- sets the `IN_NIX_SHELL` environment variable during evaluation and
- in the shell itself. This can be used to perform different actions
- depending on whether you’re in a Nix shell or in a regular build.
- Nixpkgs provides `lib.inNixShell` to check this variable during
- evaluation.
-
- - `NIX_PATH` is now lazy, so URIs in the path are only downloaded if
- they are needed for evaluation.
-
- - You can now use `channel:` as a short-hand for
- . For example,
- `nix-build channel:nixos-15.09 -A hello` will build the GNU Hello
- package from the `nixos-15.09` channel. In the future, this may
- use Git to fetch updates more efficiently.
-
- - When `--no-build-output` is given, the last 10 lines of the build
- log will be shown if a build fails.
-
- - Networking has been improved:
-
- - HTTP/2 is now supported. This makes binary cache lookups [much
- more
- efficient](https://github.com/NixOS/nix/commit/90ad02bf626b885a5dd8967894e2eafc953bdf92).
-
- - We now retry downloads on many HTTP errors, making binary caches
- substituters more resilient to temporary failures.
-
- - HTTP credentials can now be configured via the standard `netrc`
- mechanism.
-
- - If S3 support is enabled at compile time, ` now uses the content-addressable tarball cache
- at '` which can be recovered with
- `nix repl --file ''` or `nix repl --expr 'import {}'`.
-
- This is currently guarded by the `repl-flake` experimental feature.
-
-* A new function `builtins.traceVerbose` is available. It is similar
- to `builtins.trace` if the `trace-verbose` setting is set to true,
- and it is a no-op otherwise.
-
-* `nix search` has a new flag `--exclude` to filter out packages.
-
-* On Linux, if `/nix` doesn't exist and cannot be created and you're
- not running as root, Nix will automatically use
- `~/.local/share/nix/root` as a chroot store. This enables non-root
- users to download the statically linked Nix binary and have it work
- out of the box, e.g.
-
- ```
- # ~/nix run nixpkgs#hello
- warning: '/nix' does not exists, so Nix will use '/home/ubuntu/.local/share/nix/root' as a chroot store
- Hello, world!
- ```
-
-* `flake-registry.json` is now fetched from `channels.nixos.org`.
-
-* Nix can now be built with LTO by passing `--enable-lto` to `configure`.
- LTO is currently only supported when building with GCC.
diff --git a/doc/manual/src/release-notes/rl-2.11.md b/doc/manual/src/release-notes/rl-2.11.md
deleted file mode 100644
index b322a4e5e..000000000
--- a/doc/manual/src/release-notes/rl-2.11.md
+++ /dev/null
@@ -1,5 +0,0 @@
-# Release 2.11 (2022-08-24)
-
-* `nix copy` now copies the store paths in parallel as much as possible (again).
- This doesn't apply for the `daemon` and `ssh-ng` stores which copy everything
- in one batch to avoid latencies issues.
diff --git a/doc/manual/src/release-notes/rl-2.12.md b/doc/manual/src/release-notes/rl-2.12.md
deleted file mode 100644
index e2045d7bf..000000000
--- a/doc/manual/src/release-notes/rl-2.12.md
+++ /dev/null
@@ -1,43 +0,0 @@
-# Release 2.12 (2022-12-06)
-
-* On Linux, Nix can now run builds in a user namespace where they run
- as root (UID 0) and have 65,536 UIDs available.
-
- This is primarily useful for running containers such as `systemd-nspawn`
- inside a Nix build. For an example, see [`tests/systemd-nspawn/nix`][nspawn].
-
- [nspawn]: https://github.com/NixOS/nix/blob/67bcb99700a0da1395fa063d7c6586740b304598/tests/systemd-nspawn.nix.
-
- A build can enable this by setting the derivation attribute:
-
- ```
- requiredSystemFeatures = [ "uid-range" ];
- ```
-
- The `uid-range` [system feature] requires the [`auto-allocate-uids`]
- setting to be enabled.
-
- [system feature]: ../command-ref/conf-file.md#conf-system-features
-
-* Nix can now automatically pick UIDs for builds, removing the need to
- create `nixbld*` user accounts. See [`auto-allocate-uids`].
-
- [`auto-allocate-uids`]: ../command-ref/conf-file.md#conf-auto-allocate-uids
-
-* On Linux, Nix has experimental support for running builds inside a
- cgroup. See
- [`use-cgroups`](../command-ref/conf-file.md#conf-use-cgroups).
-
-* `` now accepts an additional argument `impure` which
- defaults to `false`. If it is set to `true`, the `hash` and `sha256`
- arguments will be ignored and the resulting derivation will have
- `__impure` set to `true`, making it an impure derivation.
-
-* If `builtins.readFile` is called on a file with context, then only
- the parts of the context that appear in the content of the file are
- retained. This avoids a lot of spurious errors where strings end up
- having a context just because they are read from a store path
- ([#7260](https://github.com/NixOS/nix/pull/7260)).
-
-* `nix build --json` now prints some statistics about top-level
- derivations, such as CPU statistics when cgroups are enabled.
diff --git a/doc/manual/src/release-notes/rl-2.13.md b/doc/manual/src/release-notes/rl-2.13.md
deleted file mode 100644
index 168708113..000000000
--- a/doc/manual/src/release-notes/rl-2.13.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# Release 2.13 (2023-01-17)
-
-* The `repeat` and `enforce-determinism` options have been removed
- since they had been broken under many circumstances for a long time.
-
-* You can now use [flake references] in the [old command line interface], e.g.
-
- [flake references]: ../command-ref/new-cli/nix3-flake.md#flake-references
- [old command line interface]: ../command-ref/main-commands.md
-
- ```shell-session
- # nix-build flake:nixpkgs -A hello
- # nix-build -I nixpkgs=flake:github:NixOS/nixpkgs/nixos-22.05 \
- '' -A hello
- # NIX_PATH=nixpkgs=flake:nixpkgs nix-build '' -A hello
- ```
-
-* Instead of "antiquotation", the more common term [string interpolation](../language/string-interpolation.md) is now used consistently.
- Historical release notes were not changed.
-
-* Error traces have been reworked to provide detailed explanations and more
- accurate error locations. A short excerpt of the trace is now shown by
- default when an error occurs.
-
-* Allow explicitly selecting outputs in a store derivation installable, just like we can do with other sorts of installables.
- For example,
- ```shell-session
- # nix build /nix/store/gzaflydcr6sb3567hap9q6srzx8ggdgg-glibc-2.33-78.drv^dev
- ```
- now works just as
- ```shell-session
- # nix build nixpkgs#glibc^dev
- ```
- does already.
-
-* On Linux, `nix develop` now sets the
- [*personality*](https://man7.org/linux/man-pages/man2/personality.2.html)
- for the development shell in the same way as the actual build of the
- derivation. This makes shells for `i686-linux` derivations work
- correctly on `x86_64-linux`.
-
-* You can now disable the global flake registry by setting the `flake-registry`
- configuration option to an empty string. The same can be achieved at runtime with
- `--flake-registry ""`.
diff --git a/doc/manual/src/release-notes/rl-2.14.md b/doc/manual/src/release-notes/rl-2.14.md
deleted file mode 100644
index 705c118bb..000000000
--- a/doc/manual/src/release-notes/rl-2.14.md
+++ /dev/null
@@ -1,22 +0,0 @@
-# Release 2.14 (2023-02-28)
-
-* A new function `builtins.readFileType` is available. It is similar to
- `builtins.readDir` but acts on a single file or directory.
-
-* In flakes, the `.outPath` attribute of a flake now always refers to
- the directory containing the `flake.nix`. This was not the case for
- when `flake.nix` was in a subdirectory of e.g. a Git repository.
- The root of the source of a flake in a subdirectory is still
- available in `.sourceInfo.outPath`.
-
-* In derivations that use structured attributes, you can now use `unsafeDiscardReferences`
- to disable scanning a given output for runtime dependencies:
- ```nix
- __structuredAttrs = true;
- unsafeDiscardReferences.out = true;
- ```
- This is useful e.g. when generating self-contained filesystem images with
- their own embedded Nix store: hashes found inside such an image refer
- to the embedded store and not to the host's Nix store.
-
- This requires the `discard-references` experimental feature.
diff --git a/doc/manual/src/release-notes/rl-2.15.md b/doc/manual/src/release-notes/rl-2.15.md
deleted file mode 100644
index 133121999..000000000
--- a/doc/manual/src/release-notes/rl-2.15.md
+++ /dev/null
@@ -1,58 +0,0 @@
-# Release 2.15 (2023-04-11)
-
-* Commands which take installables on the command line can now read them from the standard input if
- passed the `--stdin` flag. This is primarily useful when you have a large amount of paths which
- exceed the OS argument limit.
-
-* The `nix-hash` command now supports Base64 and SRI. Use the flags `--base64`
- or `--sri` to specify the format of output hash as Base64 or SRI, and `--to-base64`
- or `--to-sri` to convert a hash to Base64 or SRI format, respectively.
-
- As the choice of hash formats is no longer binary, the `--base16` flag is also added
- to explicitly specify the Base16 format, which is still the default.
-
-* The special handling of an [installable](../command-ref/new-cli/nix.md#installables) with `.drv` suffix being interpreted as all of the given [store derivation](../glossary.md#gloss-store-derivation)'s output paths is removed, and instead taken as the literal store path that it represents.
-
- The new `^` syntax for store paths introduced in Nix 2.13 allows explicitly referencing output paths of a derivation.
- Using this is better and more clear than relying on the now-removed `.drv` special handling.
-
- For example,
- ```shell-session
- $ nix path-info /nix/store/gzaflydcr6sb3567hap9q6srzx8ggdgg-glibc-2.33-78.drv
- ```
-
- now gives info about the derivation itself, while
-
- ```shell-session
- $ nix path-info /nix/store/gzaflydcr6sb3567hap9q6srzx8ggdgg-glibc-2.33-78.drv^*
- ```
- provides information about each of its outputs.
-
-* The experimental command `nix describe-stores` has been removed.
-
-* Nix stores and their settings are now documented in [`nix help-stores`](@docroot@/command-ref/new-cli/nix3-help-stores.md).
-
-* Documentation for operations of `nix-store` and `nix-env` are now available on separate pages of the manual.
- They include all common options that can be specified and common environment variables that affect these commands.
-
- These pages can be viewed offline with `man` using
-
- * `man nix-store-` and `man nix-env-`
- * `nix-store --help --` and `nix-env --help --`.
-
-* Nix when used as a client now checks whether the store (the server) trusts the client.
- (The store always had to check whether it trusts the client, but now the client is informed of the store's decision.)
- This is useful for scripting interactions with (non-legacy-ssh) remote Nix stores.
-
- `nix store ping` and `nix doctor` now display this information.
-
-* The new command `nix derivation add` allows adding derivations to the store without involving the Nix language.
- It exists to round out our collection of basic utility/plumbing commands, and allow for a low barrier-to-entry way of experimenting with alternative front-ends to the Nix Store.
- It uses the same JSON layout as `nix derivation show`, and is its inverse.
-
-* `nix show-derivation` has been renamed to `nix derivation show`.
- This matches `nix derivation add`, and avoids bloating the top-level namespace.
- The old name is still kept as an alias for compatibility, however.
-
-* The `nix derivation {add,show}` JSON format now includes the derivation name as a top-level field.
- This is useful in general, but especially necessary for the `add` direction, as otherwise we would need to pass in the name out of band for certain cases.
diff --git a/doc/manual/src/release-notes/rl-2.16.md b/doc/manual/src/release-notes/rl-2.16.md
deleted file mode 100644
index 97b40d0b8..000000000
--- a/doc/manual/src/release-notes/rl-2.16.md
+++ /dev/null
@@ -1,8 +0,0 @@
-# Release 2.16 (2023-05-31)
-
-* Speed-up of downloads from binary caches.
- The number of parallel downloads (also known as substitutions) has been separated from the [`--max-jobs` setting](../command-ref/conf-file.md#conf-max-jobs).
- The new setting is called [`max-substitution-jobs`](../command-ref/conf-file.md#conf-max-substitution-jobs).
- The number of parallel downloads is now set to 16 by default (previously, the default was 1 due to the coupling to build jobs).
-
-* The function [`builtins.replaceStrings`](@docroot@/language/builtins.md#builtins-replaceStrings) is now lazy in the value of its second argument `to`. That is, `to` is only evaluated when its corresponding pattern in `from` is matched in the string `s`.
diff --git a/doc/manual/src/release-notes/rl-2.17.md b/doc/manual/src/release-notes/rl-2.17.md
deleted file mode 100644
index 0b861aecc..000000000
--- a/doc/manual/src/release-notes/rl-2.17.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Release 2.17 (2023-07-24)
-
-* [`nix-channel`](../command-ref/nix-channel.md) now supports a `--list-generations` subcommand.
-
-* The function [`builtins.fetchClosure`](../language/builtins.md#builtins-fetchClosure) can now fetch input-addressed paths in [pure evaluation mode](../command-ref/conf-file.md#conf-pure-eval), as those are not impure.
-
-* Nix now allows unprivileged/[`allowed-users`](../command-ref/conf-file.md#conf-allowed-users) to sign paths.
- Previously, only [`trusted-users`](../command-ref/conf-file.md#conf-trusted-users) users could sign paths.
-
-* Nested dynamic attributes are now merged correctly by the parser. For example:
-
- ```nix
- {
- nested = {
- foo = 1;
- };
- nested = {
- ${"ba" + "r"} = 2;
- };
- }
- ```
-
- This used to silently discard `nested.bar`, but now behaves as one would expect and evaluates to:
-
- ```nix
- { nested = { bar = 2; foo = 1; }; }
- ```
-
- Note that the feature of merging multiple *full declarations* of attribute sets like `nested` in the example is of questionable value.
- It allows writing expressions that are very hard to read, for instance when there are many lines of code between two declarations of the same attribute.
- This has been around for a long time and is therefore supported for backwards compatibility, but should not be relied upon.
-
- Instead, consider using the *nested attribute path* syntax:
-
- ```nix
- {
- nested.foo = 1;
- nested.${"ba" + "r"} = 2;
- }
- ```
-
-* Tarball flakes can now redirect to an "immutable" URL that will be recorded in lock files. This allows the use of "mutable" tarball URLs like `https://example.org/hello/latest.tar.gz` in flakes. See the [tarball fetcher](../protocols/tarball-fetcher.md) for details.
diff --git a/doc/manual/src/release-notes/rl-2.18.md b/doc/manual/src/release-notes/rl-2.18.md
deleted file mode 100644
index 4bbc52b50..000000000
--- a/doc/manual/src/release-notes/rl-2.18.md
+++ /dev/null
@@ -1,28 +0,0 @@
-# Release 2.18 (2023-09-20)
-
-- Two new builtin functions,
- [`builtins.parseFlakeRef`](@docroot@/language/builtins.md#builtins-parseFlakeRef)
- and
- [`builtins.flakeRefToString`](@docroot@/language/builtins.md#builtins-flakeRefToString),
- have been added.
- These functions are useful for converting between flake references encoded as attribute sets and URLs.
-
-- [`builtins.toJSON`](@docroot@/language/builtins.md#builtins-parseFlakeRef) now prints [--show-trace](@docroot@/command-ref/conf-file.html#conf-show-trace) items for the path in which it finds an evaluation error.
-
-- Error messages regarding malformed input to [`nix derivation add`](@docroot@/command-ref/new-cli/nix3-derivation-add.md) are now clearer and more detailed.
-
-- The `discard-references` feature has been stabilized.
- This means that the
- [unsafeDiscardReferences](@docroot@/contributing/experimental-features.md#xp-feature-discard-references)
- attribute is no longer guarded by an experimental flag and can be used
- freely.
-
-- The JSON output for derived paths which are store paths is now a string, not an object with a single `path` field.
- This only affects `nix-build --json` when "building" non-derivation things like fetched sources, which is a no-op.
-
-- A new builtin [`outputOf`](@docroot@/language/builtins.md#builtins-outputOf) has been added.
- It is part of the [`dynamic-derivations`](@docroot@/contributing/experimental-features.md#xp-feature-dynamic-derivations) experimental feature.
-
-- Flake follow paths at depths greater than 2 are now handled correctly, preventing "follows a non-existent input" errors.
-
-- [`nix-store --query`](@docroot@/command-ref/nix-store/query.md) gained a new type of query: `--valid-derivers`. It returns all `.drv` files in the local store that *can be* used to build the output passed in argument. This is in contrast to `--deriver`, which returns the single `.drv` file that *was actually* used to build the output passed in argument. In case the output was substituted from a binary cache, this `.drv` file may only exist on said binary cache and not locally.
diff --git a/doc/manual/src/release-notes/rl-2.2.md b/doc/manual/src/release-notes/rl-2.2.md
deleted file mode 100644
index fa9af920d..000000000
--- a/doc/manual/src/release-notes/rl-2.2.md
+++ /dev/null
@@ -1,82 +0,0 @@
-# Release 2.2 (2019-01-11)
-
-This is primarily a bug fix release. It also has the following changes:
-
- - In derivations that use structured attributes (i.e. that specify set
- the `__structuredAttrs` attribute to `true` to cause all attributes
- to be passed to the builder in JSON format), you can now specify
- closure checks per output, e.g.:
-
- outputChecks."out" = {
- # The closure of 'out' must not be larger than 256 MiB.
- maxClosureSize = 256 * 1024 * 1024;
-
- # It must not refer to C compiler or to the 'dev' output.
- disallowedRequisites = [ stdenv.cc "dev" ];
- };
-
- outputChecks."dev" = {
- # The 'dev' output must not be larger than 128 KiB.
- maxSize = 128 * 1024;
- };
-
- - The derivation attribute `requiredSystemFeatures` is now enforced
- for local builds, and not just to route builds to remote builders.
- The supported features of a machine can be specified through the
- configuration setting `system-features`.
-
- By default, `system-features` includes `kvm` if `/dev/kvm` exists.
- For compatibility, it also includes the pseudo-features
- `nixos-test`, `benchmark` and `big-parallel` which are used by
- Nixpkgs to route builds to particular Hydra build machines.
-
- - Sandbox builds are now enabled by default on Linux.
-
- - The new command `nix doctor` shows potential issues with your Nix
- installation.
-
- - The `fetchGit` builtin function now uses a caching scheme that puts
- different remote repositories in distinct local repositories, rather
- than a single shared repository. This may require more disk space
- but is faster.
-
- - The `dirOf` builtin function now works on relative paths.
-
- - Nix now supports [SRI hashes](https://www.w3.org/TR/SRI/), allowing
- the hash algorithm and hash to be specified in a single string. For
- example, you can write:
-
- import {
- url = https://nixos.org/releases/nix/nix-2.1.3/nix-2.1.3.tar.xz;
- hash = "sha256-XSLa0FjVyADWWhFfkZ2iKTjFDda6mMXjoYMXLRSYQKQ=";
- };
-
- instead of
-
- import {
- url = https://nixos.org/releases/nix/nix-2.1.3/nix-2.1.3.tar.xz;
- sha256 = "5d22dad058d5c800d65a115f919da22938c50dd6ba98c5e3a183172d149840a4";
- };
-
- In fixed-output derivations, the `outputHashAlgo` attribute is no
- longer mandatory if `outputHash` specifies the hash.
-
- `nix hash-file` and `nix
- hash-path` now print hashes in SRI format by default. They also use
- SHA-256 by default instead of SHA-512 because that's what we use
- most of the time in Nixpkgs.
-
- - Integers are now 64 bits on all platforms.
-
- - The evaluator now prints profiling statistics (enabled via the
- `NIX_SHOW_STATS` and `NIX_COUNT_CALLS` environment variables) in
- JSON format.
-
- - The option `--xml` in `nix-store
- --query` has been removed. Instead, there now is an option
- `--graphml` to output the dependency graph in GraphML format.
-
- - All `nix-*` commands are now symlinks to `nix`. This saves a bit of
- disk space.
-
- - `nix repl` now uses `libeditline` or `libreadline`.
diff --git a/doc/manual/src/release-notes/rl-2.3.md b/doc/manual/src/release-notes/rl-2.3.md
deleted file mode 100644
index d1f4e3734..000000000
--- a/doc/manual/src/release-notes/rl-2.3.md
+++ /dev/null
@@ -1,44 +0,0 @@
-# Release 2.3 (2019-09-04)
-
-This is primarily a bug fix release. However, it makes some incompatible
-changes:
-
- - Nix now uses BSD file locks instead of POSIX file locks. Because of
- this, you should not use Nix 2.3 and previous releases at the same
- time on a Nix store.
-
-It also has the following changes:
-
- - `builtins.fetchGit`'s `ref` argument now allows specifying an
- absolute remote ref. Nix will automatically prefix `ref` with
- `refs/heads` only if `ref` doesn't already begin with `refs/`.
-
- - The installer now enables sandboxing by default on Linux when the
- system has the necessary kernel support.
-
- - The `max-jobs` setting now defaults to 1.
-
- - New builtin functions: `builtins.isPath`, `builtins.hashFile`.
-
- - The `nix` command has a new `--print-build-logs` (`-L`) flag to
- print build log output to stderr, rather than showing the last log
- line in the progress bar. To distinguish between concurrent builds,
- log lines are prefixed by the name of the package.
-
- - Builds are now executed in a pseudo-terminal, and the `TERM`
- environment variable is set to `xterm-256color`. This allows many
- programs (e.g. `gcc`, `clang`, `cmake`) to print colorized log
- output.
-
- - Add `--no-net` convenience flag. This flag disables substituters;
- sets the `tarball-ttl` setting to infinity (ensuring that any
- previously downloaded files are considered current); and disables
- retrying downloads and sets the connection timeout to the minimum.
- This flag is enabled automatically if there are no configured
- non-loopback network interfaces.
-
- - Add a `post-build-hook` setting to run a program after a build has
- succeeded.
-
- - Add a `trace-function-calls` setting to log the duration of Nix
- function calls to stderr.
diff --git a/doc/manual/src/release-notes/rl-2.4.md b/doc/manual/src/release-notes/rl-2.4.md
deleted file mode 100644
index 8b566fc7b..000000000
--- a/doc/manual/src/release-notes/rl-2.4.md
+++ /dev/null
@@ -1,542 +0,0 @@
-# Release 2.4 (2021-11-01)
-
-This is the first release in more than two years and is the result of
-more than 2800 commits from 195 contributors since release 2.3.
-
-## Highlights
-
-* Nix's **error messages** have been improved a lot. For instance,
- evaluation errors now point out the location of the error:
-
- ```
- $ nix build
- error: undefined variable 'bzip3'
-
- at /nix/store/449lv242z0zsgwv95a8124xi11sp419f-source/flake.nix:88:13:
-
- 87| [ curl
- 88| bzip3 xz brotli editline
- | ^
- 89| openssl sqlite
- ```
-
-* The **`nix` command** has seen a lot of work and is now almost at
- feature parity with the old command-line interface (the `nix-*`
- commands). It aims to be [more modern, consistent and pleasant to
- use](../contributing/cli-guideline.md) than the old CLI. It is still
- marked as experimental but its interface should not change much
- anymore in future releases.
-
-* **Flakes** are a new format to package Nix-based projects in a more
- discoverable, composable, consistent and reproducible way. A flake
- is just a repository or tarball containing a file named `flake.nix`
- that specifies dependencies on other flakes and returns any Nix
- assets such as packages, Nixpkgs overlays, NixOS modules or CI
- tests. The new `nix` CLI is primarily based around flakes; for
- example, a command like `nix run nixpkgs#hello` runs the `hello`
- application from the `nixpkgs` flake.
-
- Flakes are currently marked as experimental. For an introduction,
- see [this blog
- post](https://www.tweag.io/blog/2020-05-25-flakes/). For detailed
- information about flake syntax and semantics, see the [`nix flake`
- manual page](../command-ref/new-cli/nix3-flake.md).
-
-* Nix's store can now be **content-addressed**, meaning that the hash
- component of a store path is the hash of the path's
- contents. Previously Nix could only build **input-addressed** store
- paths, where the hash is computed from the derivation dependency
- graph. Content-addressing allows deduplication, early cutoff in
- build systems, and unprivileged closure copying. This is still [an
- experimental
- feature](https://discourse.nixos.org/t/content-addressed-nix-call-for-testers/12881).
-
-* The Nix manual has been converted into Markdown, making it easier to
- contribute. In addition, every `nix` subcommand now has a manual
- page, documenting every option.
-
-* A new setting that allows **experimental features** to be enabled
- selectively. This allows us to merge unstable features into Nix more
- quickly and do more frequent releases.
-
-## Other features
-
-* There are many new `nix` subcommands:
-
- - `nix develop` is intended to replace `nix-shell`. It has a number
- of new features:
-
- * It automatically sets the output environment variables (such as
- `$out`) to writable locations (such as `./outputs/out`).
-
- * It can store the environment in a profile. This is useful for
- offline work.
-
- * It can run specific phases directly. For instance, `nix develop
- --build` runs `buildPhase`.
-
- - It allows dependencies in the Nix store to be "redirected" to
- arbitrary directories using the `--redirect` flag. This is
- useful if you want to hack on a package *and* some of its
- dependencies at the same time.
-
- - `nix print-dev-env` prints the environment variables and bash
- functions defined by a derivation. This is useful for users of
- other shells than bash (especially with `--json`).
-
- - `nix shell` was previously named `nix run` and is intended to
- replace `nix-shell -p`, but without the `stdenv` overhead. It
- simply starts a shell where some packages have been added to
- `$PATH`.
-
- - `nix run` (not to be confused with the old subcommand that has
- been renamed to `nix shell`) runs an "app", a flake output that
- specifies a command to run, or an eponymous program from a
- package. For example, `nix run nixpkgs#hello` runs the `hello`
- program from the `hello` package in `nixpkgs`.
-
- - `nix flake` is the container for flake-related operations, such as
- creating a new flake, querying the contents of a flake or updating
- flake lock files.
-
- - `nix registry` allows you to query and update the flake registry,
- which maps identifiers such as `nixpkgs` to concrete flake URLs.
-
- - `nix profile` is intended to replace `nix-env`. Its main advantage
- is that it keeps track of the provenance of installed packages
- (e.g. exactly which flake version a package came from). It also
- has some helpful subcommands:
-
- * `nix profile history` shows what packages were added, upgraded
- or removed between each version of a profile.
-
- * `nix profile diff-closures` shows the changes between the
- closures of each version of a profile. This allows you to
- discover the addition or removal of dependencies or size
- changes.
-
- **Warning**: after a profile has been updated using `nix profile`,
- it is no longer usable with `nix-env`.
-
- - `nix store diff-closures` shows the differences between the
- closures of two store paths in terms of the versions and sizes of
- dependencies in the closures.
-
- - `nix store make-content-addressable` rewrites an arbitrary closure
- to make it content-addressed. Such paths can be copied into other
- stores without requiring signatures.
-
- - `nix bundle` uses the [`nix-bundle`
- program](https://github.com/matthewbauer/nix-bundle) to convert a
- closure into a self-extracting executable.
-
- - Various other replacements for the old CLI, e.g. `nix store gc`,
- `nix store delete`, `nix store repair`, `nix nar dump-path`, `nix
- store prefetch-file`, `nix store prefetch-tarball`, `nix key` and
- `nix daemon`.
-
-* Nix now has an **evaluation cache** for flake outputs. For example,
- a second invocation of the command `nix run nixpkgs#firefox` will
- not need to evaluate the `firefox` attribute because it's already in
- the evaluation cache. This is made possible by the hermetic
- evaluation model of flakes.
-
-* The new `--offline` flag disables substituters and causes all
- locally cached tarballs and repositories to be considered
- up-to-date.
-
-* The new `--refresh` flag causes all locally cached tarballs and
- repositories to be considered out-of-date.
-
-* Many `nix` subcommands now have a `--json` option to produce
- machine-readable output.
-
-* `nix repl` has a new `:doc` command to show documentation about
- builtin functions (e.g. `:doc builtins.map`).
-
-* Binary cache stores now have an option `index-debug-info` to create
- an index of DWARF debuginfo files for use by
- [`dwarffs`](https://github.com/edolstra/dwarffs).
-
-* To support flakes, Nix now has an extensible mechanism for fetching
- source trees. Currently it has the following backends:
-
- * Git repositories
-
- * Mercurial repositories
-
- * GitHub and GitLab repositories (an optimisation for faster
- fetching than Git)
-
- * Tarballs
-
- * Arbitrary directories
-
- The fetcher infrastructure is exposed via flake input specifications
- and via the `fetchTree` built-in.
-
-* **Languages changes**: the only new language feature is that you can
- now have antiquotations in paths, e.g. `./${foo}` instead of `./. +
- foo`.
-
-* **New built-in functions**:
-
- - `builtins.fetchTree` allows fetching a source tree using any
- backends supported by the fetcher infrastructure. It subsumes the
- functionality of existing built-ins like `fetchGit`,
- `fetchMercurial` and `fetchTarball`.
-
- - `builtins.getFlake` fetches a flake and returns its output
- attributes. This function should not be used inside flakes! Use
- flake inputs instead.
-
- - `builtins.floor` and `builtins.ceil` round a floating-point number
- down and up, respectively.
-
-* Experimental support for recursive Nix. This means that Nix
- derivations can now call Nix to build other derivations. This is not
- in a stable state yet and not well
- [documented](https://github.com/NixOS/nix/commit/c4d7c76b641d82b2696fef73ce0ac160043c18da).
-
-* The new experimental feature `no-url-literals` disables URL
- literals. This helps to implement [RFC
- 45](https://github.com/NixOS/rfcs/pull/45).
-
-* Nix now uses `libarchive` to decompress and unpack tarballs and zip
- files, so `tar` is no longer required.
-
-* The priority of substituters can now be overridden using the
- `priority` substituter setting (e.g. `--substituters
- 'http://cache.nixos.org?priority=100 daemon?priority=10'`).
-
-* `nix edit` now supports non-derivation attributes, e.g. `nix edit
- .#nixosConfigurations.bla`.
-
-* The `nix` command now provides command line completion for `bash`,
- `zsh` and `fish`. Since the support for getting completions is built
- into `nix`, it's easy to add support for other shells.
-
-* The new `--log-format` flag selects what Nix's output looks like. It
- defaults to a terse progress indicator. There is a new
- `internal-json` output format for use by other programs.
-
-* `nix eval` has a new `--apply` flag that applies a function to the
- evaluation result.
-
-* `nix eval` has a new `--write-to` flag that allows it to write a
- nested attribute set of string leaves to a corresponding directory
- tree.
-
-* Memory improvements: many operations that add paths to the store or
- copy paths between stores now run in constant memory.
-
-* Many `nix` commands now support the flag `--derivation` to operate
- on a `.drv` file itself instead of its outputs.
-
-* There is a new store called `dummy://` that does not support
- building or adding paths. This is useful if you want to use the Nix
- evaluator but don't have a Nix store.
-
-* The `ssh-ng://` store now allows substituting paths on the remote,
- as `ssh://` already did.
-
-* When auto-calling a function with an ellipsis, all arguments are now
- passed.
-
-* New `nix-shell` features:
-
- - It preserves the `PS1` environment variable if
- `NIX_SHELL_PRESERVE_PROMPT` is set.
-
- - With `-p`, it passes any `--arg`s as Nixpkgs arguments.
-
- - Support for structured attributes.
-
-* `nix-prefetch-url` has a new `--executable` flag.
-
-* On `x86_64` systems, [`x86_64` microarchitecture
- levels](https://lwn.net/Articles/844831/) are mapped to additional
- system types (e.g. `x86_64-v1-linux`).
-
-* The new `--eval-store` flag allows you to use a different store for
- evaluation than for building or storing the build result. This is
- primarily useful when you want to query whether something exists in
- a read-only store, such as a binary cache:
-
- ```
- # nix path-info --json --store https://cache.nixos.org \
- --eval-store auto nixpkgs#hello
- ```
-
- (Here `auto` indicates the local store.)
-
-* The Nix daemon has a new low-latency mechanism for copying
- closures. This is useful when building on remote stores such as
- `ssh-ng://`.
-
-* Plugins can now register `nix` subcommands.
-
-* The `--indirect` flag to `nix-store --add-root` has become a no-op.
- `--add-root` will always generate indirect GC roots from now on.
-
-## Incompatible changes
-
-* The `nix` command is now marked as an experimental feature. This
- means that you need to add
-
- ```
- experimental-features = nix-command
- ```
-
- to your `nix.conf` if you want to use it, or pass
- `--extra-experimental-features nix-command` on the command line.
-
-* The `nix` command no longer has a syntax for referring to packages
- in a channel. This means that the following no longer works:
-
- ```console
- nix build nixpkgs.hello # Nix 2.3
- ```
-
- Instead, you can either use the `#` syntax to select a package from
- a flake, e.g.
-
- ```console
- nix build nixpkgs#hello
- ```
-
- Or, if you want to use the `nixpkgs` channel in the `NIX_PATH`
- environment variable:
-
- ```console
- nix build -f '' hello
- ```
-
-* The old `nix run` has been renamed to `nix shell`, while there is a
- new `nix run` that runs a default command. So instead of
-
- ```console
- nix run nixpkgs.hello -c hello # Nix 2.3
- ```
-
- you should use
-
- ```console
- nix shell nixpkgs#hello -c hello
- ```
-
- or just
-
- ```console
- nix run nixpkgs#hello
- ```
-
- if the command you want to run has the same name as the package.
-
-* It is now an error to modify the `plugin-files` setting via a
- command-line flag that appears after the first non-flag argument to
- any command, including a subcommand to `nix`. For example,
- `nix-instantiate default.nix --plugin-files ""` must now become
- `nix-instantiate --plugin-files "" default.nix`.
-
-* We no longer release source tarballs. If you want to build from
- source, please build from the tags in the Git repository.
-
-## Contributors
-
-This release has contributions from
-Adam Höse,
-Albert Safin,
-Alex Kovar,
-Alex Zero,
-Alexander Bantyev,
-Alexandre Esteves,
-Alyssa Ross,
-Anatole Lucet,
-Anders Kaseorg,
-Andreas Rammhold,
-Antoine Eiche,
-Antoine Martin,
-Arnout Engelen,
-Arthur Gautier,
-aszlig,
-Ben Burdette,
-Benjamin Hipple,
-Bernardo Meurer,
-Björn Gohla,
-Bjørn Forsman,
-Bob van der Linden,
-Brian Leung,
-Brian McKenna,
-Brian Wignall,
-Bruce Toll,
-Bryan Richter,
-Calle Rosenquist,
-Calvin Loncaric,
-Carlo Nucera,
-Carlos D'Agostino,
-Chaz Schlarp,
-Christian Höppner,
-Christian Kampka,
-Chua Hou,
-Chuck,
-Cole Helbling,
-Daiderd Jordan,
-Dan Callahan,
-Dani,
-Daniel Fitzpatrick,
-Danila Fedorin,
-Daniël de Kok,
-Danny Bautista,
-DavHau,
-David McFarland,
-Dima,
-Domen Kožar,
-Dominik Schrempf,
-Dominique Martinet,
-dramforever,
-Dustin DeWeese,
-edef,
-Eelco Dolstra,
-Ellie Hermaszewska,
-Emilio Karakey,
-Emily,
-Eric Culp,
-Ersin Akinci,
-Fabian Möller,
-Farid Zakaria,
-Federico Pellegrin,
-Finn Behrens,
-Florian Franzen,
-Félix Baylac-Jacqué,
-Gabriella Gonzalez,
-Geoff Reedy,
-Georges Dubus,
-Graham Christensen,
-Greg Hale,
-Greg Price,
-Gregor Kleen,
-Gregory Hale,
-Griffin Smith,
-Guillaume Bouchard,
-Harald van Dijk,
-illustris,
-Ivan Zvonimir Horvat,
-Jade,
-Jake Waksbaum,
-jakobrs,
-James Ottaway,
-Jan Tojnar,
-Janne Heß,
-Jaroslavas Pocepko,
-Jarrett Keifer,
-Jeremy Schlatter,
-Joachim Breitner,
-Joe Pea,
-John Ericson,
-Jonathan Ringer,
-Josef Kemetmüller,
-Joseph Lucas,
-Jude Taylor,
-Julian Stecklina,
-Julien Tanguy,
-Jörg Thalheim,
-Kai Wohlfahrt,
-keke,
-Keshav Kini,
-Kevin Quick,
-Kevin Stock,
-Kjetil Orbekk,
-Krzysztof Gogolewski,
-kvtb,
-Lars Mühmel,
-Leonhard Markert,
-Lily Ballard,
-Linus Heckemann,
-Lorenzo Manacorda,
-Lucas Desgouilles,
-Lucas Franceschino,
-Lucas Hoffmann,
-Luke Granger-Brown,
-Madeline Haraj,
-Marwan Aljubeh,
-Mat Marini,
-Mateusz Piotrowski,
-Matthew Bauer,
-Matthew Kenigsberg,
-Mauricio Scheffer,
-Maximilian Bosch,
-Michael Adler,
-Michael Bishop,
-Michael Fellinger,
-Michael Forney,
-Michael Reilly,
-mlatus,
-Mykola Orliuk,
-Nathan van Doorn,
-Naïm Favier,
-ng0,
-Nick Van den Broeck,
-Nicolas Stig124 Formichella,
-Niels Egberts,
-Niklas Hambüchen,
-Nikola Knezevic,
-oxalica,
-p01arst0rm,
-Pamplemousse,
-Patrick Hilhorst,
-Paul Opiyo,
-Pavol Rusnak,
-Peter Kolloch,
-Philipp Bartsch,
-Philipp Middendorf,
-Piotr Szubiakowski,
-Profpatsch,
-Puck Meerburg,
-Ricardo M. Correia,
-Rickard Nilsson,
-Robert Hensing,
-Robin Gloster,
-Rodrigo,
-Rok Garbas,
-Ronnie Ebrin,
-Rovanion Luckey,
-Ryan Burns,
-Ryan Mulligan,
-Ryne Everett,
-Sam Doshi,
-Sam Lidder,
-Samir Talwar,
-Samuel Dionne-Riel,
-Sebastian Ullrich,
-Sergei Trofimovich,
-Sevan Janiyan,
-Shao Cheng,
-Shea Levy,
-Silvan Mosberger,
-Stefan Frijters,
-Stefan Jaax,
-sternenseemann,
-Steven Shaw,
-Stéphan Kochen,
-SuperSandro2000,
-Suraj Barkale,
-Taeer Bar-Yam,
-Thomas Churchman,
-Théophane Hufschmitt,
-Timothy DeHerrera,
-Timothy Klim,
-Tobias Möst,
-Tobias Pflug,
-Tom Bereknyei,
-Travis A. Everett,
-Ujjwal Jain,
-Vladimír Čunát,
-Wil Taylor,
-Will Dietz,
-Yaroslav Bolyukin,
-Yestin L. Harrison,
-YI,
-Yorick van Pelt,
-Yuriy Taraday and
-zimbatm.
diff --git a/doc/manual/src/release-notes/rl-2.5.md b/doc/manual/src/release-notes/rl-2.5.md
deleted file mode 100644
index dd6fd3b0f..000000000
--- a/doc/manual/src/release-notes/rl-2.5.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# Release 2.5 (2021-12-13)
-
-* The garbage collector no longer blocks new builds, so the message
- `waiting for the big garbage collector lock...` is a thing of the
- past.
-
-* Binary cache stores now have a setting `compression-level`.
-
-* `nix develop` now has a flag `--unpack` to run `unpackPhase`.
-
-* Lists can now be compared lexicographically using the `<` operator.
-
-* New built-in function: `builtins.groupBy`, with the same functionality as
- Nixpkgs' `lib.groupBy`, but faster.
-
-* `nix repl` now has a `:log` command.
diff --git a/doc/manual/src/release-notes/rl-2.6.md b/doc/manual/src/release-notes/rl-2.6.md
deleted file mode 100644
index 280faead1..000000000
--- a/doc/manual/src/release-notes/rl-2.6.md
+++ /dev/null
@@ -1,21 +0,0 @@
-# Release 2.6 (2022-01-24)
-
-* The Nix CLI now searches for a `flake.nix` up until the root of the current
- Git repository or a filesystem boundary rather than just in the current
- directory.
-* The TOML parser used by `builtins.fromTOML` has been replaced by [a
- more compliant one](https://github.com/ToruNiina/toml11).
-* Added `:st`/`:show-trace` commands to `nix repl`, which are used to
- set or toggle display of error traces.
-* New builtin function `builtins.zipAttrsWith` with the same
- functionality as `lib.zipAttrsWith` from Nixpkgs, but much more
- efficient.
-* New command `nix store copy-log` to copy build logs from one store
- to another.
-* The `commit-lockfile-summary` option can be set to a non-empty
- string to override the commit summary used when commiting an updated
- lockfile. This may be used in conjunction with the `nixConfig`
- attribute in `flake.nix` to better conform to repository
- conventions.
-* `docker run -ti nixos/nix:master` will place you in the Docker
- container with the latest version of Nix from the `master` branch.
diff --git a/doc/manual/src/release-notes/rl-2.7.md b/doc/manual/src/release-notes/rl-2.7.md
deleted file mode 100644
index 2f3879422..000000000
--- a/doc/manual/src/release-notes/rl-2.7.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Release 2.7 (2022-03-07)
-
-* Nix will now make some helpful suggestions when you mistype
- something on the command line. For instance, if you type `nix build
- nixpkgs#thunderbrd`, it will suggest `thunderbird`.
-
-* A number of "default" flake output attributes have been
- renamed. These are:
-
- * `defaultPackage.` → `packages..default`
- * `defaultApps.` → `apps..default`
- * `defaultTemplate` → `templates.default`
- * `defaultBundler.` → `bundlers..default`
- * `overlay` → `overlays.default`
- * `devShell.` → `devShells..default`
-
- The old flake output attributes still work, but `nix flake check`
- will warn about them.
-
-* Breaking API change: `nix bundle` now supports bundlers of the form
- `bundler..= derivation: another-derivation;`. This
- supports additional functionality to inspect evaluation information
- during bundling. A new
- [repository](https://github.com/NixOS/bundlers) has various bundlers
- implemented.
-
-* `nix store ping` now reports the version of the remote Nix daemon.
-
-* `nix flake {init,new}` now display information about which files have been
- created.
-
-* Templates can now define a `welcomeText` attribute, which is printed out by
- `nix flake {init,new} --template `.
diff --git a/doc/manual/src/release-notes/rl-2.8.md b/doc/manual/src/release-notes/rl-2.8.md
deleted file mode 100644
index 9778e8c3a..000000000
--- a/doc/manual/src/release-notes/rl-2.8.md
+++ /dev/null
@@ -1,53 +0,0 @@
-# Release 2.8 (2022-04-19)
-
-* New experimental command: `nix fmt`, which applies a formatter
- defined by the `formatter.` flake output to the Nix
- expressions in a flake.
-
-* Various Nix commands can now read expressions from standard input
- using `--file -`.
-
-* New experimental builtin function `builtins.fetchClosure` that
- copies a closure from a binary cache at evaluation time and rewrites
- it to content-addressed form (if it isn't already). Like
- `builtins.storePath`, this allows importing pre-built store paths;
- the difference is that it doesn't require the user to configure
- binary caches and trusted public keys.
-
- This function is only available if you enable the experimental
- feature `fetch-closure`.
-
-* New experimental feature: *impure derivations*. These are
- derivations that can produce a different result every time they're
- built. Here is an example:
-
- ```nix
- stdenv.mkDerivation {
- name = "impure";
- __impure = true; # marks this derivation as impure
- buildCommand = "date > $out";
- }
- ```
-
- Running `nix build` twice on this expression will build the
- derivation twice, producing two different content-addressed store
- paths. Like fixed-output derivations, impure derivations have access
- to the network. Only fixed-output derivations and impure derivations
- can depend on an impure derivation.
-
-* `nix store make-content-addressable` has been renamed to `nix store
- make-content-addressed`.
-
-* The `nixosModule` flake output attribute has been renamed consistent
- with the `.default` renames in Nix 2.7.
-
- * `nixosModule` → `nixosModules.default`
-
- As before, the old output will continue to work, but `nix flake check` will
- issue a warning about it.
-
-* `nix run` is now stricter in what it accepts: members of the `apps`
- flake output are now required to be apps (as defined in [the
- manual](https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3-run.html#apps)),
- and members of `packages` or `legacyPackages` must be derivations
- (not apps).
diff --git a/doc/manual/src/release-notes/rl-2.9.md b/doc/manual/src/release-notes/rl-2.9.md
deleted file mode 100644
index 98cc4235d..000000000
--- a/doc/manual/src/release-notes/rl-2.9.md
+++ /dev/null
@@ -1,47 +0,0 @@
-# Release 2.9 (2022-05-30)
-
-* Running Nix with the new `--debugger` flag will cause it to start a
- repl session if an exception is thrown during evaluation, or if
- `builtins.break` is called. From there you can inspect the values
- of variables and evaluate Nix expressions. In debug mode, the
- following new repl commands are available:
-
- ```
- :env Show env stack
- :bt Show trace stack
- :st Show current trace
- :st Change to another trace in the stack
- :c Go until end of program, exception, or builtins.break().
- :s Go one step
- ```
-
- Read more about the debugger
- [here](https://www.zknotes.com/note/5970).
-
-* Nix now provides better integration with zsh's `run-help`
- feature. It is now included in the Nix installation in the form of
- an autoloadable shell function, `run-help-nix`. It picks up Nix
- subcommands from the currently typed in command and directs the user
- to the associated man pages.
-
-* `nix repl` has a new build-and-link (`:bl`) command that builds a
- derivation while creating GC root symlinks.
-
-* The path produced by `builtins.toFile` is now allowed to be imported
- or read even with restricted evaluation. Note that this will not
- work with a read-only store.
-
-* `nix build` has a new `--print-out-paths` flag to print the
- resulting output paths. This matches the default behaviour of
- `nix-build`.
-
-* You can now specify which outputs of a derivation `nix` should
- operate on using the syntax `installable^outputs`,
- e.g. `nixpkgs#glibc^dev,static` or `nixpkgs#glibc^*`. By default,
- `nix` will use the outputs specified by the derivation's
- `meta.outputsToInstall` attribute if it exists, or all outputs
- otherwise.
-
-* `builtins.fetchTree` (and flake inputs) can now be used to fetch
- plain files over the `http(s)` and `file` protocols in addition to
- directory tarballs.
diff --git a/doc/manual/src/release-notes/rl-next.md b/doc/manual/src/release-notes/rl-next.md
deleted file mode 100644
index bf4bb194b..000000000
--- a/doc/manual/src/release-notes/rl-next.md
+++ /dev/null
@@ -1,3 +0,0 @@
-# Upcoming release
-
-{{#include @generated@/release-notes/rl-next-generated.md}}
diff --git a/doc/manual/substitute.py b/doc/manual/substitute.py
deleted file mode 100755
index 18b7bed68..000000000
--- a/doc/manual/substitute.py
+++ /dev/null
@@ -1,101 +0,0 @@
-#!/usr/bin/env python3
-
-from pathlib import Path
-import json
-import os, os.path
-import sys
-
-name = 'substitute.py'
-
-def log(*args, **kwargs):
- kwargs['file'] = sys.stderr
- return print(f'{name}:', *args, **kwargs)
-
-def do_include(content: str, relative_md_path: Path, source_root: Path, search_path: Path):
- assert not relative_md_path.is_absolute(), f'{relative_md_path=} from mdbook should be relative'
-
- md_path_abs = source_root / relative_md_path
- var_abs = md_path_abs.parent
- assert var_abs.is_dir(), f'supposed directory {var_abs} is not a directory (cwd={os.getcwd()})'
-
- lines = []
- for l in content.splitlines(keepends=True):
- if l.strip().startswith("{{#include "):
- requested = l.strip()[11:][:-2]
- if requested.startswith("@generated@/"):
- included = search_path / Path(requested[12:])
- requested = included.relative_to(search_path)
- else:
- included = source_root / relative_md_path.parent / requested
- requested = included.resolve().relative_to(source_root)
- assert included.exists(), f"{requested} not found at {included}"
- lines.append(do_include(included.read_text(), requested, source_root, search_path) + "\n")
- else:
- lines.append(l)
- return "".join(lines)
-
-def recursive_replace(data, book_root, search_path):
- match data:
- case {'sections': sections}:
- return data | dict(
- sections = [recursive_replace(section, book_root, search_path) for section in sections],
- )
- case {'Chapter': chapter}:
- path_to_chapter = Path(chapter['path'])
- chapter_content = chapter['content']
-
- return data | dict(
- Chapter = chapter | dict(
- # first process includes. this must happen before docroot processing since
- # mdbook does not see these included files, only the final agglomeration.
- content = do_include(
- chapter_content,
- path_to_chapter,
- book_root,
- search_path
- ).replace(
- '@docroot@',
- ("../" * len(path_to_chapter.parent.parts) or "./")[:-1]
- ),
- sub_items = [
- recursive_replace(sub_item, book_root, search_path)
- for sub_item in chapter['sub_items']
- ],
- ),
- )
-
- case rest:
- assert False, f'should have been called on a dict, not {type(rest)=}\n\t{rest=}'
-
-def main():
-
- if len(sys.argv) > 1 and sys.argv[1] == 'supports':
- return 0
-
- # mdbook communicates with us over stdin and stdout.
- # It splorks us a JSON array, the first element describing the context,
- # the second element describing the book itself,
- # and then expects us to send it the modified book JSON over stdout.
-
- context, book = json.load(sys.stdin)
-
- # book_root is the directory where book contents leave (ie, src/)
- book_root = Path(context['root']) / context['config']['book']['src']
-
- # includes pointing into @generated@ will look here
- search_path = Path(os.environ['MDBOOK_SUBSTITUTE_SEARCH'])
-
- # Find @var@ in all parts of our recursive book structure.
- replaced_content = recursive_replace(book, book_root, search_path)
-
- replaced_content_str = json.dumps(replaced_content)
-
- # Give mdbook our changes.
- print(replaced_content_str)
-
-try:
- sys.exit(main())
-except AssertionError as e:
- print(f'{name}: INTERNAL ERROR in mdbook preprocessor', file=sys.stderr)
- print(f'this is a bug in {name}', file=sys.stderr)
- raise
diff --git a/doc/manual/theme/highlight.js b/doc/manual/theme/highlight.js
deleted file mode 100644
index f4fd4faea..000000000
--- a/doc/manual/theme/highlight.js
+++ /dev/null
@@ -1,6 +0,0 @@
-/*
- Highlight.js 10.1.2 (edd73d24)
- License: BSD-3-Clause
- Copyright (c) 2006-2020, Ivan Sagalaev
-*/
-var hljs=function(){"use strict";function e(n){Object.freeze(n);var t="function"==typeof n;return Object.getOwnPropertyNames(n).forEach((function(r){!Object.hasOwnProperty.call(n,r)||null===n[r]||"object"!=typeof n[r]&&"function"!=typeof n[r]||t&&("caller"===r||"callee"===r||"arguments"===r)||Object.isFrozen(n[r])||e(n[r])})),n}class n{constructor(e){void 0===e.data&&(e.data={}),this.data=e.data}ignoreMatch(){this.ignore=!0}}function t(e){return e.replace(/&/g,"&").replace(//g,">").replace(/"/g,""").replace(/'/g,"'")}function r(e,...n){var t={};for(const n in e)t[n]=e[n];return n.forEach((function(e){for(const n in e)t[n]=e[n]})),t}function a(e){return e.nodeName.toLowerCase()}var i=Object.freeze({__proto__:null,escapeHTML:t,inherit:r,nodeStream:function(e){var n=[];return function e(t,r){for(var i=t.firstChild;i;i=i.nextSibling)3===i.nodeType?r+=i.nodeValue.length:1===i.nodeType&&(n.push({event:"start",offset:r,node:i}),r=e(i,r),a(i).match(/br|hr|img|input/)||n.push({event:"stop",offset:r,node:i}));return r}(e,0),n},mergeStreams:function(e,n,r){var i=0,s="",o=[];function l(){return e.length&&n.length?e[0].offset!==n[0].offset?e[0].offset"}function u(e){s+=""}function d(e){("start"===e.event?c:u)(e.node)}for(;e.length||n.length;){var g=l();if(s+=t(r.substring(i,g[0].offset)),i=g[0].offset,g===e){o.reverse().forEach(u);do{d(g.splice(0,1)[0]),g=l()}while(g===e&&g.length&&g[0].offset===i);o.reverse().forEach(c)}else"start"===g[0].event?o.push(g[0].node):o.pop(),d(g.splice(0,1)[0])}return s+t(r.substr(i))}});const s=" ",o=e=>!!e.kind;class l{constructor(e,n){this.buffer="",this.classPrefix=n.classPrefix,e.walk(this)}addText(e){this.buffer+=t(e)}openNode(e){if(!o(e))return;let n=e.kind;e.sublanguage||(n=`${this.classPrefix}${n}`),this.span(n)}closeNode(e){o(e)&&(this.buffer+=s)}value(){return this.buffer}span(e){this.buffer+=``}}class c{constructor(){this.rootNode={children:[]},this.stack=[this.rootNode]}get top(){return this.stack[this.stack.length-1]}get root(){return this.rootNode}add(e){this.top.children.push(e)}openNode(e){const n={kind:e,children:[]};this.add(n),this.stack.push(n)}closeNode(){if(this.stack.length>1)return this.stack.pop()}closeAllNodes(){for(;this.closeNode(););}toJSON(){return JSON.stringify(this.rootNode,null,4)}walk(e){return this.constructor._walk(e,this.rootNode)}static _walk(e,n){return"string"==typeof n?e.addText(n):n.children&&(e.openNode(n),n.children.forEach(n=>this._walk(e,n)),e.closeNode(n)),e}static _collapse(e){"string"!=typeof e&&e.children&&(e.children.every(e=>"string"==typeof e)?e.children=[e.children.join("")]:e.children.forEach(e=>{c._collapse(e)}))}}class u extends c{constructor(e){super(),this.options=e}addKeyword(e,n){""!==e&&(this.openNode(n),this.addText(e),this.closeNode())}addText(e){""!==e&&this.add(e)}addSublanguage(e,n){const t=e.root;t.kind=n,t.sublanguage=!0,this.add(t)}toHTML(){return new l(this,this.options).value()}finalize(){return!0}}function d(e){return e?"string"==typeof e?e:e.source:null}const g="(-?)(\\b0[xX][a-fA-F0-9]+|(\\b\\d+(\\.\\d*)?|\\.\\d+)([eE][-+]?\\d+)?)",h={begin:"\\\\[\\s\\S]",relevance:0},f={className:"string",begin:"'",end:"'",illegal:"\\n",contains:[h]},p={className:"string",begin:'"',end:'"',illegal:"\\n",contains:[h]},b={begin:/\b(a|an|the|are|I'm|isn't|don't|doesn't|won't|but|just|should|pretty|simply|enough|gonna|going|wtf|so|such|will|you|your|they|like|more)\b/},m=function(e,n,t={}){var a=r({className:"comment",begin:e,end:n,contains:[]},t);return a.contains.push(b),a.contains.push({className:"doctag",begin:"(?:TODO|FIXME|NOTE|BUG|OPTIMIZE|HACK|XXX):",relevance:0}),a},v=m("//","$"),x=m("/\\*","\\*/"),E=m("#","$");var _=Object.freeze({__proto__:null,IDENT_RE:"[a-zA-Z]\\w*",UNDERSCORE_IDENT_RE:"[a-zA-Z_]\\w*",NUMBER_RE:"\\b\\d+(\\.\\d+)?",C_NUMBER_RE:g,BINARY_NUMBER_RE:"\\b(0b[01]+)",RE_STARTERS_RE:"!|!=|!==|%|%=|&|&&|&=|\\*|\\*=|\\+|\\+=|,|-|-=|/=|/|:|;|<<|<<=|<=|<|===|==|=|>>>=|>>=|>=|>>>|>>|>|\\?|\\[|\\{|\\(|\\^|\\^=|\\||\\|=|\\|\\||~",SHEBANG:(e={})=>{const n=/^#![ ]*\//;return e.binary&&(e.begin=function(...e){return e.map(e=>d(e)).join("")}(n,/.*\b/,e.binary,/\b.*/)),r({className:"meta",begin:n,end:/$/,relevance:0,"on:begin":(e,n)=>{0!==e.index&&n.ignoreMatch()}},e)},BACKSLASH_ESCAPE:h,APOS_STRING_MODE:f,QUOTE_STRING_MODE:p,PHRASAL_WORDS_MODE:b,COMMENT:m,C_LINE_COMMENT_MODE:v,C_BLOCK_COMMENT_MODE:x,HASH_COMMENT_MODE:E,NUMBER_MODE:{className:"number",begin:"\\b\\d+(\\.\\d+)?",relevance:0},C_NUMBER_MODE:{className:"number",begin:g,relevance:0},BINARY_NUMBER_MODE:{className:"number",begin:"\\b(0b[01]+)",relevance:0},CSS_NUMBER_MODE:{className:"number",begin:"\\b\\d+(\\.\\d+)?(%|em|ex|ch|rem|vw|vh|vmin|vmax|cm|mm|in|pt|pc|px|deg|grad|rad|turn|s|ms|Hz|kHz|dpi|dpcm|dppx)?",relevance:0},REGEXP_MODE:{begin:/(?=\/[^/\n]*\/)/,contains:[{className:"regexp",begin:/\//,end:/\/[gimuy]*/,illegal:/\n/,contains:[h,{begin:/\[/,end:/\]/,relevance:0,contains:[h]}]}]},TITLE_MODE:{className:"title",begin:"[a-zA-Z]\\w*",relevance:0},UNDERSCORE_TITLE_MODE:{className:"title",begin:"[a-zA-Z_]\\w*",relevance:0},METHOD_GUARD:{begin:"\\.\\s*[a-zA-Z_]\\w*",relevance:0},END_SAME_AS_BEGIN:function(e){return Object.assign(e,{"on:begin":(e,n)=>{n.data._beginMatch=e[1]},"on:end":(e,n)=>{n.data._beginMatch!==e[1]&&n.ignoreMatch()}})}}),N="of and for in not or if then".split(" ");function w(e,n){return n?+n:function(e){return N.includes(e.toLowerCase())}(e)?0:1}const R=t,y=r,{nodeStream:O,mergeStreams:k}=i,M=Symbol("nomatch");return function(t){var a=[],i=Object.create(null),s=Object.create(null),o=[],l=!0,c=/(^(<[^>]+>|\t|)+|\n)/gm,g="Could not find the language '{}', did you forget to load/include a language module?";const h={disableAutodetect:!0,name:"Plain text",contains:[]};var f={noHighlightRe:/^(no-?highlight)$/i,languageDetectRe:/\blang(?:uage)?-([\w-]+)\b/i,classPrefix:"hljs-",tabReplace:null,useBR:!1,languages:null,__emitter:u};function p(e){return f.noHighlightRe.test(e)}function b(e,n,t,r){var a={code:n,language:e};S("before:highlight",a);var i=a.result?a.result:m(a.language,a.code,t,r);return i.code=a.code,S("after:highlight",i),i}function m(e,t,a,s){var o=t;function c(e,n){var t=E.case_insensitive?n[0].toLowerCase():n[0];return Object.prototype.hasOwnProperty.call(e.keywords,t)&&e.keywords[t]}function u(){null!=y.subLanguage?function(){if(""!==A){var e=null;if("string"==typeof y.subLanguage){if(!i[y.subLanguage])return void k.addText(A);e=m(y.subLanguage,A,!0,O[y.subLanguage]),O[y.subLanguage]=e.top}else e=v(A,y.subLanguage.length?y.subLanguage:null);y.relevance>0&&(I+=e.relevance),k.addSublanguage(e.emitter,e.language)}}():function(){if(!y.keywords)return void k.addText(A);let e=0;y.keywordPatternRe.lastIndex=0;let n=y.keywordPatternRe.exec(A),t="";for(;n;){t+=A.substring(e,n.index);const r=c(y,n);if(r){const[e,a]=r;k.addText(t),t="",I+=a,k.addKeyword(n[0],e)}else t+=n[0];e=y.keywordPatternRe.lastIndex,n=y.keywordPatternRe.exec(A)}t+=A.substr(e),k.addText(t)}(),A=""}function h(e){return e.className&&k.openNode(e.className),y=Object.create(e,{parent:{value:y}})}function p(e){return 0===y.matcher.regexIndex?(A+=e[0],1):(L=!0,0)}var b={};function x(t,r){var i=r&&r[0];if(A+=t,null==i)return u(),0;if("begin"===b.type&&"end"===r.type&&b.index===r.index&&""===i){if(A+=o.slice(r.index,r.index+1),!l){const n=Error("0 width match regex");throw n.languageName=e,n.badRule=b.rule,n}return 1}if(b=r,"begin"===r.type)return function(e){var t=e[0],r=e.rule;const a=new n(r),i=[r.__beforeBegin,r["on:begin"]];for(const n of i)if(n&&(n(e,a),a.ignore))return p(t);return r&&r.endSameAsBegin&&(r.endRe=RegExp(t.replace(/[-/\\^$*+?.()|[\]{}]/g,"\\$&"),"m")),r.skip?A+=t:(r.excludeBegin&&(A+=t),u(),r.returnBegin||r.excludeBegin||(A=t)),h(r),r.returnBegin?0:t.length}(r);if("illegal"===r.type&&!a){const e=Error('Illegal lexeme "'+i+'" for mode "'+(y.className||"")+'"');throw e.mode=y,e}if("end"===r.type){var s=function(e){var t=e[0],r=o.substr(e.index),a=function e(t,r,a){let i=function(e,n){var t=e&&e.exec(n);return t&&0===t.index}(t.endRe,a);if(i){if(t["on:end"]){const e=new n(t);t["on:end"](r,e),e.ignore&&(i=!1)}if(i){for(;t.endsParent&&t.parent;)t=t.parent;return t}}if(t.endsWithParent)return e(t.parent,r,a)}(y,e,r);if(!a)return M;var i=y;i.skip?A+=t:(i.returnEnd||i.excludeEnd||(A+=t),u(),i.excludeEnd&&(A=t));do{y.className&&k.closeNode(),y.skip||y.subLanguage||(I+=y.relevance),y=y.parent}while(y!==a.parent);return a.starts&&(a.endSameAsBegin&&(a.starts.endRe=a.endRe),h(a.starts)),i.returnEnd?0:t.length}(r);if(s!==M)return s}if("illegal"===r.type&&""===i)return 1;if(B>1e5&&B>3*r.index)throw Error("potential infinite loop, way more iterations than matches");return A+=i,i.length}var E=T(e);if(!E)throw console.error(g.replace("{}",e)),Error('Unknown language: "'+e+'"');var _=function(e){function n(n,t){return RegExp(d(n),"m"+(e.case_insensitive?"i":"")+(t?"g":""))}class t{constructor(){this.matchIndexes={},this.regexes=[],this.matchAt=1,this.position=0}addRule(e,n){n.position=this.position++,this.matchIndexes[this.matchAt]=n,this.regexes.push([n,e]),this.matchAt+=function(e){return RegExp(e.toString()+"|").exec("").length-1}(e)+1}compile(){0===this.regexes.length&&(this.exec=()=>null);const e=this.regexes.map(e=>e[1]);this.matcherRe=n(function(e,n="|"){for(var t=/\[(?:[^\\\]]|\\.)*\]|\(\??|\\([1-9][0-9]*)|\\./,r=0,a="",i=0;i0&&(a+=n),a+="(";o.length>0;){var l=t.exec(o);if(null==l){a+=o;break}a+=o.substring(0,l.index),o=o.substring(l.index+l[0].length),"\\"===l[0][0]&&l[1]?a+="\\"+(+l[1]+s):(a+=l[0],"("===l[0]&&r++)}a+=")"}return a}(e),!0),this.lastIndex=0}exec(e){this.matcherRe.lastIndex=this.lastIndex;const n=this.matcherRe.exec(e);if(!n)return null;const t=n.findIndex((e,n)=>n>0&&void 0!==e),r=this.matchIndexes[t];return n.splice(0,t),Object.assign(n,r)}}class a{constructor(){this.rules=[],this.multiRegexes=[],this.count=0,this.lastIndex=0,this.regexIndex=0}getMatcher(e){if(this.multiRegexes[e])return this.multiRegexes[e];const n=new t;return this.rules.slice(e).forEach(([e,t])=>n.addRule(e,t)),n.compile(),this.multiRegexes[e]=n,n}considerAll(){this.regexIndex=0}addRule(e,n){this.rules.push([e,n]),"begin"===n.type&&this.count++}exec(e){const n=this.getMatcher(this.regexIndex);n.lastIndex=this.lastIndex;const t=n.exec(e);return t&&(this.regexIndex+=t.position+1,this.regexIndex===this.count&&(this.regexIndex=0)),t}}function i(e,n){const t=e.input[e.index-1],r=e.input[e.index+e[0].length];"."!==t&&"."!==r||n.ignoreMatch()}if(e.contains&&e.contains.includes("self"))throw Error("ERR: contains `self` is not supported at the top-level of a language. See documentation.");return function t(s,o){const l=s;if(s.compiled)return l;s.compiled=!0,s.__beforeBegin=null,s.keywords=s.keywords||s.beginKeywords;let c=null;if("object"==typeof s.keywords&&(c=s.keywords.$pattern,delete s.keywords.$pattern),s.keywords&&(s.keywords=function(e,n){var t={};return"string"==typeof e?r("keyword",e):Object.keys(e).forEach((function(n){r(n,e[n])})),t;function r(e,r){n&&(r=r.toLowerCase()),r.split(" ").forEach((function(n){var r=n.split("|");t[r[0]]=[e,w(r[0],r[1])]}))}}(s.keywords,e.case_insensitive)),s.lexemes&&c)throw Error("ERR: Prefer `keywords.$pattern` to `mode.lexemes`, BOTH are not allowed. (see mode reference) ");return l.keywordPatternRe=n(s.lexemes||c||/\w+/,!0),o&&(s.beginKeywords&&(s.begin="\\b("+s.beginKeywords.split(" ").join("|")+")(?=\\b|\\s)",s.__beforeBegin=i),s.begin||(s.begin=/\B|\b/),l.beginRe=n(s.begin),s.endSameAsBegin&&(s.end=s.begin),s.end||s.endsWithParent||(s.end=/\B|\b/),s.end&&(l.endRe=n(s.end)),l.terminator_end=d(s.end)||"",s.endsWithParent&&o.terminator_end&&(l.terminator_end+=(s.end?"|":"")+o.terminator_end)),s.illegal&&(l.illegalRe=n(s.illegal)),void 0===s.relevance&&(s.relevance=1),s.contains||(s.contains=[]),s.contains=[].concat(...s.contains.map((function(e){return function(e){return e.variants&&!e.cached_variants&&(e.cached_variants=e.variants.map((function(n){return r(e,{variants:null},n)}))),e.cached_variants?e.cached_variants:function e(n){return!!n&&(n.endsWithParent||e(n.starts))}(e)?r(e,{starts:e.starts?r(e.starts):null}):Object.isFrozen(e)?r(e):e}("self"===e?s:e)}))),s.contains.forEach((function(e){t(e,l)})),s.starts&&t(s.starts,o),l.matcher=function(e){const n=new a;return e.contains.forEach(e=>n.addRule(e.begin,{rule:e,type:"begin"})),e.terminator_end&&n.addRule(e.terminator_end,{type:"end"}),e.illegal&&n.addRule(e.illegal,{type:"illegal"}),n}(l),l}(e)}(E),N="",y=s||_,O={},k=new f.__emitter(f);!function(){for(var e=[],n=y;n!==E;n=n.parent)n.className&&e.unshift(n.className);e.forEach(e=>k.openNode(e))}();var A="",I=0,S=0,B=0,L=!1;try{for(y.matcher.considerAll();;){B++,L?L=!1:(y.matcher.lastIndex=S,y.matcher.considerAll());const e=y.matcher.exec(o);if(!e)break;const n=x(o.substring(S,e.index),e);S=e.index+n}return x(o.substr(S)),k.closeAllNodes(),k.finalize(),N=k.toHTML(),{relevance:I,value:N,language:e,illegal:!1,emitter:k,top:y}}catch(n){if(n.message&&n.message.includes("Illegal"))return{illegal:!0,illegalBy:{msg:n.message,context:o.slice(S-100,S+100),mode:n.mode},sofar:N,relevance:0,value:R(o),emitter:k};if(l)return{illegal:!1,relevance:0,value:R(o),emitter:k,language:e,top:y,errorRaised:n};throw n}}function v(e,n){n=n||f.languages||Object.keys(i);var t=function(e){const n={relevance:0,emitter:new f.__emitter(f),value:R(e),illegal:!1,top:h};return n.emitter.addText(e),n}(e),r=t;return n.filter(T).filter(I).forEach((function(n){var a=m(n,e,!1);a.language=n,a.relevance>r.relevance&&(r=a),a.relevance>t.relevance&&(r=t,t=a)})),r.language&&(t.second_best=r),t}function x(e){return f.tabReplace||f.useBR?e.replace(c,e=>"\n"===e?f.useBR?"
":e:f.tabReplace?e.replace(/\t/g,f.tabReplace):e):e}function E(e){let n=null;const t=function(e){var n=e.className+" ";n+=e.parentNode?e.parentNode.className:"";const t=f.languageDetectRe.exec(n);if(t){var r=T(t[1]);return r||(console.warn(g.replace("{}",t[1])),console.warn("Falling back to no-highlight mode for this block.",e)),r?t[1]:"no-highlight"}return n.split(/\s+/).find(e=>p(e)||T(e))}(e);if(p(t))return;S("before:highlightBlock",{block:e,language:t}),f.useBR?(n=document.createElement("div")).innerHTML=e.innerHTML.replace(/\n/g,"").replace(//g,"\n"):n=e;const r=n.textContent,a=t?b(t,r,!0):v(r),i=O(n);if(i.length){const e=document.createElement("div");e.innerHTML=a.value,a.value=k(i,O(e),r)}a.value=x(a.value),S("after:highlightBlock",{block:e,result:a}),e.innerHTML=a.value,e.className=function(e,n,t){var r=n?s[n]:t,a=[e.trim()];return e.match(/\bhljs\b/)||a.push("hljs"),e.includes(r)||a.push(r),a.join(" ").trim()}(e.className,t,a.language),e.result={language:a.language,re:a.relevance,relavance:a.relevance},a.second_best&&(e.second_best={language:a.second_best.language,re:a.second_best.relevance,relavance:a.second_best.relevance})}const N=()=>{if(!N.called){N.called=!0;var e=document.querySelectorAll("pre code");a.forEach.call(e,E)}};function T(e){return e=(e||"").toLowerCase(),i[e]||i[s[e]]}function A(e,{languageName:n}){"string"==typeof e&&(e=[e]),e.forEach(e=>{s[e]=n})}function I(e){var n=T(e);return n&&!n.disableAutodetect}function S(e,n){var t=e;o.forEach((function(e){e[t]&&e[t](n)}))}Object.assign(t,{highlight:b,highlightAuto:v,fixMarkup:x,highlightBlock:E,configure:function(e){f=y(f,e)},initHighlighting:N,initHighlightingOnLoad:function(){window.addEventListener("DOMContentLoaded",N,!1)},registerLanguage:function(e,n){var r=null;try{r=n(t)}catch(n){if(console.error("Language definition for '{}' could not be registered.".replace("{}",e)),!l)throw n;console.error(n),r=h}r.name||(r.name=e),i[e]=r,r.rawDefinition=n.bind(null,t),r.aliases&&A(r.aliases,{languageName:e})},listLanguages:function(){return Object.keys(i)},getLanguage:T,registerAliases:A,requireLanguage:function(e){var n=T(e);if(n)return n;throw Error("The '{}' language is required, but not loaded.".replace("{}",e))},autoDetection:I,inherit:y,addPlugin:function(e){o.push(e)}}),t.debugMode=function(){l=!1},t.safeMode=function(){l=!0},t.versionString="10.1.2";for(const n in _)"object"==typeof _[n]&&e(_[n]);return Object.assign(t,_),t}({})}();"object"==typeof exports&&"undefined"!=typeof module&&(module.exports=hljs);hljs.registerLanguage("xml",function(){"use strict";return function(e){var n={className:"symbol",begin:"&[a-z]+;|&#[0-9]+;|&#x[a-f0-9]+;"},a={begin:"\\s",contains:[{className:"meta-keyword",begin:"#?[a-z_][a-z1-9_-]+",illegal:"\\n"}]},s=e.inherit(a,{begin:"\\(",end:"\\)"}),t=e.inherit(e.APOS_STRING_MODE,{className:"meta-string"}),i=e.inherit(e.QUOTE_STRING_MODE,{className:"meta-string"}),c={endsWithParent:!0,illegal:/`]+/}]}]}]};return{name:"HTML, XML",aliases:["html","xhtml","rss","atom","xjb","xsd","xsl","plist","wsf","svg"],case_insensitive:!0,contains:[{className:"meta",begin:"",relevance:10,contains:[a,i,t,s,{begin:"\\[",end:"\\]",contains:[{className:"meta",begin:"",contains:[a,s,i,t]}]}]},e.COMMENT("\x3c!--","--\x3e",{relevance:10}),{begin:"<\\!\\[CDATA\\[",end:"\\]\\]>",relevance:10},n,{className:"meta",begin:/<\?xml/,end:/\?>/,relevance:10},{className:"tag",begin:")",end:">",keywords:{name:"style"},contains:[c],starts:{end:"",returnEnd:!0,subLanguage:["css","xml"]}},{className:"tag",begin:")",end:">",keywords:{name:"script"},contains:[c],starts:{end:"<\/script>",returnEnd:!0,subLanguage:["javascript","handlebars","xml"]}},{className:"tag",begin:"",contains:[{className:"name",begin:/[^\/><\s]+/,relevance:0},c]}]}}}());hljs.registerLanguage("markdown",function(){"use strict";return function(n){const e={begin:"<",end:">",subLanguage:"xml",relevance:0},a={begin:"\\[.+?\\][\\(\\[].*?[\\)\\]]",returnBegin:!0,contains:[{className:"string",begin:"\\[",end:"\\]",excludeBegin:!0,returnEnd:!0,relevance:0},{className:"link",begin:"\\]\\(",end:"\\)",excludeBegin:!0,excludeEnd:!0},{className:"symbol",begin:"\\]\\[",end:"\\]",excludeBegin:!0,excludeEnd:!0}],relevance:10},i={className:"strong",contains:[],variants:[{begin:/_{2}/,end:/_{2}/},{begin:/\*{2}/,end:/\*{2}/}]},s={className:"emphasis",contains:[],variants:[{begin:/\*(?!\*)/,end:/\*/},{begin:/_(?!_)/,end:/_/,relevance:0}]};i.contains.push(s),s.contains.push(i);var c=[e,a];return i.contains=i.contains.concat(c),s.contains=s.contains.concat(c),{name:"Markdown",aliases:["md","mkdown","mkd"],contains:[{className:"section",variants:[{begin:"^#{1,6}",end:"$",contains:c=c.concat(i,s)},{begin:"(?=^.+?\\n[=-]{2,}$)",contains:[{begin:"^[=-]*$"},{begin:"^",end:"\\n",contains:c}]}]},e,{className:"bullet",begin:"^[ \t]*([*+-]|(\\d+\\.))(?=\\s+)",end:"\\s+",excludeEnd:!0},i,s,{className:"quote",begin:"^>\\s+",contains:c,end:"$"},{className:"code",variants:[{begin:"(`{3,})(.|\\n)*?\\1`*[ ]*"},{begin:"(~{3,})(.|\\n)*?\\1~*[ ]*"},{begin:"```",end:"```+[ ]*$"},{begin:"~~~",end:"~~~+[ ]*$"},{begin:"`.+?`"},{begin:"(?=^( {4}|\\t))",contains:[{begin:"^( {4}|\\t)",end:"(\\n)$"}],relevance:0}]},{begin:"^[-\\*]{3,}",end:"$"},a,{begin:/^\[[^\n]+\]:/,returnBegin:!0,contains:[{className:"symbol",begin:/\[/,end:/\]/,excludeBegin:!0,excludeEnd:!0},{className:"link",begin:/:\s*/,end:/$/,excludeBegin:!0}]}]}}}());hljs.registerLanguage("perl",function(){"use strict";return function(e){var n={$pattern:/[\w.]+/,keyword:"getpwent getservent quotemeta msgrcv scalar kill dbmclose undef lc ma syswrite tr send umask sysopen shmwrite vec qx utime local oct semctl localtime readpipe do return format read sprintf dbmopen pop getpgrp not getpwnam rewinddir qq fileno qw endprotoent wait sethostent bless s|0 opendir continue each sleep endgrent shutdown dump chomp connect getsockname die socketpair close flock exists index shmget sub for endpwent redo lstat msgctl setpgrp abs exit select print ref gethostbyaddr unshift fcntl syscall goto getnetbyaddr join gmtime symlink semget splice x|0 getpeername recv log setsockopt cos last reverse gethostbyname getgrnam study formline endhostent times chop length gethostent getnetent pack getprotoent getservbyname rand mkdir pos chmod y|0 substr endnetent printf next open msgsnd readdir use unlink getsockopt getpriority rindex wantarray hex system getservbyport endservent int chr untie rmdir prototype tell listen fork shmread ucfirst setprotoent else sysseek link getgrgid shmctl waitpid unpack getnetbyname reset chdir grep split require caller lcfirst until warn while values shift telldir getpwuid my getprotobynumber delete and sort uc defined srand accept package seekdir getprotobyname semop our rename seek if q|0 chroot sysread setpwent no crypt getc chown sqrt write setnetent setpriority foreach tie sin msgget map stat getlogin unless elsif truncate exec keys glob tied closedir ioctl socket readlink eval xor readline binmode setservent eof ord bind alarm pipe atan2 getgrent exp time push setgrent gt lt or ne m|0 break given say state when"},t={className:"subst",begin:"[$@]\\{",end:"\\}",keywords:n},s={begin:"->{",end:"}"},r={variants:[{begin:/\$\d/},{begin:/[\$%@](\^\w\b|#\w+(::\w+)*|{\w+}|\w+(::\w*)*)/},{begin:/[\$%@][^\s\w{]/,relevance:0}]},i=[e.BACKSLASH_ESCAPE,t,r],a=[r,e.HASH_COMMENT_MODE,e.COMMENT("^\\=\\w","\\=cut",{endsWithParent:!0}),s,{className:"string",contains:i,variants:[{begin:"q[qwxr]?\\s*\\(",end:"\\)",relevance:5},{begin:"q[qwxr]?\\s*\\[",end:"\\]",relevance:5},{begin:"q[qwxr]?\\s*\\{",end:"\\}",relevance:5},{begin:"q[qwxr]?\\s*\\|",end:"\\|",relevance:5},{begin:"q[qwxr]?\\s*\\<",end:"\\>",relevance:5},{begin:"qw\\s+q",end:"q",relevance:5},{begin:"'",end:"'",contains:[e.BACKSLASH_ESCAPE]},{begin:'"',end:'"'},{begin:"`",end:"`",contains:[e.BACKSLASH_ESCAPE]},{begin:"{\\w+}",contains:[],relevance:0},{begin:"-?\\w+\\s*\\=\\>",contains:[],relevance:0}]},{className:"number",begin:"(\\b0[0-7_]+)|(\\b0x[0-9a-fA-F_]+)|(\\b[1-9][0-9_]*(\\.[0-9_]+)?)|[0_]\\b",relevance:0},{begin:"(\\/\\/|"+e.RE_STARTERS_RE+"|\\b(split|return|print|reverse|grep)\\b)\\s*",keywords:"split return print reverse grep",relevance:0,contains:[e.HASH_COMMENT_MODE,{className:"regexp",begin:"(s|tr|y)/(\\\\.|[^/])*/(\\\\.|[^/])*/[a-z]*",relevance:10},{className:"regexp",begin:"(m|qr)?/",end:"/[a-z]*",contains:[e.BACKSLASH_ESCAPE],relevance:0}]},{className:"function",beginKeywords:"sub",end:"(\\s*\\(.*?\\))?[;{]",excludeEnd:!0,relevance:5,contains:[e.TITLE_MODE]},{begin:"-\\w\\b",relevance:0},{begin:"^__DATA__$",end:"^__END__$",subLanguage:"mojolicious",contains:[{begin:"^@@.*",end:"$",className:"comment"}]}];return t.contains=a,s.contains=a,{name:"Perl",aliases:["pl","pm"],keywords:n,contains:a}}}());hljs.registerLanguage("plaintext",function(){"use strict";return function(t){return{name:"Plain text",aliases:["text","txt"],disableAutodetect:!0}}}());hljs.registerLanguage("ini",function(){"use strict";function e(e){return e?"string"==typeof e?e:e.source:null}function n(...n){return n.map(n=>e(n)).join("")}return function(a){var s={className:"number",relevance:0,variants:[{begin:/([\+\-]+)?[\d]+_[\d_]+/},{begin:a.NUMBER_RE}]},i=a.COMMENT();i.variants=[{begin:/;/,end:/$/},{begin:/#/,end:/$/}];var t={className:"variable",variants:[{begin:/\$[\w\d"][\w\d_]*/},{begin:/\$\{(.*?)}/}]},r={className:"literal",begin:/\bon|off|true|false|yes|no\b/},l={className:"string",contains:[a.BACKSLASH_ESCAPE],variants:[{begin:"'''",end:"'''",relevance:10},{begin:'"""',end:'"""',relevance:10},{begin:'"',end:'"'},{begin:"'",end:"'"}]},c={begin:/\[/,end:/\]/,contains:[i,r,t,l,s,"self"],relevance:0},g="("+[/[A-Za-z0-9_-]+/,/"(\\"|[^"])*"/,/'[^']*'/].map(n=>e(n)).join("|")+")";return{name:"TOML, also INI",aliases:["toml"],case_insensitive:!0,illegal:/\S/,contains:[i,{className:"section",begin:/\[+/,end:/\]+/},{begin:n(g,"(\\s*\\.\\s*",g,")*",n("(?=",/\s*=\s*[^#\s]/,")")),className:"attr",starts:{end:/$/,contains:[i,c,r,t,l,s]}}]}}}());hljs.registerLanguage("json",function(){"use strict";return function(n){var e={literal:"true false null"},i=[n.C_LINE_COMMENT_MODE,n.C_BLOCK_COMMENT_MODE],t=[n.QUOTE_STRING_MODE,n.C_NUMBER_MODE],a={end:",",endsWithParent:!0,excludeEnd:!0,contains:t,keywords:e},l={begin:"{",end:"}",contains:[{className:"attr",begin:/"/,end:/"/,contains:[n.BACKSLASH_ESCAPE],illegal:"\\n"},n.inherit(a,{begin:/:/})].concat(i),illegal:"\\S"},s={begin:"\\[",end:"\\]",contains:[n.inherit(a)],illegal:"\\S"};return t.push(l,s),i.forEach((function(n){t.push(n)})),{name:"JSON",contains:t,keywords:e,illegal:"\\S"}}}());hljs.registerLanguage("ruby",function(){"use strict";return function(e){var n="[a-zA-Z_]\\w*[!?=]?|[-+~]\\@|<<|>>|=~|===?|<=>|[<>]=?|\\*\\*|[-/+%^&*~`|]|\\[\\]=?",a={keyword:"and then defined module in return redo if BEGIN retry end for self when next until do begin unless END rescue else break undef not super class case require yield alias while ensure elsif or include attr_reader attr_writer attr_accessor",literal:"true false nil"},s={className:"doctag",begin:"@[A-Za-z]+"},i={begin:"#<",end:">"},r=[e.COMMENT("#","$",{contains:[s]}),e.COMMENT("^\\=begin","^\\=end",{contains:[s],relevance:10}),e.COMMENT("^__END__","\\n$")],c={className:"subst",begin:"#\\{",end:"}",keywords:a},t={className:"string",contains:[e.BACKSLASH_ESCAPE,c],variants:[{begin:/'/,end:/'/},{begin:/"/,end:/"/},{begin:/`/,end:/`/},{begin:"%[qQwWx]?\\(",end:"\\)"},{begin:"%[qQwWx]?\\[",end:"\\]"},{begin:"%[qQwWx]?{",end:"}"},{begin:"%[qQwWx]?<",end:">"},{begin:"%[qQwWx]?/",end:"/"},{begin:"%[qQwWx]?%",end:"%"},{begin:"%[qQwWx]?-",end:"-"},{begin:"%[qQwWx]?\\|",end:"\\|"},{begin:/\B\?(\\\d{1,3}|\\x[A-Fa-f0-9]{1,2}|\\u[A-Fa-f0-9]{4}|\\?\S)\b/},{begin:/<<[-~]?'?(\w+)(?:.|\n)*?\n\s*\1\b/,returnBegin:!0,contains:[{begin:/<<[-~]?'?/},e.END_SAME_AS_BEGIN({begin:/(\w+)/,end:/(\w+)/,contains:[e.BACKSLASH_ESCAPE,c]})]}]},b={className:"params",begin:"\\(",end:"\\)",endsParent:!0,keywords:a},d=[t,i,{className:"class",beginKeywords:"class module",end:"$|;",illegal:/=/,contains:[e.inherit(e.TITLE_MODE,{begin:"[A-Za-z_]\\w*(::\\w+)*(\\?|\\!)?"}),{begin:"<\\s*",contains:[{begin:"("+e.IDENT_RE+"::)?"+e.IDENT_RE}]}].concat(r)},{className:"function",beginKeywords:"def",end:"$|;",contains:[e.inherit(e.TITLE_MODE,{begin:n}),b].concat(r)},{begin:e.IDENT_RE+"::"},{className:"symbol",begin:e.UNDERSCORE_IDENT_RE+"(\\!|\\?)?:",relevance:0},{className:"symbol",begin:":(?!\\s)",contains:[t,{begin:n}],relevance:0},{className:"number",begin:"(\\b0[0-7_]+)|(\\b0x[0-9a-fA-F_]+)|(\\b[1-9][0-9_]*(\\.[0-9_]+)?)|[0_]\\b",relevance:0},{begin:"(\\$\\W)|((\\$|\\@\\@?)(\\w+))"},{className:"params",begin:/\|/,end:/\|/,keywords:a},{begin:"("+e.RE_STARTERS_RE+"|unless)\\s*",keywords:"unless",contains:[i,{className:"regexp",contains:[e.BACKSLASH_ESCAPE,c],illegal:/\n/,variants:[{begin:"/",end:"/[a-z]*"},{begin:"%r{",end:"}[a-z]*"},{begin:"%r\\(",end:"\\)[a-z]*"},{begin:"%r!",end:"![a-z]*"},{begin:"%r\\[",end:"\\][a-z]*"}]}].concat(r),relevance:0}].concat(r);c.contains=d,b.contains=d;var g=[{begin:/^\s*=>/,starts:{end:"$",contains:d}},{className:"meta",begin:"^([>?]>|[\\w#]+\\(\\w+\\):\\d+:\\d+>|(\\w+-)?\\d+\\.\\d+\\.\\d(p\\d+)?[^>]+>)",starts:{end:"$",contains:d}}];return{name:"Ruby",aliases:["rb","gemspec","podspec","thor","irb"],keywords:a,illegal:/\/\*/,contains:r.concat(g).concat(d)}}}());hljs.registerLanguage("yaml",function(){"use strict";return function(e){var n="true false yes no null",a="[\\w#;/?:@&=+$,.~*\\'()[\\]]+",s={className:"string",relevance:0,variants:[{begin:/'/,end:/'/},{begin:/"/,end:/"/},{begin:/\S+/}],contains:[e.BACKSLASH_ESCAPE,{className:"template-variable",variants:[{begin:"{{",end:"}}"},{begin:"%{",end:"}"}]}]},i=e.inherit(s,{variants:[{begin:/'/,end:/'/},{begin:/"/,end:/"/},{begin:/[^\s,{}[\]]+/}]}),l={end:",",endsWithParent:!0,excludeEnd:!0,contains:[],keywords:n,relevance:0},t={begin:"{",end:"}",contains:[l],illegal:"\\n",relevance:0},g={begin:"\\[",end:"\\]",contains:[l],illegal:"\\n",relevance:0},b=[{className:"attr",variants:[{begin:"\\w[\\w :\\/.-]*:(?=[ \t]|$)"},{begin:'"\\w[\\w :\\/.-]*":(?=[ \t]|$)'},{begin:"'\\w[\\w :\\/.-]*':(?=[ \t]|$)"}]},{className:"meta",begin:"^---s*$",relevance:10},{className:"string",begin:"[\\|>]([0-9]?[+-])?[ ]*\\n( *)[\\S ]+\\n(\\2[\\S ]+\\n?)*"},{begin:"<%[%=-]?",end:"[%-]?%>",subLanguage:"ruby",excludeBegin:!0,excludeEnd:!0,relevance:0},{className:"type",begin:"!\\w+!"+a},{className:"type",begin:"!<"+a+">"},{className:"type",begin:"!"+a},{className:"type",begin:"!!"+a},{className:"meta",begin:"&"+e.UNDERSCORE_IDENT_RE+"$"},{className:"meta",begin:"\\*"+e.UNDERSCORE_IDENT_RE+"$"},{className:"bullet",begin:"\\-(?=[ ]|$)",relevance:0},e.HASH_COMMENT_MODE,{beginKeywords:n,keywords:{literal:n}},{className:"number",begin:"\\b[0-9]{4}(-[0-9][0-9]){0,2}([Tt \\t][0-9][0-9]?(:[0-9][0-9]){2})?(\\.[0-9]*)?([ \\t])*(Z|[-+][0-9][0-9]?(:[0-9][0-9])?)?\\b"},{className:"number",begin:e.C_NUMBER_RE+"\\b"},t,g,s],c=[...b];return c.pop(),c.push(i),l.contains=c,{name:"YAML",case_insensitive:!0,aliases:["yml","YAML"],contains:b}}}());hljs.registerLanguage("haskell",function(){"use strict";return function(e){var n={variants:[e.COMMENT("--","$"),e.COMMENT("{-","-}",{contains:["self"]})]},i={className:"meta",begin:"{-#",end:"#-}"},a={className:"meta",begin:"^#",end:"$"},s={className:"type",begin:"\\b[A-Z][\\w']*",relevance:0},l={begin:"\\(",end:"\\)",illegal:'"',contains:[i,a,{className:"type",begin:"\\b[A-Z][\\w]*(\\((\\.\\.|,|\\w+)\\))?"},e.inherit(e.TITLE_MODE,{begin:"[_a-z][\\w']*"}),n]};return{name:"Haskell",aliases:["hs"],keywords:"let in if then else case of where do module import hiding qualified type data newtype deriving class instance as default infix infixl infixr foreign export ccall stdcall cplusplus jvm dotnet safe unsafe family forall mdo proc rec",contains:[{beginKeywords:"module",end:"where",keywords:"module where",contains:[l,n],illegal:"\\W\\.|;"},{begin:"\\bimport\\b",end:"$",keywords:"import qualified as hiding",contains:[l,n],illegal:"\\W\\.|;"},{className:"class",begin:"^(\\s*)?(class|instance)\\b",end:"where",keywords:"class family instance where",contains:[s,l,n]},{className:"class",begin:"\\b(data|(new)?type)\\b",end:"$",keywords:"data family type newtype deriving",contains:[i,s,l,{begin:"{",end:"}",contains:l.contains},n]},{beginKeywords:"default",end:"$",contains:[s,l,n]},{beginKeywords:"infix infixl infixr",end:"$",contains:[e.C_NUMBER_MODE,n]},{begin:"\\bforeign\\b",end:"$",keywords:"foreign import export ccall stdcall cplusplus jvm dotnet safe unsafe",contains:[s,e.QUOTE_STRING_MODE,n]},{className:"meta",begin:"#!\\/usr\\/bin\\/env runhaskell",end:"$"},i,a,e.QUOTE_STRING_MODE,e.C_NUMBER_MODE,s,e.inherit(e.TITLE_MODE,{begin:"^[_a-z][\\w']*"}),n,{begin:"->|<-"}]}}}());hljs.registerLanguage("nix",function(){"use strict";return function(e){var n={keyword:"rec with let in inherit assert if else then",literal:"true false or and null",built_in:"import abort baseNameOf dirOf isNull builtins map removeAttrs throw toString derivation"},i={className:"subst",begin:/\$\{/,end:/}/,keywords:n},t={className:"string",contains:[i],variants:[{begin:"''",end:"''"},{begin:'"',end:'"'}]},s=[e.NUMBER_MODE,e.HASH_COMMENT_MODE,e.C_BLOCK_COMMENT_MODE,t,{begin:/[a-zA-Z0-9-_]+(\s*=)/,returnBegin:!0,relevance:0,contains:[{className:"attr",begin:/\S+/}]}];return i.contains=s,{name:"Nix",aliases:["nixos"],keywords:n,contains:s}}}());hljs.registerLanguage("bash",function(){"use strict";return function(e){const s={};Object.assign(s,{className:"variable",variants:[{begin:/\$[\w\d#@][\w\d_]*/},{begin:/\$\{/,end:/\}/,contains:[{begin:/:-/,contains:[s]}]}]});const t={className:"subst",begin:/\$\(/,end:/\)/,contains:[e.BACKSLASH_ESCAPE]},n={className:"string",begin:/"/,end:/"/,contains:[e.BACKSLASH_ESCAPE,s,t]};t.contains.push(n);const a={begin:/\$\(\(/,end:/\)\)/,contains:[{begin:/\d+#[0-9a-f]+/,className:"number"},e.NUMBER_MODE,s]},i=e.SHEBANG({binary:"(fish|bash|zsh|sh|csh|ksh|tcsh|dash|scsh)",relevance:10}),c={className:"function",begin:/\w[\w\d_]*\s*\(\s*\)\s*\{/,returnBegin:!0,contains:[e.inherit(e.TITLE_MODE,{begin:/\w[\w\d_]*/})],relevance:0};return{name:"Bash",aliases:["sh","zsh"],keywords:{$pattern:/\b-?[a-z\._]+\b/,keyword:"if then else elif fi for while in do done case esac function",literal:"true false",built_in:"break cd continue eval exec exit export getopts hash pwd readonly return shift test times trap umask unset alias bind builtin caller command declare echo enable help let local logout mapfile printf read readarray source type typeset ulimit unalias set shopt autoload bg bindkey bye cap chdir clone comparguments compcall compctl compdescribe compfiles compgroups compquote comptags comptry compvalues dirs disable disown echotc echoti emulate fc fg float functions getcap getln history integer jobs kill limit log noglob popd print pushd pushln rehash sched setcap setopt stat suspend ttyctl unfunction unhash unlimit unsetopt vared wait whence where which zcompile zformat zftp zle zmodload zparseopts zprof zpty zregexparse zsocket zstyle ztcp",_:"-ne -eq -lt -gt -f -d -e -s -l -a"},contains:[i,e.SHEBANG(),c,a,e.HASH_COMMENT_MODE,n,{className:"",begin:/\\"/},{className:"string",begin:/'/,end:/'/},s]}}}());hljs.registerLanguage("shell",function(){"use strict";return function(s){return{name:"Shell Session",aliases:["console"],contains:[{className:"meta",begin:"^\\s{0,3}[/\\w\\d\\[\\]()@-]*[>%$#]",starts:{end:"$",subLanguage:"bash"}}]}}}());hljs.registerLanguage("python",function(){"use strict";return function(e){var n={keyword:"and elif is global as in if from raise for except finally print import pass return exec else break not with class assert yield try while continue del or def lambda async await nonlocal|10",built_in:"Ellipsis NotImplemented",literal:"False None True"},a={className:"meta",begin:/^(>>>|\.\.\.) /},i={className:"subst",begin:/\{/,end:/\}/,keywords:n,illegal:/#/},s={begin:/\{\{/,relevance:0},r={className:"string",contains:[e.BACKSLASH_ESCAPE],variants:[{begin:/(u|b)?r?'''/,end:/'''/,contains:[e.BACKSLASH_ESCAPE,a],relevance:10},{begin:/(u|b)?r?"""/,end:/"""/,contains:[e.BACKSLASH_ESCAPE,a],relevance:10},{begin:/(fr|rf|f)'''/,end:/'''/,contains:[e.BACKSLASH_ESCAPE,a,s,i]},{begin:/(fr|rf|f)"""/,end:/"""/,contains:[e.BACKSLASH_ESCAPE,a,s,i]},{begin:/(u|r|ur)'/,end:/'/,relevance:10},{begin:/(u|r|ur)"/,end:/"/,relevance:10},{begin:/(b|br)'/,end:/'/},{begin:/(b|br)"/,end:/"/},{begin:/(fr|rf|f)'/,end:/'/,contains:[e.BACKSLASH_ESCAPE,s,i]},{begin:/(fr|rf|f)"/,end:/"/,contains:[e.BACKSLASH_ESCAPE,s,i]},e.APOS_STRING_MODE,e.QUOTE_STRING_MODE]},l={className:"number",relevance:0,variants:[{begin:e.BINARY_NUMBER_RE+"[lLjJ]?"},{begin:"\\b(0o[0-7]+)[lLjJ]?"},{begin:e.C_NUMBER_RE+"[lLjJ]?"}]},t={className:"params",variants:[{begin:/\(\s*\)/,skip:!0,className:null},{begin:/\(/,end:/\)/,excludeBegin:!0,excludeEnd:!0,contains:["self",a,l,r,e.HASH_COMMENT_MODE]}]};return i.contains=[r,l,a],{name:"Python",aliases:["py","gyp","ipython"],keywords:n,illegal:/(<\/|->|\?)|=>/,contains:[a,l,{beginKeywords:"if",relevance:0},r,e.HASH_COMMENT_MODE,{variants:[{className:"function",beginKeywords:"def"},{className:"class",beginKeywords:"class"}],end:/:/,illegal:/[${=;\n,]/,contains:[e.UNDERSCORE_TITLE_MODE,t,{begin:/->/,endsWithParent:!0,keywords:"None"}]},{className:"meta",begin:/^[\t ]*@/,end:/$/},{begin:/\b(print|exec)\(/}]}}}());
diff --git a/doc/manual/utils.nix b/doc/manual/utils.nix
deleted file mode 100644
index 17e6378eb..000000000
--- a/doc/manual/utils.nix
+++ /dev/null
@@ -1,139 +0,0 @@
-with builtins;
-
-rec {
- splitLines = s: filter (x: !isList x) (split "\n" s);
-
- concatStrings = concatStringsSep "";
-
- attrsToList =
- a:
- map (name: {
- inherit name;
- value = a.${name};
- }) (builtins.attrNames a);
-
- replaceStringsRec =
- from: to: string:
- # recursively replace occurrences of `from` with `to` within `string`
- # example:
- # replaceStringRec "--" "-" "hello-----world"
- # => "hello-world"
- let
- replaced = replaceStrings [ from ] [ to ] string;
- in
- if replaced == string then string else replaceStringsRec from to replaced;
-
- squash = replaceStringsRec "\n\n\n" "\n\n";
-
- trim =
- string:
- # trim trailing spaces and squash non-leading spaces
- let
- trimLine =
- line:
- let
- # separate leading spaces from the rest
- parts = split "(^ *)" line;
- spaces = head (elemAt parts 1);
- rest = elemAt parts 2;
- # drop trailing spaces
- body = head (split " *$" rest);
- in
- spaces + replaceStringsRec " " " " body;
- in
- concatStringsSep "\n" (map trimLine (splitLines string));
-
- # FIXME: O(n^2)
- unique = foldl' (acc: e: if elem e acc then acc else acc ++ [ e ]) [ ];
-
- nameValuePair = name: value: { inherit name value; };
-
- filterAttrs =
- pred: set:
- listToAttrs (
- concatMap (
- name:
- let
- v = set.${name};
- in
- if pred name v then [ (nameValuePair name v) ] else [ ]
- ) (attrNames set)
- );
-
- optionalString = cond: string: if cond then string else "";
-
- showSetting =
- { inlineHTML }:
- name:
- {
- description,
- documentDefault,
- defaultValue,
- aliases,
- value,
- experimentalFeature,
- }:
- let
- result = squash ''
- - ${
- if inlineHTML then ''[`${name}`](#conf-${name})'' else ''`${name}`''
- }
-
- ${indent " " body}
- '';
-
- experimentalFeatureNote = optionalString (experimentalFeature != null) ''
- > **Warning**
- > This setting is part of an
- > [experimental feature](@docroot@/contributing/experimental-features.md).
-
- To change this setting, you need to make sure the corresponding experimental feature,
- [`${experimentalFeature}`](@docroot@/contributing/experimental-features.md#xp-feature-${experimentalFeature}),
- is enabled.
- For example, include the following in [`nix.conf`](#):
-
- ```
- extra-experimental-features = ${experimentalFeature}
- ${name} = ...
- ```
- '';
-
- # separate body to cleanly handle indentation
- body = ''
- ${description}
-
- ${experimentalFeatureNote}
-
- **Default:** ${showDefault documentDefault defaultValue}
-
- ${showAliases aliases}
- '';
-
- showDefault =
- documentDefault: defaultValue:
- if documentDefault then
- # a StringMap value type is specified as a string, but
- # this shows the value type. The empty stringmap is `null` in
- # JSON, but that converts to `{ }` here.
- if defaultValue == "" || defaultValue == [ ] || isAttrs defaultValue then
- "*empty*"
- else if isBool defaultValue then
- if defaultValue then "`true`" else "`false`"
- else
- "`${toString defaultValue}`"
- else
- "*machine-specific*";
-
- showAliases =
- aliases:
- optionalString (aliases != [ ])
- "**Deprecated alias:** ${(concatStringsSep ", " (map (s: "`${s}`") aliases))}";
- in
- result;
-
- indent =
- prefix: s: concatStringsSep "\n" (map (x: if x == "" then x else "${prefix}${x}") (splitLines s));
-
- showSettings =
- args: settingsInfo: concatStrings (attrValues (mapAttrs (showSetting args) settingsInfo));
-}
diff --git a/docker.nix b/docker.nix
deleted file mode 100644
index 2d57cd548..000000000
--- a/docker.nix
+++ /dev/null
@@ -1,315 +0,0 @@
-{
- pkgs ? import { },
- lib ? pkgs.lib,
- name ? "nix",
- tag ? "latest",
- bundleNixpkgs ? true,
- channelName ? "nixpkgs",
- channelURL ? "https://nixos.org/channels/nixpkgs-unstable",
- extraPkgs ? [ ],
- maxLayers ? 100,
- nixConf ? { },
- flake-registry ? null,
-}:
-let
- defaultPkgs =
- with pkgs;
- [
- nix
- bashInteractive
- coreutils-full
- gnutar
- gzip
- gnugrep
- which
- curl
- less
- wget
- man
- cacert.out
- findutils
- iana-etc
- git
- openssh
- ]
- ++ extraPkgs;
-
- users =
- {
-
- root = {
- uid = 0;
- shell = "${pkgs.bashInteractive}/bin/bash";
- home = "/root";
- gid = 0;
- groups = [ "root" ];
- description = "System administrator";
- };
-
- nobody = {
- uid = 65534;
- shell = "${pkgs.shadow}/bin/nologin";
- home = "/var/empty";
- gid = 65534;
- groups = [ "nobody" ];
- description = "Unprivileged account (don't use!)";
- };
- }
- // lib.listToAttrs (
- map (n: {
- name = "nixbld${toString n}";
- value = {
- uid = 30000 + n;
- gid = 30000;
- groups = [ "nixbld" ];
- description = "Nix build user ${toString n}";
- };
- }) (lib.lists.range 1 32)
- );
-
- groups = {
- root.gid = 0;
- nixbld.gid = 30000;
- nobody.gid = 65534;
- };
-
- userToPasswd = (
- k:
- {
- uid,
- gid ? 65534,
- home ? "/var/empty",
- description ? "",
- shell ? "/bin/false",
- groups ? [ ],
- }:
- "${k}:x:${toString uid}:${toString gid}:${description}:${home}:${shell}"
- );
- passwdContents = (lib.concatStringsSep "\n" (lib.attrValues (lib.mapAttrs userToPasswd users)));
-
- userToShadow = k: { ... }: "${k}:!:1::::::";
- shadowContents = (lib.concatStringsSep "\n" (lib.attrValues (lib.mapAttrs userToShadow users)));
-
- # Map groups to members
- # {
- # group = [ "user1" "user2" ];
- # }
- groupMemberMap = (
- let
- # Create a flat list of user/group mappings
- mappings = (
- builtins.foldl' (
- acc: user:
- let
- groups = users.${user}.groups or [ ];
- in
- acc ++ map (group: { inherit user group; }) groups
- ) [ ] (lib.attrNames users)
- );
- in
- (builtins.foldl' (
- acc: v: acc // { ${v.group} = acc.${v.group} or [ ] ++ [ v.user ]; }
- ) { } mappings)
- );
-
- groupToGroup =
- k:
- { gid }:
- let
- members = groupMemberMap.${k} or [ ];
- in
- "${k}:x:${toString gid}:${lib.concatStringsSep "," members}";
- groupContents = (lib.concatStringsSep "\n" (lib.attrValues (lib.mapAttrs groupToGroup groups)));
-
- defaultNixConf = {
- sandbox = "false";
- build-users-group = "nixbld";
- trusted-public-keys = [ "cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=" ];
- };
-
- nixConfContents =
- (lib.concatStringsSep "\n" (
- lib.mapAttrsFlatten (
- n: v:
- let
- vStr = if builtins.isList v then lib.concatStringsSep " " v else v;
- in
- "${n} = ${vStr}"
- ) (defaultNixConf // nixConf)
- ))
- + "\n";
-
- baseSystem =
- let
- nixpkgs = pkgs.path;
- channel = pkgs.runCommand "channel-nixos" { inherit bundleNixpkgs; } ''
- mkdir $out
- if [ "$bundleNixpkgs" ]; then
- ln -s ${nixpkgs} $out/nixpkgs
- echo "[]" > $out/manifest.nix
- fi
- '';
- rootEnv = pkgs.buildPackages.buildEnv {
- name = "root-profile-env";
- paths = defaultPkgs;
- };
- manifest = pkgs.buildPackages.runCommand "manifest.nix" { } ''
- cat > $out < $out/etc/passwd
- echo "" >> $out/etc/passwd
-
- cat $groupContentsPath > $out/etc/group
- echo "" >> $out/etc/group
-
- cat $shadowContentsPath > $out/etc/shadow
- echo "" >> $out/etc/shadow
-
- mkdir -p $out/usr
- ln -s /nix/var/nix/profiles/share $out/usr/
-
- mkdir -p $out/nix/var/nix/gcroots
-
- mkdir $out/tmp
-
- mkdir -p $out/var/tmp
-
- mkdir -p $out/etc/nix
- cat $nixConfContentsPath > $out/etc/nix/nix.conf
-
- mkdir -p $out/root
- mkdir -p $out/nix/var/nix/profiles/per-user/root
-
- ln -s ${profile} $out/nix/var/nix/profiles/default-1-link
- ln -s $out/nix/var/nix/profiles/default-1-link $out/nix/var/nix/profiles/default
- ln -s /nix/var/nix/profiles/default $out/root/.nix-profile
-
- ln -s ${channel} $out/nix/var/nix/profiles/per-user/root/channels-1-link
- ln -s $out/nix/var/nix/profiles/per-user/root/channels-1-link $out/nix/var/nix/profiles/per-user/root/channels
-
- mkdir -p $out/root/.nix-defexpr
- ln -s $out/nix/var/nix/profiles/per-user/root/channels $out/root/.nix-defexpr/channels
- echo "${channelURL} ${channelName}" > $out/root/.nix-channels
-
- mkdir -p $out/bin $out/usr/bin
- ln -s ${pkgs.coreutils}/bin/env $out/usr/bin/env
- ln -s ${pkgs.bashInteractive}/bin/bash $out/bin/sh
-
- ''
- + (lib.optionalString (flake-registry-path != null) ''
- nixCacheDir="/root/.cache/nix"
- mkdir -p $out$nixCacheDir
- globalFlakeRegistryPath="$nixCacheDir/flake-registry.json"
- ln -s ${flake-registry-path} $out$globalFlakeRegistryPath
- mkdir -p $out/nix/var/nix/gcroots/auto
- rootName=$(${pkgs.nix}/bin/nix --extra-experimental-features nix-command hash file --type sha1 --base32 <(echo -n $globalFlakeRegistryPath))
- ln -s $globalFlakeRegistryPath $out/nix/var/nix/gcroots/auto/$rootName
- '')
- );
-in
-pkgs.dockerTools.buildLayeredImageWithNixDb {
-
- inherit name tag maxLayers;
-
- contents = [ baseSystem ];
-
- extraCommands = ''
- rm -rf nix-support
- ln -s /nix/var/nix/profiles nix/var/nix/gcroots/profiles
- '';
- fakeRootCommands = ''
- chmod 1777 tmp
- chmod 1777 var/tmp
- '';
-
- config = {
- Cmd = [ "/root/.nix-profile/bin/bash" ];
- Env = [
- "USER=root"
- "PATH=${
- lib.concatStringsSep ":" [
- "/root/.nix-profile/bin"
- "/nix/var/nix/profiles/default/bin"
- "/nix/var/nix/profiles/default/sbin"
- ]
- }"
- "MANPATH=${
- lib.concatStringsSep ":" [
- "/root/.nix-profile/share/man"
- "/nix/var/nix/profiles/default/share/man"
- ]
- }"
- "SSL_CERT_FILE=/nix/var/nix/profiles/default/etc/ssl/certs/ca-bundle.crt"
- "GIT_SSL_CAINFO=/nix/var/nix/profiles/default/etc/ssl/certs/ca-bundle.crt"
- "NIX_SSL_CERT_FILE=/nix/var/nix/profiles/default/etc/ssl/certs/ca-bundle.crt"
- "NIX_PATH=/nix/var/nix/profiles/per-user/root/channels:/root/.nix-defexpr/channels"
- ];
- };
-}
diff --git a/flake.lock b/flake.lock
deleted file mode 100644
index 8e59b2942..000000000
--- a/flake.lock
+++ /dev/null
@@ -1,78 +0,0 @@
-{
- "nodes": {
- "flake-compat": {
- "flake": false,
- "locked": {
- "lastModified": 1696426674,
- "narHash": "sha256-kvjfFW7WAETZlt09AgDn1MrtKzP7t90Vf7vypd3OL1U=",
- "owner": "edolstra",
- "repo": "flake-compat",
- "rev": "0f9255e01c2351cc7d116c072cb317785dd33b33",
- "type": "github"
- },
- "original": {
- "owner": "edolstra",
- "repo": "flake-compat",
- "type": "github"
- }
- },
- "nixpkgs": {
- "locked": {
- "lastModified": 1715123187,
- "narHash": "sha256-0czuu757t53lK6uWeo1a5/jJbCd9t4sOtLDFpts60DM=",
- "owner": "NixOS",
- "repo": "nixpkgs",
- "rev": "0c592f9a288bdf764b6f24c757277c0e49757a46",
- "type": "github"
- },
- "original": {
- "owner": "NixOS",
- "ref": "nixos-23.11-small",
- "repo": "nixpkgs",
- "type": "github"
- }
- },
- "nixpkgs-regression": {
- "locked": {
- "lastModified": 1643052045,
- "narHash": "sha256-uGJ0VXIhWKGXxkeNnq4TvV3CIOkUJ3PAoLZ3HMzNVMw=",
- "owner": "NixOS",
- "repo": "nixpkgs",
- "rev": "215d4d0fd80ca5163643b03a33fde804a29cc1e2",
- "type": "github"
- },
- "original": {
- "owner": "NixOS",
- "repo": "nixpkgs",
- "rev": "215d4d0fd80ca5163643b03a33fde804a29cc1e2",
- "type": "github"
- }
- },
- "pre-commit-hooks": {
- "flake": false,
- "locked": {
- "lastModified": 1712055707,
- "narHash": "sha256-4XLvuSIDZJGS17xEwSrNuJLL7UjDYKGJSbK1WWX2AK8=",
- "owner": "cachix",
- "repo": "git-hooks.nix",
- "rev": "e35aed5fda3cc79f88ed7f1795021e559582093a",
- "type": "github"
- },
- "original": {
- "owner": "cachix",
- "repo": "git-hooks.nix",
- "type": "github"
- }
- },
- "root": {
- "inputs": {
- "flake-compat": "flake-compat",
- "nixpkgs": "nixpkgs",
- "nixpkgs-regression": "nixpkgs-regression",
- "pre-commit-hooks": "pre-commit-hooks"
- }
- }
- },
- "root": "root",
- "version": 7
-}
diff --git a/flake.nix b/flake.nix
deleted file mode 100644
index 14ee8e1ad..000000000
--- a/flake.nix
+++ /dev/null
@@ -1,402 +0,0 @@
-{
- description = "The purely functional package manager";
-
- inputs = {
- nixpkgs.url = "github:NixOS/nixpkgs/nixos-23.11-small";
- nixpkgs-regression.url = "github:NixOS/nixpkgs/215d4d0fd80ca5163643b03a33fde804a29cc1e2";
- pre-commit-hooks = {
- url = "github:cachix/git-hooks.nix";
- flake = false;
- };
- flake-compat = {
- url = "github:edolstra/flake-compat";
- flake = false;
- };
- };
-
- outputs =
- {
- self,
- nixpkgs,
- nixpkgs-regression,
- pre-commit-hooks,
- flake-compat,
- }:
-
- let
- inherit (nixpkgs) lib;
-
- # This notice gets echoed as a dev shell hook, and can be turned off with
- # `touch .nocontribmsg`
- sgr = ''['';
- freezePage = "https://wiki.lix.systems/books/lix-contributors/page/freezes-and-recommended-contributions";
- codebaseOverview = "https://wiki.lix.systems/books/lix-contributors/page/codebase-overview";
- contribNotice = builtins.toFile "lix-contrib-notice" ''
- Hey there!
-
- If you're thinking of working on Lix, please consider talking to us about it!
- You should be aware that we are ${sgr}1mnot${sgr}0m accepting major features without some conditions,
- and we highly recommend looking at our freeze status page on the wiki:
- ${sgr}32m${freezePage}${sgr}0m
-
- We also have an overview of the codebase at
- ${sgr}32m${codebaseOverview}${sgr}0m,
- and other helpful information on the wiki.
-
- But above all else, ${sgr}1mwe want to hear from you!${sgr}0m
- We can help you figure out where in the codebase to look for whatever you want to do,
- and we'd like to work together with all contributors as much as possible.
- Lix is a collaborative project :)
-
- You can open an issue at https://git.lix.systems/lix-project/lix/issues
- or chat with us on Matrix: #space:lix.systems.
-
- (Run `touch .nocontribmsg` to hide this message.)
- '';
-
- officialRelease = false;
-
- # Set to true to build the release notes for the next release.
- buildUnreleasedNotes = true;
-
- version = lib.fileContents ./.version + versionSuffix;
- versionSuffix =
- if officialRelease then
- ""
- else
- "pre${
- builtins.substring 0 8 (self.lastModifiedDate or self.lastModified or "19700101")
- }_${self.shortRev or "dirty"}";
-
- linux32BitSystems = [ "i686-linux" ];
- linux64BitSystems = [
- "x86_64-linux"
- "aarch64-linux"
- ];
- linuxSystems = linux32BitSystems ++ linux64BitSystems;
- darwinSystems = [
- "x86_64-darwin"
- "aarch64-darwin"
- ];
- systems = linuxSystems ++ darwinSystems;
-
- crossSystems = [
- "armv6l-linux"
- "armv7l-linux"
- # FIXME: doesn't evaluate, plausibly fixed in >=24.05, so recheck when
- # we update to 24.05
- # "x86_64-freebsd13"
- "x86_64-netbsd"
- ];
-
- stdenvs = [
- "gccStdenv"
- "clangStdenv"
- "stdenv"
- "libcxxStdenv"
- "ccacheStdenv"
- ];
-
- forAllSystems = lib.genAttrs systems;
- # Same as forAllSystems, but removes nulls, in case something is broken
- # on that system.
- forAvailableSystems =
- f: lib.filterAttrs (name: value: value != null && value != { }) (forAllSystems f);
-
- forAllCrossSystems = lib.genAttrs crossSystems;
-
- forAllStdenvs =
- f:
- lib.listToAttrs (
- map (stdenvName: {
- name = "${stdenvName}Packages";
- value = f stdenvName;
- }) stdenvs
- );
-
- # Memoize nixpkgs for different platforms for efficiency.
- nixpkgsFor = forAllSystems (
- system:
- let
- make-pkgs =
- crossSystem: stdenv:
- import nixpkgs {
- localSystem = {
- inherit system;
- };
- crossSystem =
- if crossSystem == null then
- null
- else
- {
- system = crossSystem;
- }
- // lib.optionalAttrs (crossSystem == "x86_64-freebsd13") { useLLVM = true; };
- overlays = [
- (overlayFor (p: p.${stdenv}))
- (final: prev: { nixfmt = final.callPackage ./nix-support/nixfmt.nix { }; })
- ];
-
- config.permittedInsecurePackages = [ "nix-2.13.6" ];
- };
- stdenvs = forAllStdenvs (make-pkgs null);
- native = stdenvs.stdenvPackages;
- in
- {
- inherit stdenvs native;
- static = native.pkgsStatic;
- cross = forAllCrossSystems (crossSystem: make-pkgs crossSystem "stdenv");
- }
- );
-
- binaryTarball =
- nix: pkgs: pkgs.callPackage ./nix-support/binary-tarball.nix { inherit nix version; };
-
- overlayFor =
- getStdenv: final: prev:
- let
- currentStdenv = getStdenv final;
- in
- {
- nixStable = prev.nix;
-
- # Forward from the previous stage as we don’t want it to pick the lowdown override
- nixUnstable = prev.nixUnstable;
-
- check-headers = final.buildPackages.callPackage ./maintainers/check-headers.nix { };
- clangbuildanalyzer = final.buildPackages.callPackage ./misc/clangbuildanalyzer.nix { };
-
- default-busybox-sandbox-shell = final.busybox.override {
- useMusl = true;
- enableStatic = true;
- enableMinimal = true;
- extraConfig = ''
- CONFIG_FEATURE_FANCY_ECHO y
- CONFIG_FEATURE_SH_MATH y
- CONFIG_FEATURE_SH_MATH_64 y
-
- CONFIG_ASH y
- CONFIG_ASH_OPTIMIZE_FOR_SIZE y
-
- CONFIG_ASH_ALIAS y
- CONFIG_ASH_BASH_COMPAT y
- CONFIG_ASH_CMDCMD y
- CONFIG_ASH_ECHO y
- CONFIG_ASH_GETOPTS y
- CONFIG_ASH_INTERNAL_GLOB y
- CONFIG_ASH_JOB_CONTROL y
- CONFIG_ASH_PRINTF y
- CONFIG_ASH_TEST y
- '';
- };
-
- nix = final.callPackage ./package.nix {
- inherit versionSuffix;
- stdenv = currentStdenv;
- busybox-sandbox-shell = final.busybox-sandbox-shell or final.default-busybox-sandbox-shell;
- };
-
- # Export the patched version of boehmgc that Lix uses into the overlay
- # for consumers of this flake.
- boehmgc-nix = final.nix.boehmgc-nix;
- # And same thing for our build-release-notes package.
- build-release-notes = final.nix.build-release-notes;
- };
- in
- {
- # A Nixpkgs overlay that overrides the 'nix' and
- # 'nix.perl-bindings' packages.
- overlays.default = overlayFor (p: p.stdenv);
-
- hydraJobs = {
-
- # Binary package for various platforms.
- build = forAllSystems (system: self.packages.${system}.nix);
-
- rl-next = forAllSystems (
- system:
- let
- rl-next-check =
- name: dir:
- let
- pkgs = nixpkgsFor.${system}.native;
- in
- pkgs.buildPackages.runCommand "test-${name}-release-notes" { } ''
- LANG=C.UTF-8 ${lib.getExe pkgs.build-release-notes} --change-authors ${./doc/manual/change-authors.yml} ${dir} >$out
- '';
- in
- {
- user = rl-next-check "rl-next" ./doc/manual/rl-next;
- dev = rl-next-check "rl-next-dev" ./doc/manual/rl-next-dev;
- }
- );
-
- # Perl bindings for various platforms.
- perlBindings = forAllSystems (system: nixpkgsFor.${system}.native.nix.perl-bindings);
-
- # Binary tarball for various platforms, containing a Nix store
- # with the closure of 'nix' package.
- binaryTarball = forAllSystems (
- system: binaryTarball nixpkgsFor.${system}.native.nix nixpkgsFor.${system}.native
- );
-
- # docker image with Nix inside
- dockerImage = lib.genAttrs linux64BitSystems (system: self.packages.${system}.dockerImage);
-
- # API docs for Nix's unstable internal C++ interfaces.
- internal-api-docs =
- let
- nixpkgs = nixpkgsFor.x86_64-linux.native;
- inherit (nixpkgs) pkgs;
-
- nix = pkgs.callPackage ./package.nix {
- inherit versionSuffix officialRelease buildUnreleasedNotes;
- inherit (pkgs) build-release-notes;
- internalApiDocs = true;
- busybox-sandbox-shell = pkgs.busybox-sandbox-shell;
- };
- in
- nix.overrideAttrs (prev: {
- # This Hydra job is just for the internal API docs.
- # We don't need the build artifacts here.
- dontBuild = true;
- doCheck = false;
- doInstallCheck = false;
- });
-
- # System tests.
- tests = import ./tests/nixos { inherit lib nixpkgs nixpkgsFor; } // {
-
- # Make sure that nix-env still produces the exact same result
- # on a particular version of Nixpkgs.
- evalNixpkgs =
- with nixpkgsFor.x86_64-linux.native;
- runCommand "eval-nixos" { buildInputs = [ nix ]; } ''
- type -p nix-env
- # Note: we're filtering out nixos-install-tools because https://github.com/NixOS/nixpkgs/pull/153594#issuecomment-1020530593.
- time nix-env --store dummy:// -f ${nixpkgs-regression} -qaP --drv-path | sort | grep -v nixos-install-tools > packages
- [[ $(sha1sum < packages | cut -c1-40) = 402242fca90874112b34718b8199d844e8b03d12 ]]
- mkdir $out
- '';
-
- nixpkgsLibTests = forAllSystems (
- system:
- import (nixpkgs + "/lib/tests/release.nix") {
- pkgs = nixpkgsFor.${system}.native;
- nixVersions = [ self.packages.${system}.nix ];
- }
- );
- };
-
- pre-commit = forAvailableSystems (
- system:
- let
- pkgs = nixpkgsFor.${system}.native;
- pre-commit-check = import ./misc/pre-commit.nix { inherit self pkgs pre-commit-hooks; };
- # dotnet-sdk_6, a nativeBuildInputs of pre-commit, is broken on i686-linux.
- available = lib.meta.availableOn { inherit system; } pkgs.dotnet-sdk_6;
- in
- lib.optionalAttrs available pre-commit-check
- );
- };
-
- # NOTE *do not* add fresh derivations to checks, always add them to
- # hydraJobs first (so CI will pick them up) and only link them here
- checks = forAvailableSystems (
- system:
- {
- binaryTarball = self.hydraJobs.binaryTarball.${system};
- perlBindings = self.hydraJobs.perlBindings.${system};
- nixpkgsLibTests = self.hydraJobs.tests.nixpkgsLibTests.${system};
- rl-next = self.hydraJobs.rl-next.${system}.user;
- rl-next-dev = self.hydraJobs.rl-next.${system}.dev;
- # Will be empty attr set on i686-linux, and filtered out by forAvailableSystems.
- pre-commit = self.hydraJobs.pre-commit.${system};
- }
- // (lib.optionalAttrs (builtins.elem system linux64BitSystems)) {
- dockerImage = self.hydraJobs.dockerImage.${system};
- }
- );
-
- packages = forAllSystems (
- system:
- rec {
- inherit (nixpkgsFor.${system}.native) nix;
- default = nix;
- }
- // (
- lib.optionalAttrs (builtins.elem system linux64BitSystems) {
- nix-static = nixpkgsFor.${system}.static.nix;
- dockerImage =
- let
- pkgs = nixpkgsFor.${system}.native;
- image = import ./docker.nix {
- inherit pkgs;
- tag = version;
- };
- in
- pkgs.runCommand "docker-image-tarball-${version}"
- { meta.description = "Docker image with Nix for ${system}"; }
- ''
- mkdir -p $out/nix-support
- image=$out/image.tar.gz
- ln -s ${image} $image
- echo "file binary-dist $image" >> $out/nix-support/hydra-build-products
- '';
- }
- // builtins.listToAttrs (
- map (crossSystem: {
- name = "nix-${crossSystem}";
- value = nixpkgsFor.${system}.cross.${crossSystem}.nix;
- }) crossSystems
- )
- // builtins.listToAttrs (
- map (stdenvName: {
- name = "nix-${stdenvName}";
- value = nixpkgsFor.${system}.stdenvs."${stdenvName}Packages".nix;
- }) stdenvs
- )
- )
- );
-
- devShells =
- let
- makeShell =
- pkgs: stdenv:
- let
- nix = pkgs.callPackage ./package.nix {
- inherit stdenv versionSuffix;
- busybox-sandbox-shell = pkgs.busybox-sandbox-shell or pkgs.default-busybox-sandbox;
- internalApiDocs = true;
- };
- pre-commit = self.hydraJobs.pre-commit.${pkgs.system} or { };
- in
- pkgs.callPackage nix.mkDevShell {
- pre-commit-checks = pre-commit;
- inherit contribNotice;
- };
- in
- forAllSystems (
- system:
- let
- makeShells =
- prefix: pkgs:
- lib.mapAttrs' (k: v: lib.nameValuePair "${prefix}-${k}" v) (
- forAllStdenvs (stdenvName: makeShell pkgs pkgs.${stdenvName})
- );
- in
- (makeShells "native" nixpkgsFor.${system}.native)
- // (makeShells "static" nixpkgsFor.${system}.static)
- // (forAllCrossSystems (
- crossSystem:
- let
- pkgs = nixpkgsFor.${system}.cross.${crossSystem};
- in
- makeShell pkgs pkgs.stdenv
- ))
- // {
- default = self.devShells.${system}.native-stdenvPackages;
- }
- );
- };
-}
diff --git a/justfile b/justfile
deleted file mode 100644
index 83743ec42..000000000
--- a/justfile
+++ /dev/null
@@ -1,27 +0,0 @@
-# https://just.systems/man/en/
-
-# List all available targets
-list:
- just --list
-
-# Clean build artifacts
-clean:
- rm -rf build
-
-# Prepare meson for building
-setup:
- meson setup build --prefix="$PWD/outputs/out"
-
-# Build lix
-build *OPTIONS:
- meson compile -C build {{ OPTIONS }}
-
-alias compile := build
-
-# Install lix for local development
-install *OPTIONS: (build OPTIONS)
- meson install -C build
-
-# Run tests
-test *OPTIONS:
- meson test -C build --print-errorlogs --quiet {{ OPTIONS }}
diff --git a/lix-doc/.gitignore b/lix-doc/.gitignore
deleted file mode 100644
index c0d245929..000000000
--- a/lix-doc/.gitignore
+++ /dev/null
@@ -1,6 +0,0 @@
-# SPDX-FileCopyrightText: 2024 Jade Lovelace
-#
-# SPDX-License-Identifier: BSD-2-Clause OR MIT
-
-/target
-result
diff --git a/lix-doc/Cargo.lock b/lix-doc/Cargo.lock
deleted file mode 100644
index d5028edfe..000000000
--- a/lix-doc/Cargo.lock
+++ /dev/null
@@ -1,161 +0,0 @@
-# This file is automatically @generated by Cargo.
-# It is not intended for manual editing.
-version = 3
-
-[[package]]
-name = "autocfg"
-version = "1.1.0"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
-
-[[package]]
-name = "cbitset"
-version = "0.2.0"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "29b6ad25ae296159fb0da12b970b2fe179b234584d7cd294c891e2bbb284466b"
-dependencies = [
- "num-traits",
-]
-
-[[package]]
-name = "dissimilar"
-version = "1.0.7"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "86e3bdc80eee6e16b2b6b0f87fbc98c04bee3455e35174c0de1a125d0688c632"
-
-[[package]]
-name = "expect-test"
-version = "1.4.1"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "30d9eafeadd538e68fb28016364c9732d78e420b9ff8853fa5e4058861e9f8d3"
-dependencies = [
- "dissimilar",
- "once_cell",
-]
-
-[[package]]
-name = "lix-doc"
-version = "0.0.1"
-dependencies = [
- "expect-test",
- "rnix",
-]
-
-[[package]]
-name = "num-traits"
-version = "0.2.18"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "da0df0e5185db44f69b44f26786fe401b6c293d1907744beaa7fa62b2e5a517a"
-dependencies = [
- "autocfg",
-]
-
-[[package]]
-name = "once_cell"
-version = "1.19.0"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "3fdb12b2476b595f9358c5161aa467c2438859caa136dec86c26fdd2efe17b92"
-
-[[package]]
-name = "proc-macro2"
-version = "1.0.79"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "e835ff2298f5721608eb1a980ecaee1aef2c132bf95ecc026a11b7bf3c01c02e"
-dependencies = [
- "unicode-ident",
-]
-
-[[package]]
-name = "quote"
-version = "1.0.35"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "291ec9ab5efd934aaf503a6466c5d5251535d108ee747472c3977cc5acc868ef"
-dependencies = [
- "proc-macro2",
-]
-
-[[package]]
-name = "rnix"
-version = "0.8.1"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "0a9b645f0edba447dbfc6473dd22999f46a1d00ab39e777a2713a1cf34a1597b"
-dependencies = [
- "cbitset",
- "rowan",
-]
-
-[[package]]
-name = "rowan"
-version = "0.9.1"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "1ea7cadf87a9d8432e85cb4eb86bd2e765ace60c24ef86e79084dcae5d1c5a19"
-dependencies = [
- "rustc-hash",
- "smol_str",
- "text_unit",
- "thin-dst",
-]
-
-[[package]]
-name = "rustc-hash"
-version = "1.1.0"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
-
-[[package]]
-name = "serde"
-version = "1.0.197"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "3fb1c873e1b9b056a4dc4c0c198b24c3ffa059243875552b2bd0933b1aee4ce2"
-dependencies = [
- "serde_derive",
-]
-
-[[package]]
-name = "serde_derive"
-version = "1.0.197"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "7eb0b34b42edc17f6b7cac84a52a1c5f0e1bb2227e997ca9011ea3dd34e8610b"
-dependencies = [
- "proc-macro2",
- "quote",
- "syn",
-]
-
-[[package]]
-name = "smol_str"
-version = "0.1.24"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "fad6c857cbab2627dcf01ec85a623ca4e7dcb5691cbaa3d7fb7653671f0d09c9"
-dependencies = [
- "serde",
-]
-
-[[package]]
-name = "syn"
-version = "2.0.53"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "7383cd0e49fff4b6b90ca5670bfd3e9d6a733b3f90c686605aa7eec8c4996032"
-dependencies = [
- "proc-macro2",
- "quote",
- "unicode-ident",
-]
-
-[[package]]
-name = "text_unit"
-version = "0.1.10"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "20431e104bfecc1a40872578dbc390e10290a0e9c35fffe3ce6f73c15a9dbfc2"
-
-[[package]]
-name = "thin-dst"
-version = "1.1.0"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "db3c46be180f1af9673ebb27bc1235396f61ef6965b3fe0dbb2e624deb604f0e"
-
-[[package]]
-name = "unicode-ident"
-version = "1.0.12"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "3354b9ac3fae1ff6755cb6db53683adb661634f67557942dea4facebec0fee4b"
diff --git a/lix-doc/Cargo.toml b/lix-doc/Cargo.toml
deleted file mode 100644
index df4eed932..000000000
--- a/lix-doc/Cargo.toml
+++ /dev/null
@@ -1,18 +0,0 @@
-[package]
-description = "Nix function documentation tool, stripped down into a library"
-edition = "2018"
-name = "lix-doc"
-version = "0.0.1"
-license = "BSD-2-Clause OR MIT"
-# upstream details
-homepage = "https://github.com/lf-/nix-doc"
-repository = "https://github.com/lf-/nix-doc"
-
-[lib]
-crate_type = ["staticlib"]
-
-[dependencies]
-rnix = "0.8.0"
-
-[dev-dependencies]
-expect-test = "1.1.0"
diff --git a/lix-doc/README.md b/lix-doc/README.md
deleted file mode 100644
index 26049ebd7..000000000
--- a/lix-doc/README.md
+++ /dev/null
@@ -1,6 +0,0 @@
-# lix-doc
-
-This is a stripped down fork of `nix-doc`, used for `:doc` in `nix repl` in
-Lix. It will be replaced in the future with proper support when we get the new
-parser working, but it exists today as a low-risk implementation of an
-important usability feature.
diff --git a/lix-doc/package.nix b/lix-doc/package.nix
deleted file mode 100644
index d3896e726..000000000
--- a/lix-doc/package.nix
+++ /dev/null
@@ -1,8 +0,0 @@
-{ rustPlatform, lib }:
-
-rustPlatform.buildRustPackage {
- name = "lix-doc";
-
- cargoLock.lockFile = ./Cargo.lock;
- src = lib.cleanSource ./.;
-}
diff --git a/lix-doc/src/lib.rs b/lix-doc/src/lib.rs
deleted file mode 100644
index 27fe5c9b5..000000000
--- a/lix-doc/src/lib.rs
+++ /dev/null
@@ -1,338 +0,0 @@
-// SPDX-FileCopyrightText: 2024 Jade Lovelace
-//
-// SPDX-License-Identifier: BSD-2-Clause OR MIT
-
-//! library components of nix-doc
-pub mod pprint;
-
-use crate::pprint::pprint_args;
-
-use rnix::types::{Lambda, TypedNode};
-use rnix::SyntaxKind::*;
-use rnix::{NodeOrToken, SyntaxNode, TextUnit, WalkEvent};
-
-use std::ffi::{CStr, CString};
-use std::fs;
-use std::iter;
-use std::os::raw::c_char;
-use std::panic;
-
-use std::ptr;
-
-use std::{fmt::Display, str};
-
-pub type Result = std::result::Result>;
-
-const DOC_INDENT: usize = 3;
-
-struct SearchResult {
- /// Name of the function
- identifier: String,
-
- /// Dedented documentation comments
- doc: String,
-
- /// Parameter block for the function
- param_block: String,
-}
-
-fn find_pos(file: &str, line: usize, col: usize) -> usize {
- let mut lines = 1;
- let mut line_start = 0;
- let mut it = file.chars().enumerate().peekable();
- while let Some((count, ch)) = it.next() {
- if ch == '\n' || ch == '\r' {
- lines += 1;
- let addend = if ch == '\r' && it.peek().map(|x| x.1) == Some('\n') {
- it.next();
- 1
- } else {
- 0
- };
- line_start = count + addend;
- }
-
- let col_diff = ((count as i32) - (line_start as i32)).abs() as usize;
- if lines == line && col_diff == col {
- return count;
- }
- }
- unreachable!();
-}
-
-impl SearchResult {
- fn format(&self, filename: P, line: usize) -> String {
- format!(
- "**Synopsis:** `{}` = {}\n\n{}\n\n# {}",
- self.identifier.as_str(),
- self.param_block,
- indented(&self.doc, DOC_INDENT),
- format!("{}:{}", filename, line).as_str(),
- )
- }
-}
-
-/// Emits a string `s` indented by `indent` spaces
-fn indented(s: &str, indent: usize) -> String {
- let indent_s = iter::repeat(' ').take(indent).collect::();
- s.split('\n')
- .map(|line| indent_s.clone() + line)
- .collect::>()
- .join("\n")
-}
-
-/// Cleans up a single line, erasing prefix single line comments but preserving indentation
-fn cleanup_single_line<'a>(s: &'a str) -> &'a str {
- let mut cmt_new_start = 0;
- let mut iter = s.char_indices().peekable();
- while let Some((idx, ch)) = iter.next() {
- // peek at the next character, with an explicit '\n' as "next character" at end of line
- let (_, next_ch) = iter.peek().unwrap_or(&(0, '\n'));
-
- // if we find a character, save the byte position after it as our new string start
- if ch == '#' || (ch == '*' && next_ch.is_whitespace()) {
- cmt_new_start = idx + 1;
- break;
- }
- // if, instead, we are on a line with no starting comment characters, leave it alone as it
- // will be handled by dedent later
- if !ch.is_whitespace() {
- break;
- }
- }
- &s[cmt_new_start..]
-}
-
-/// Erases indents in comments. This is *almost* a normal dedent function, but it starts by looking
-/// at the second line if it can.
-fn dedent_comment(s: &str) -> String {
- let mut whitespaces = 0;
- let mut lines = s.lines();
- let first = lines.next();
-
- // scan for whitespace
- for line in lines.chain(first) {
- let line_whitespace = line.chars().take_while(|ch| ch.is_whitespace()).count();
-
- if line_whitespace != line.len() {
- // a non-whitespace line, perfect for taking whitespace off of
- whitespaces = line_whitespace;
- break;
- }
- }
-
- // maybe the first considered line we found was indented further, so let's look for more lines
- // that might have a shorter indent. In the case of one line, do nothing.
- for line in s.lines().skip(1) {
- let line_whitespace = line.chars().take_while(|ch| ch.is_whitespace()).count();
-
- if line_whitespace != line.len() {
- whitespaces = line_whitespace.min(whitespaces);
- }
- }
-
- // delete up to `whitespaces` whitespace characters from each line and reconstitute the string
- let mut out = String::new();
- for line in s.lines() {
- let content_begin = line.find(|ch: char| !ch.is_whitespace()).unwrap_or(0);
- out.push_str(&line[content_begin.min(whitespaces)..]);
- out.push('\n');
- }
-
- out.truncate(out.trim_end_matches('\n').len());
- out
-}
-
-/// Deletes whitespace and leading comment characters
-///
-/// Oversight we are choosing to ignore: if you put # characters at the beginning of lines in a
-/// multiline comment, they will be deleted.
-fn cleanup_comments, I: DoubleEndedIterator- >(comment: &mut I) -> String {
- dedent_comment(
- &comment
- .rev()
- .map(|small_comment| {
- small_comment
- .as_ref()
- // space before multiline start
- .trim_start()
- // multiline starts
- .trim_start_matches("/*")
- // trailing so we can grab multiline end
- .trim_end()
- // multiline ends
- .trim_end_matches("*/")
- // extra space that was in the multiline
- .trim()
- .split('\n')
- // erase single line comments and such
- .map(cleanup_single_line)
- .collect::
>()
- .join("\n")
- })
- .collect::>()
- .join("\n"),
- )
-}
-
-/// Get the docs for a specific function
-pub fn get_function_docs(filename: &str, line: usize, col: usize) -> Option {
- let content = fs::read(filename).ok()?;
- let decoded = str::from_utf8(&content).ok()?;
- let pos = find_pos(&decoded, line, col);
- let rowan_pos = TextUnit::from_usize(pos);
- let tree = rnix::parse(decoded);
-
- let mut lambda = None;
- for node in tree.node().preorder() {
- match node {
- WalkEvent::Enter(n) => {
- if n.text_range().start() >= rowan_pos && n.kind() == NODE_LAMBDA {
- lambda = Lambda::cast(n);
- break;
- }
- }
- WalkEvent::Leave(_) => (),
- }
- }
- let lambda = lambda?;
- let res = visit_lambda("func".to_string(), &lambda);
- Some(res.format(filename, line))
-}
-
-fn visit_lambda(name: String, lambda: &Lambda) -> SearchResult {
- // grab the arguments
- let param_block = pprint_args(&lambda);
-
- // find the doc comment
- let comment = find_comment(lambda.node().clone()).unwrap_or_else(|| "".to_string());
-
- SearchResult {
- identifier: name,
- doc: comment,
- param_block,
- }
-}
-
-fn find_comment(node: SyntaxNode) -> Option {
- let mut node = NodeOrToken::Node(node);
- let mut comments = Vec::new();
- loop {
- loop {
- if let Some(new) = node.prev_sibling_or_token() {
- node = new;
- break;
- } else {
- node = NodeOrToken::Node(node.parent()?);
- }
- }
-
- match node.kind() {
- TOKEN_COMMENT => match &node {
- NodeOrToken::Token(token) => comments.push(token.text().clone()),
- NodeOrToken::Node(_) => unreachable!(),
- },
- // This stuff is found as part of `the-fn = f: ...`
- // here: ^^^^^^^^
- NODE_KEY | TOKEN_ASSIGN => (),
- t if t.is_trivia() => (),
- _ => break,
- }
- }
- let doc = cleanup_comments(&mut comments.iter().map(|c| c.as_str()));
- Some(doc).filter(|it| !it.is_empty())
-}
-
-/// Get the docs for a function in the given file path at the given file position and return it as
-/// a C string pointer
-#[no_mangle]
-pub extern "C" fn nd_get_function_docs(
- filename: *const c_char,
- line: usize,
- col: usize,
-) -> *const c_char {
- let fname = unsafe { CStr::from_ptr(filename) };
- fname
- .to_str()
- .ok()
- .and_then(|f| {
- panic::catch_unwind(|| get_function_docs(f, line, col))
- .map_err(|e| {
- eprintln!("panic!! {:#?}", e);
- e
- })
- .ok()
- })
- .flatten()
- .and_then(|s| CString::new(s).ok())
- .map(|s| s.into_raw() as *const c_char)
- .unwrap_or(ptr::null())
-}
-
-/// Call this to free a string from nd_get_function_docs
-#[no_mangle]
-pub extern "C" fn nd_free_string(s: *const c_char) {
- unsafe {
- // cast note: this cast is turning something that was cast to const
- // back to mut
- drop(CString::from_raw(s as *mut c_char));
- }
-}
-
-#[cfg(test)]
-mod tests {
- use super::*;
-
- #[test]
- fn test_bytepos() {
- let fakefile = "abc\ndef\nghi";
- assert_eq!(find_pos(fakefile, 2, 2), 5);
- }
-
- #[test]
- fn test_bytepos_cursed() {
- let fakefile = "abc\rdef\r\nghi";
- assert_eq!(find_pos(fakefile, 2, 2), 5);
- assert_eq!(find_pos(fakefile, 3, 2), 10);
- }
-
- #[test]
- fn test_comment_stripping() {
- let ex1 = ["/* blah blah blah\n foooo baaar\n blah */"];
- assert_eq!(
- cleanup_comments(&mut ex1.iter()),
- "blah blah blah\n foooo baaar\nblah"
- );
-
- let ex2 = ["# a1", "# a2", "# aa"];
- assert_eq!(cleanup_comments(&mut ex2.iter()), "aa\n a2\na1");
- }
-
- #[test]
- fn test_dedent() {
- let ex1 = "a\n b\n c\n d";
- assert_eq!(dedent_comment(ex1), "a\nb\nc\n d");
- let ex2 = "a\nb\nc";
- assert_eq!(dedent_comment(ex2), ex2);
- let ex3 = " a\n b\n\n c";
- assert_eq!(dedent_comment(ex3), "a\nb\n\n c");
- }
-
- #[test]
- fn test_single_line_comment_stripping() {
- let ex1 = " * a";
- let ex2 = " # a";
- let ex3 = " a";
- let ex4 = " *";
- assert_eq!(cleanup_single_line(ex1), " a");
- assert_eq!(cleanup_single_line(ex2), " a");
- assert_eq!(cleanup_single_line(ex3), ex3);
- assert_eq!(cleanup_single_line(ex4), "");
- }
-
- #[test]
- fn test_single_line_retains_bold_headings() {
- let ex1 = " **Foo**:";
- assert_eq!(cleanup_single_line(ex1), ex1);
- }
-}
diff --git a/lix-doc/src/pprint.rs b/lix-doc/src/pprint.rs
deleted file mode 100644
index 7e73d2d20..000000000
--- a/lix-doc/src/pprint.rs
+++ /dev/null
@@ -1,40 +0,0 @@
-// SPDX-FileCopyrightText: 2024 Jade Lovelace
-//
-// SPDX-License-Identifier: BSD-2-Clause OR MIT
-
-use rnix::types::{Lambda, TypedNode};
-use rnix::SyntaxKind::*;
-
-/// Pretty-prints the arguments to a function
-pub fn pprint_args(lambda: &Lambda) -> String {
- // TODO: handle docs directly on NODE_IDENT args (uncommon case)
- let mut lambda = lambda.clone();
- let mut out = String::new();
- loop {
- let arg = lambda.arg().unwrap();
- match arg.kind() {
- NODE_IDENT => {
- out += &format!("*{}*", &arg.to_string());
- out.push_str(": ");
- let body = lambda.body().unwrap();
- if body.kind() == NODE_LAMBDA {
- lambda = Lambda::cast(body).unwrap();
- } else {
- break;
- }
- }
- NODE_PATTERN => {
- out += &format!("*{}*", &arg.to_string());
- out.push_str(": ");
- break;
- }
- t => {
- unreachable!("unhandled arg type {:?}", t);
- }
- }
- }
- out.push_str("...");
- out
-
- //pprint_arg(lambda.arg());
-}
diff --git a/maintainers/build-release-notes.nix b/maintainers/build-release-notes.nix
deleted file mode 100644
index 1acbe87f1..000000000
--- a/maintainers/build-release-notes.nix
+++ /dev/null
@@ -1,10 +0,0 @@
-{
- lib,
- python3,
- writeShellScriptBin,
-}:
-
-writeShellScriptBin "build-release-notes" ''
- exec ${lib.getExe (python3.withPackages (p: [ p.python-frontmatter ]))} \
- ${./build-release-notes.py} "$@"
-''
diff --git a/maintainers/build-release-notes.py b/maintainers/build-release-notes.py
deleted file mode 100644
index 45d5d6ff9..000000000
--- a/maintainers/build-release-notes.py
+++ /dev/null
@@ -1,167 +0,0 @@
-from collections import defaultdict
-import frontmatter
-import sys
-import pathlib
-import textwrap
-from typing import Any, Tuple
-import dataclasses
-import yaml
-
-GH_ROOT = "https://github.com/"
-GH_REPO_BASE = "https://github.com/NixOS/nix"
-FORGEJO_REPO_BASE = "https://git.lix.systems/lix-project/lix"
-FORGEJO_ROOT = "https://git.lix.systems/"
-GERRIT_BASE = "https://gerrit.lix.systems/c/lix/+"
-KNOWN_KEYS = ('synopsis', 'cls', 'issues', 'prs', 'significance', 'category', 'credits')
-
-SIGNIFICANCECES = {
- None: 0,
- 'significant': 10,
-}
-
-# This is just hardcoded for better validation. If you think there should be
-# more of them, feel free to add more.
-CATEGORIES = [
- 'Breaking Changes',
- 'Features',
- 'Improvements',
- 'Fixes',
- 'Packaging',
- 'Miscellany',
-]
-
-
-@dataclasses.dataclass
-class AuthorInfo:
- name: str
- github: str | None = None
- forgejo: str | None = None
- display_name: str | None = None
-
- def show_name(self) -> str:
- return self.display_name or self.name
-
- def __str__(self) -> str:
- if self.forgejo:
- return f'[{self.show_name()}]({FORGEJO_ROOT}{self.forgejo})'
- elif self.github:
- return f'[{self.show_name()}]({GH_ROOT}{self.github})'
- else:
- return self.show_name()
-
-
-class AuthorInfoDB:
- def __init__(self, author_info: dict[str, dict], throw_on_missing: bool):
- self.author_info = {name: AuthorInfo(name=name, **d) for (name, d) in author_info.items()}
- self.throw_on_missing = throw_on_missing
-
- def __getitem__(self, name) -> str:
- if name in self.author_info:
- return str(self.author_info[name])
- else:
- if self.throw_on_missing:
- raise Exception(f'Missing author info for author {name}')
- else:
- return name
-
-
-def format_link(ident: str, gh_part: str, fj_part: str) -> str:
- # FIXME: deprecate github as default
- if ident.isdigit():
- num, link, base = int(ident), f"#{ident}", f"{GH_REPO_BASE}/{gh_part}"
- elif ident.startswith("gh#"):
- num, link, base = int(ident[3:]), ident, f"{GH_REPO_BASE}/{gh_part}"
- elif ident.startswith("fj#"):
- num, link, base = int(ident[3:]), ident, f"{FORGEJO_REPO_BASE}/{fj_part}"
- else:
- raise Exception("unrecognized reference format", ident)
- return f"[{link}]({base}/{num})"
-
-def format_issue(issue: str) -> str:
- return format_link(issue, "issues", "issues")
-def format_pr(pr: str) -> str:
- return format_link(pr, "pull", "pulls")
-def format_cl(clid: int) -> str:
- return f"[cl/{clid}]({GERRIT_BASE}/{clid})"
-
-def plural_list(strs: list[str]) -> str:
- if len(strs) <= 1:
- return ''.join(strs)
- else:
- comma = ',' if len(strs) >= 3 else ''
- return '{}{} and {}'.format(', '.join(strs[:-1]), comma, strs[-1])
-
-def listify(l: list | int) -> list:
- if not isinstance(l, list):
- return [l]
- else:
- return l
-
-def do_category(author_info: AuthorInfoDB, entries: list[Tuple[pathlib.Path, Any]]):
- for p, entry in sorted(entries, key=lambda e: (-SIGNIFICANCECES[e[1].metadata.get('significance')], e[0])):
- try:
- header = entry.metadata['synopsis']
- links = []
- links += [format_issue(str(s)) for s in listify(entry.metadata.get('issues', []))]
- links += [format_pr(str(s)) for s in listify(entry.metadata.get('prs', []))]
- links += [format_cl(cl) for cl in listify(entry.metadata.get('cls', []))]
- if links != []:
- header += " " + " ".join(links)
- if header:
- print(f"- {header}")
- print()
- print(textwrap.indent(entry.content, ' '))
- if credits := listify(entry.metadata.get('credits', [])):
- print()
- print(textwrap.indent('Many thanks to {} for this.'.format(plural_list(list(author_info[c] for c in credits))), ' '))
- except Exception as e:
- e.add_note(f"in {p}")
- raise
-
-
-def run_on_dir(author_info: AuthorInfoDB, d):
- d = pathlib.Path(d)
- if not d.is_dir():
- raise ValueError(f'provided path {d} is not a directory')
- paths = pathlib.Path(d).glob('*.md')
- entries = defaultdict(list)
- for p in paths:
- try:
- e = frontmatter.load(p)
- if 'synopsis' not in e.metadata:
- raise Exception('missing synopsis')
- unknownKeys = set(e.metadata.keys()) - set(KNOWN_KEYS)
- if unknownKeys:
- raise Exception('unknown keys', unknownKeys)
- category = e.metadata.get('category', 'Miscellany')
- if category not in CATEGORIES:
- raise Exception('unknown category', category)
- entries[category].append((p, e))
- except Exception as e:
- e.add_note(f"in {p}")
- raise
-
- for category in CATEGORIES:
- if entries[category]:
- print('\n#', category)
- do_category(author_info, entries[category])
-
-def main():
- import argparse
-
- ap = argparse.ArgumentParser()
- ap.add_argument('--change-authors', help='File name of the change authors metadata YAML file', type=argparse.FileType('r'))
- ap.add_argument('dirs', help='Directories to run on', nargs='+')
-
- args = ap.parse_args()
-
- author_info = AuthorInfoDB(yaml.safe_load(args.change_authors), throw_on_missing=True) \
- if args.change_authors \
- else AuthorInfoDB({}, throw_on_missing=False)
-
- for d in args.dirs:
- run_on_dir(author_info, d)
-
-
-if __name__ == '__main__':
- main()
diff --git a/maintainers/buildtime_report.sh b/maintainers/buildtime_report.sh
deleted file mode 100755
index 54ce75eb5..000000000
--- a/maintainers/buildtime_report.sh
+++ /dev/null
@@ -1,20 +0,0 @@
-#!/bin/sh
-
-# Generates a report of build time based on a meson build using -ftime-trace in
-# Clang.
-if [ $# -lt 1 ]; then
- echo "usage: $0 BUILD-DIR [filename]" >&2
- exit 1
-fi
-
-scriptdir=$(cd "$(dirname -- "$0")" || exit ; pwd -P)
-filename=${2:-$scriptdir/../buildtime.bin}
-
-if [ "$(meson introspect "$1" --buildoptions | jq -r '.[] | select(.name == "profile-build") | .value')" != enabled ]; then
- echo 'This build was not done with profile-build enabled, so cannot generate a report' >&2
- # shellcheck disable=SC2016
- echo 'Run `meson configure build -Dprofile-build=enabled` then rebuild, first' >&2
- exit 1
-fi
-
-ClangBuildAnalyzer --all "$1" "$filename" && ClangBuildAnalyzer --analyze "$filename"
diff --git a/maintainers/check-headers.nix b/maintainers/check-headers.nix
deleted file mode 100644
index a184bb401..000000000
--- a/maintainers/check-headers.nix
+++ /dev/null
@@ -1,7 +0,0 @@
-{ writeShellApplication, gnugrep }:
-writeShellApplication {
- name = "check-headers";
-
- runtimeInputs = [ gnugrep ];
- text = builtins.readFile ./check-headers.sh;
-}
diff --git a/maintainers/check-headers.sh b/maintainers/check-headers.sh
deleted file mode 100755
index 2b4dd248a..000000000
--- a/maintainers/check-headers.sh
+++ /dev/null
@@ -1,47 +0,0 @@
-#!/usr/bin/env bash
-
-set -eu
-
-# n.b. this might be printed multiple times if any violating header files are
-# in different parallelism groups inside pre-commit. We cannot do anything about
-# this.
-explanation=$(cat <<'EOF'
-
-We found some header files that don't conform to the style guide.
-
-The Lix style guide requests that header files:
-- Begin with `#pragma once` so they only get parsed once
-- Contain a doxygen comment (`/**` or `///`) containing `@file`, for
- example, `///@file`, which will make doxygen generate docs for them.
-
- When adding that, consider also adding a `@brief` with a sentence
- explaining what the header is for.
-
-For more details: https://wiki.lix.systems/link/3#bkmrk-header-files
-EOF
-)
-
-check_file() {
- grep -q "$1" "$2" || (echo "Missing pattern $1 in file $2" >&2; return 1)
-}
-
-patterns=(
- # makes a file get included only once even if it is included multiple times
- '^#pragma once$'
- # as used in ///@file, makes the file appear to doxygen
- '@file'
-)
-fail=0
-
-for pattern in "${patterns[@]}"; do
- for file in "$@"; do
- check_file "$pattern" "$file" || fail=1
- done
-done
-
-if [[ $fail != 0 ]]; then
- echo "$explanation" >&2
- exit 1
-else
- echo OK
-fi
diff --git a/maintainers/issue_import.py b/maintainers/issue_import.py
deleted file mode 100644
index ea226b7b8..000000000
--- a/maintainers/issue_import.py
+++ /dev/null
@@ -1,148 +0,0 @@
-import requests
-import textwrap
-import dataclasses
-import logging
-import re
-import os
-
-API_BASE = 'https://git.lix.systems/api/v1'
-API_KEY = os.environ['FORGEJO_API_KEY']
-
-log = logging.getLogger(__name__)
-log.setLevel(logging.INFO)
-
-fmt = logging.Formatter('{asctime} {levelname} {name}: {message}',
- datefmt='%b %d %H:%M:%S',
- style='{')
-
-if not any(isinstance(h, logging.StreamHandler) for h in log.handlers):
- hand = logging.StreamHandler()
- hand.setFormatter(fmt)
- log.addHandler(hand)
-
-# These are erring in the direction of re-triage, rather than necessarily
-# mapping all metadata of the issue
-LABEL_MAPPING = {
- 'lix-import': 153, # 'imported',
- 'contributor-experience': 148, # 'devx',
- 'bug': 150, # 'bug',
- 'UX': 149, # 'ux',
- 'error-messages': 149, # 'ux',
- 'lix-stability': 146, # 'stability',
- 'performance': 147, # 'performance',
- 'tests': 121, # 'tests',
-}
-
-def api(method, endpoint: str, resp_json=True, **kwargs):
- log.info('http %s %s', method, endpoint)
- if not endpoint.startswith('https'):
- endpoint = API_BASE + endpoint
- resp = requests.request(method,
- endpoint,
- headers={'Authorization': f'Bearer {API_KEY}'},
- **kwargs)
- resp.raise_for_status()
- if resp_json:
- return resp.json()
- else:
- return resp
-
-def paginate(method: str, url: str):
- while True:
- resp = api(method, url, resp_json=False)
- yield from resp.json()
- next_one = resp.links.get('next')
- if not next_one:
- return
- url = next_one.get('url')
- if not url:
- return
-
-class DataClassUnpack:
- """Taken from: https://stackoverflow.com/a/72164665"""
- classFieldCache = {}
-
- @classmethod
- def instantiate(cls, classToInstantiate, argDict):
- if classToInstantiate not in cls.classFieldCache:
- cls.classFieldCache[classToInstantiate] = {
- f.name
- for f in getattr(classToInstantiate, dataclasses._FIELDS).values() if f._field_type is not dataclasses._FIELD_CLASSVAR # type: ignore
- }
-
- fieldSet = cls.classFieldCache[classToInstantiate]
- filteredArgDict = {k: v for k, v in argDict.items() if k in fieldSet}
- return classToInstantiate(**filteredArgDict)
-
-@dataclasses.dataclass
-class Label:
- name: str
- description: str
-
-@dataclasses.dataclass
-class Issue:
- number: int
- url: str
- html_url: str
- title: str
- body: str
- labels: dataclasses.InitVar[list[dict]]
- labels_clean: list[Label] = dataclasses.field(init=False)
-
- def __post_init__(self, labels):
- self.labels_clean = [DataClassUnpack.instantiate(Label, l) for l in labels]
-
-def issues_to_import():
- yield from paginate('GET', '/repos/nixos/nix/issues?state=open&labels=lix-import')
-
-def issues_already_imported():
- yield from paginate('GET', '/repos/lix-project/lix/issues?state=all&labels=imported')
-
-
-UPSTREAM_ISSUE_RE = re.compile(r'^Upstream-Issue: https://git\.lix\.systems/NixOS/nix/issues/(\d+)$', re.MULTILINE)
-
-def make_already_imported():
- d = {}
- for issue in issues_already_imported():
- iss = DataClassUnpack.instantiate(Issue, issue)
- print(iss)
- match = UPSTREAM_ISSUE_RE.search(iss.body)
- if match:
- d[int(match.group(1))] = iss
-
- return d
-
-def new_issue(title, body, labels):
- api('POST', '/repos/lix-project/lix/issues', resp_json=True, json={
- 'labels': labels,
- 'body': body,
- 'title': title,
- 'dont_notify': True,
- })
-
-already_imported = make_already_imported()
-
-def import_issue(iss: Issue):
- if iss.number in already_imported:
- log.info('Skipping already imported %d', iss.number)
- return
- new_body = textwrap.dedent('''
- Upstream-Issue: {iss}
-
- {original_body}
- ''').format(iss=iss.html_url, original_body=iss.body)
-
- new_labels = [LABEL_MAPPING[l.name] for l in iss.labels_clean if l.name in LABEL_MAPPING]
-
- new_title = '[Nix#{num}] {title}'.format(num=iss.number, title=iss.title)
-
- log.info('%s', f'create issue with: {new_labels} {new_title} {new_body}')
- new_issue(new_title, new_body, new_labels)
-
-def go():
- log.info('Importing issues!')
- for issue in issues_to_import():
- import_issue(DataClassUnpack.instantiate(Issue, issue))
-
-if __name__ == '__main__':
- go()
diff --git a/maintainers/release-notes b/maintainers/release-notes
deleted file mode 100755
index 51864cbc2..000000000
--- a/maintainers/release-notes
+++ /dev/null
@@ -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
diff --git a/maintainers/upload_manual.sh b/maintainers/upload_manual.sh
deleted file mode 100755
index f50520490..000000000
--- a/maintainers/upload_manual.sh
+++ /dev/null
@@ -1,40 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-cd "$(dirname -- "$0")/.."
-
-# This script uploads the Lix manual to the Lix s3 store.
-# It expects credentials to be configured like so:
-#
-# ~/.aws/credentials:
-#
-# [default]
-# aws_access_key_id = SOMEACCESSKEY
-# aws_secret_access_key = SOMESECRETKEY
-#
-# default can also be replaced by some other string if AWS_PROFILE is set in
-# environment.
-#
-# See: https://rclone.org/s3/#authentication
-#
-# To obtain such a key, log into the garage host and run:
-# (obtain GARAGE_RPC_SECRET into environment perhaps by systemctl cat garage)
-# garage key create SOME-KEY-NAME
-# garage bucket allow --read --write docs --key SOME-KEY-NAME
-
-if [[ ! -f result-doc/share/doc/nix/manual/index.html ]]; then
- echo -e "result-doc does not appear to contain a Lix manual. You can build one with:\n nix build '.#default^*'" >&2
- exit 1
-fi
-
-# --checksum: https://rclone.org/s3/#avoiding-head-requests-to-read-the-modification-time
-# By default rclone uses the modification time to determine if something needs
-# syncing. This is actually very bad for our use case, since we have small
-# files that have meaningless (Unix epoch) local modification time data. We can
-# make it go both 16x faster and more correct by using md5s instead.
-rclone \
- --config doc/manual/rclone.conf \
- -vv \
- sync \
- --checksum \
- result-doc/share/doc/nix/manual/ lix-docs:docs/manual/nightly/
diff --git a/meson.build b/meson.build
deleted file mode 100644
index 5885905c5..000000000
--- a/meson.build
+++ /dev/null
@@ -1,483 +0,0 @@
-#
-# OUTLINE:
-#
-# The top-level meson.build file (this file) handles general logic for build options,
-# generation of config.h (which is put in the build directory, not the source root
-# like the previous, autoconf-based build system did), the mechanism for header
-# generation, and the few global C++ compiler arguments that are added to all targets in Lix.
-#
-# src/meson.build coordinates each of Lix's subcomponents (the lib dirs in ./src),
-# which each have their own meson.build. Lix's components depend on each other,
-# so each of `src/lib{util,store,fetchers,expr,main,cmd}/meson.build` rely on variables
-# set in earlier `meson.build` files. Each of these also defines the install targets for
-# their headers.
-#
-# src/meson.build also collects the miscellaneous source files that are in further subdirectories
-# that become part of the final Nix command (things like `src/nix-build/*.cc`).
-#
-# Finally, src/nix/meson.build defines the Nix command itself, relying on all prior meson files.
-#
-# Unit tests are setup in tests/unit/meson.build, under the test suite "check".
-#
-# Functional tests are a bit more complicated. Generally they're defined in
-# tests/functional/meson.build, and rely on helper scripts meson/setup-functional-tests.py
-# and meson/run-test.py. Scattered around also are configure_file() invocations, which must
-# be placed in specific directories' meson.build files to create the right directory tree
-# in the build directory.
-
-project('lix', 'cpp',
- version : run_command('bash', '-c', 'echo -n $(cat ./.version)$VERSION_SUFFIX', check : true).stdout().strip(),
- default_options : [
- 'cpp_std=c++2a',
- # TODO(Qyriad): increase the warning level
- 'warning_level=1',
- 'debug=true',
- 'optimization=2',
- 'errorlogs=true', # Please print logs for tests that fail
- ],
-)
-
-fs = import('fs')
-
-prefix = get_option('prefix')
-# For each of these paths, assume that it is relative to the prefix unless
-# it is already an absolute path (which is the default for store-dir, state-dir, and log-dir).
-path_opts = [
- # Meson built-ins.
- 'datadir',
- 'bindir',
- 'mandir',
- 'libdir',
- 'includedir',
- 'libexecdir',
- # Homecooked Lix directories.
- 'store-dir',
- 'state-dir',
- 'log-dir',
- 'profile-dir',
-]
-# For your grepping pleasure, this loop sets the following variables that aren't mentioned
-# literally above:
-# store_dir
-# state_dir
-# log_dir
-# profile_dir
-foreach optname : path_opts
- varname = optname.replace('-', '_')
- path = get_option(optname)
- if fs.is_absolute(path)
- set_variable(varname, path)
- else
- set_variable(varname, prefix / path)
- endif
-endforeach
-
-# sysconfdir doesn't get anything installed to directly, and is only used to
-# tell Lix where to look for nix.conf, so it doesn't get appended to prefix.
-sysconfdir = get_option('sysconfdir')
-if not fs.is_absolute(sysconfdir)
- sysconfdir = '/' / sysconfdir
-endif
-
-# All of this has to go before the rest of the dependency checking,
-# so that internal-api-docs can be built with -Denable-build=false
-
-enable_docs = get_option('enable-docs')
-enable_internal_api_docs = get_option('internal-api-docs')
-
-doxygen = find_program('doxygen', required : enable_internal_api_docs, native : true)
-bash = find_program('bash', native : true)
-
-rapidcheck_meson = dependency('rapidcheck', required : enable_internal_api_docs)
-
-if enable_internal_api_docs.enabled()
- message('subdiring()')
- subdir('doc/internal-api')
-endif
-
-if not get_option('enable-build')
- subdir_done()
-endif
-
-enable_tests = get_option('enable-tests')
-
-tests_args = []
-
-if get_option('tests-color')
- tests_args += '--gtest_color=yes'
-endif
-
-if get_option('tests-brief')
- tests_args += '--gtest_brief=1'
-endif
-
-
-cxx = meson.get_compiler('cpp')
-
-# 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
-# to those architectures is currently broken for other reasons, namely:
-# - nixos-23.11's x86_64-linux -> i686-linux glibc does not build (also applies to cppnix)
-# - nixpkgs-unstable (as of 2024/04)'s boehmgc is not compatible with our patches
-# It's also broken in cppnix, though.
-host_cpu = host_machine.cpu_family()
-if host_cpu in ['x86', 'i686', 'i386']
- # Meson considers 32-bit x86 CPUs to be "x86", and does not consider 64-bit
- # x86 CPUs to be "x86" (instead using "x86_64", which needs no translation).
- host_cpu = 'i686'
-elif host_cpu == 'amd64'
- # This should not be needed under normal circumstances, but someone could pass a --cross-file
- # that sets the cpu_family to this.
- host_cpu = 'x86_64'
-elif host_cpu in ['armv6', 'armv7']
- host_cpu += 'l'
-endif
-
-host_system = host_machine.cpu_family() + '-' + host_machine.system()
-message('canonical Nix system name:', host_system)
-
-is_linux = host_machine.system() == 'linux'
-is_darwin = host_machine.system() == 'darwin'
-is_x64 = host_machine.cpu_family() == 'x86_64'
-
-# Per-platform arguments that you should probably pass to shared_module() invocations.
-# Something like add_project_arguments() can't be scoped on only shared modules, so this
-# variable is here instead.
-# This corresponds to the $(1)_ALLOW_UNDEFINED option from the Make buildsystem.
-# Mostly this is load-bearing on the plugin tests defined in tests/functional/plugins/meson.build.
-shared_module_link_args = []
-if is_darwin
- shared_module_link_args += ['-undefined', 'suppress', '-flat_namespace']
-elif is_linux
- # -Wl,-z,defs is the equivalent, but a comment in the Make buildsystem says that breaks
- # Clang sanitizers on Linux.
- # FIXME(Qyriad): is that true?
-endif
-deps = [ ]
-configdata = { }
-
-#
-# Dependencies
-#
-
-boehm = dependency('bdw-gc', required : get_option('gc'))
-if boehm.found()
- deps += boehm
-endif
-configdata += {
- 'HAVE_BOEHMGC': boehm.found().to_int(),
-}
-
-boost = dependency('boost', required : true, modules : ['context', 'coroutine', 'container'])
-deps += boost
-
-# cpuid only makes sense on x86_64
-cpuid_required = is_x64 ? get_option('cpuid') : false
-cpuid = dependency('libcpuid', 'cpuid', required : cpuid_required)
-configdata += {
- 'HAVE_LIBCPUID': cpuid.found().to_int(),
-}
-deps += cpuid
-
-# seccomp only makes sense on Linux
-seccomp_required = is_linux ? get_option('seccomp-sandboxing') : false
-seccomp = dependency('libseccomp', 'seccomp', required : seccomp_required, version : '>=2.5.5')
-configdata += {
- 'HAVE_SECCOMP': seccomp.found().to_int(),
-}
-
-libarchive = dependency('libarchive', required : true)
-deps += libarchive
-
-brotli = [
- dependency('libbrotlicommon', required : true),
- dependency('libbrotlidec', required : true),
- dependency('libbrotlienc', required : true),
-]
-deps += brotli
-
-openssl = dependency('libcrypto', 'openssl', required : true)
-deps += openssl
-
-aws_sdk = dependency('aws-cpp-sdk-core', required : false)
-aws_sdk_transfer = dependency('aws-cpp-sdk-transfer', required : aws_sdk.found())
-if aws_sdk.found()
- # The AWS pkg-config adds -std=c++11.
- # https://github.com/aws/aws-sdk-cpp/issues/2673
- aws_sdk = aws_sdk.partial_dependency(
- compile_args : false,
- includes : true,
- link_args : true,
- links : true,
- sources : true,
- )
- deps += aws_sdk
- 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,
- link_args : true,
- links : true,
- sources : true,
- )
-endif
-
-aws_s3 = dependency('aws-cpp-sdk-s3', required : false)
-if aws_s3.found()
- # The AWS pkg-config adds -std=c++11.
- # https://github.com/aws/aws-sdk-cpp/issues/2673
- aws_s3 = aws_s3.partial_dependency(
- compile_args : false,
- includes : true,
- link_args : true,
- links : true,
- sources : true,
- )
- deps += aws_s3
-endif
-
-configdata += {
- 'ENABLE_S3': aws_s3.found().to_int(),
-}
-
-sqlite = dependency('sqlite3', 'sqlite', version : '>=3.6.19', required : true)
-deps += sqlite
-
-sodium = dependency('libsodium', 'sodium', required : true)
-deps += sodium
-
-curl = dependency('libcurl', 'curl', required : true)
-deps += curl
-
-editline = dependency('libeditline', 'editline', version : '>=1.14', required : true)
-deps += editline
-
-lowdown = dependency('lowdown', version : '>=0.9.0', required : true)
-deps += lowdown
-
-# HACK(Qyriad): rapidcheck's pkg-config doesn't include the libs lol
-# Note: technically we 'check' for rapidcheck twice, for the internal-api-docs handling above,
-# but Meson will cache the result of the first one, and the required : arguments are different.
-rapidcheck_meson = dependency('rapidcheck', required : enable_tests)
-rapidcheck = declare_dependency(dependencies : rapidcheck_meson, link_args : ['-lrapidcheck'])
-deps += rapidcheck
-
-gtest = [
- dependency('gtest', required : enable_tests),
- dependency('gtest_main', required : enable_tests),
- dependency('gmock', required : enable_tests),
- dependency('gmock_main', required : enable_tests),
-]
-deps += gtest
-
-toml11 = dependency('toml11', version : '>=3.7.0', required : true, method : 'cmake')
-deps += toml11
-
-nlohmann_json = dependency('nlohmann_json', required : true)
-deps += nlohmann_json
-
-# lix-doc is a Rust project provided via buildInputs and unfortunately doesn't have any way to be detected.
-# Just declare it manually to resolve this.
-#
-# FIXME: build this with meson in the future after we drop Make (with which we
-# *absolutely* are not going to make it work)
-lix_doc = declare_dependency(link_args : [ '-llix_doc' ])
-deps += lix_doc
-
-#
-# Build-time tools
-#
-coreutils = find_program('coreutils', native : true)
-dot = find_program('dot', required : false, native : true)
-pymod = import('python')
-python = pymod.find_installation('python3')
-
-if enable_docs
- mdbook = find_program('mdbook', native : true)
-endif
-
-# Used to workaround https://github.com/mesonbuild/meson/issues/2320 in src/nix/meson.build.
-installcmd = find_program('install', native : true)
-
-enable_embedded_sandbox_shell = get_option('enable-embedded-sandbox-shell')
-if enable_embedded_sandbox_shell
- # This one goes in config.h
- # The path to busybox is passed as a -D flag when compiling libstore.
- # Idk why, ask the old buildsystem.
- configdata += {
- 'HAVE_EMBEDDED_SANDBOX_SHELL': 1,
- }
-endif
-
-sandbox_shell = get_option('sandbox-shell')
-# Consider it required if we're on Linux and the user explicitly specified a non-default value.
-sandbox_shell_required = sandbox_shell != 'busybox' and host_machine.system() == 'linux'
-# NOTE(Qyriad): package.nix puts busybox in buildInputs for Linux.
-# Most builds should not require setting this.
-busybox = find_program(sandbox_shell, required : sandbox_shell_required, native : false)
-if not busybox.found() and host_machine.system() == 'linux' and sandbox_shell_required
- warning('busybox not found and other sandbox shell was specified')
- warning('a sandbox shell is recommended on Linux -- configure with -Dsandbox-shell=/path/to/shell to set')
-endif
-# FIXME(Qyriad): the autoconf system checks that busybox has the "standalone" feature, indicating
-# 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.
-# FIXME(Qyriad): do we really need to use the shell for this?
-gen_header_sh = 'echo \'R"__NIX_STR(\' | cat - @INPUT@ && echo \')__NIX_STR"\''
-gen_header = generator(
- bash,
- arguments : [ '-c', gen_header_sh ],
- capture : true,
- output : '@PLAINNAME@.gen.hh',
-)
-
-#
-# Configuration
-#
-
-run_command('ln', '-s',
- meson.project_build_root() / '__nothing_link_target',
- meson.project_build_root() / '__nothing_symlink',
- check : true,
-)
-can_link_symlink = run_command('ln',
- meson.project_build_root() / '__nothing_symlink',
- meson.project_build_root() / '__nothing_hardlink',
- check : false,
-).returncode() == 0
-run_command('rm', '-f',
- meson.project_build_root() / '__nothing_symlink',
- meson.project_build_root() / '__nothing_hardlink',
- check : true,
-)
-summary('can hardlink to symlink', can_link_symlink, bool_yn : true)
-configdata += { 'CAN_LINK_SYMLINK': can_link_symlink.to_int() }
-
-
-# Check for each of these functions, and create a define like `#define HAVE_LCHOWN 1`.
-check_funcs = [
- 'lchown',
- 'lutimes',
- 'pipe2',
- 'posix_fallocate',
- 'statvfs',
- 'strsignal',
- 'sysconf',
-]
-foreach funcspec : check_funcs
- define_name = 'HAVE_' + funcspec.underscorify().to_upper()
- define_value = cxx.has_function(funcspec).to_int()
- configdata += {
- define_name: define_value,
- }
-endforeach
-
-config_h = configure_file(
- configuration : {
- 'PACKAGE_NAME': '"' + meson.project_name() + '"',
- 'PACKAGE_VERSION': '"' + meson.project_version() + '"',
- 'PACKAGE_TARNAME': '"' + meson.project_name() + '"',
- 'PACKAGE_STRING': '"' + meson.project_name() + ' ' + meson.project_version() + '"',
- 'HAVE_STRUCT_DIRENT_D_TYPE': 1, # FIXME: actually check this for solaris
- 'SYSTEM': '"' + host_system + '"',
- } + configdata,
- output : 'config.h',
-)
-
-install_headers(config_h, subdir : 'nix')
-
-add_project_arguments(
- # TODO(Qyriad): Yes this is how the autoconf+Make system did it.
- # It would be nice for our headers to be idempotent instead.
- '-include', 'config.h',
- '-Wno-deprecated-declarations',
- '-Wimplicit-fallthrough',
- '-Werror=switch',
- '-Werror=switch-enum',
- '-Wdeprecated-copy',
- '-Wignored-qualifiers',
- # Enable assertions in libstdc++ by default. Harmless on libc++. Benchmarked
- # at ~1% overhead in `nix search`.
- #
- # FIXME: remove when we get meson 1.4.0 which will default this to on for us:
- # https://mesonbuild.com/Release-notes-for-1-4-0.html#ndebug-setting-now-controls-c-stdlib-assertions
- '-D_GLIBCXX_ASSERTIONS=1',
- language : 'cpp',
-)
-
-if cxx.get_id() in ['gcc', 'clang']
- # 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.
- #
- # This has an unmeasurably low overhead in Nix evaluation benchmarks.
- #
- # N.B. Meson generates a completely nonsense warning here:
- # https://github.com/mesonbuild/meson/issues/9822
- # Both of these args cannot be written in the default meson configuration.
- # b_sanitize=signed-integer-overflow is ignored, and
- # -fsanitize-undefined-trap-on-error is not representable.
- sanitize_args = ['-fsanitize=signed-integer-overflow', '-fsanitize-undefined-trap-on-error']
- add_project_arguments(sanitize_args, language: 'cpp')
- add_project_link_arguments(sanitize_args, 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
-
-# Generate Chromium tracing files for each compiled file, which enables
-# maintainers/buildtime_report.sh BUILD-DIR to simply work in clang builds.
-#
-# They can also be manually viewed at https://ui.perfetto.dev
-if get_option('profile-build').require(meson.get_compiler('cpp').get_id() == 'clang').enabled()
- add_project_arguments('-ftime-trace', language: 'cpp')
-endif
-
-if cxx.get_id() in ['clang', 'gcc']
- add_project_arguments([
- # Meson uses out of source builds, conventionally usually in a subdirectory
- # of the source tree (e.g. meson setup ./build). This means that unlike in
- # the previous Make buildsystem, all compilation sources are passed as a relative
- # parent, e.g. `cc -o src/libexpr/nixexpr.cc.o ../src/libexpr/nixexpr.cc`.
- # These paths show up when debugging, and in asserts, which look both look strange
- # and confuse debuggers.
- # So let's just tell GCC and Clang that ../src really means src.
- '-ffile-prefix-map=../src=src',
- ],
- language : 'cpp',
- )
-endif
-
-if is_darwin
- configure_file(
- input : 'misc/launchd/org.nixos.nix-daemon.plist.in',
- output : 'org.nixos.nix-daemon.plist',
- copy : true,
- install_dir : prefix / 'Library/LaunchDaemons',
- )
-endif
-
-subdir('src')
-subdir('scripts')
-subdir('misc')
-
-if enable_docs
- subdir('doc/manual')
-endif
-
-if enable_tests
- subdir('tests/unit')
- subdir('tests/functional')
-endif
diff --git a/meson.options b/meson.options
deleted file mode 100644
index 6b13fa8a0..000000000
--- a/meson.options
+++ /dev/null
@@ -1,66 +0,0 @@
-# vim: filetype=meson
-
-option('enable-build', type : 'boolean', value : true,
- description : 'Set to false to not actually build. Only really makes sense with -Dinternal-api-docs=true',
-)
-
-option('gc', type : 'feature',
- description : 'enable garbage collection in the Nix expression evaluator (requires Boehm GC)',
-)
-
-option('enable-embedded-sandbox-shell', type : 'boolean', value : false,
- description : 'include the sandbox shell in the Nix binary',
-)
-
-option('cpuid', type : 'feature',
- description : 'determine microarchitecture levels with libcpuid (only relevant on x86_64)',
-)
-
-option('seccomp-sandboxing', type : 'feature',
- description : 'build support for seccomp sandboxing (recommended unless your arch doesn\'t support libseccomp, only relevant on Linux)',
-)
-
-option('sandbox-shell', type : 'string', value : 'busybox',
- description : 'path to a statically-linked shell to use as /bin/sh in sandboxes (usually busybox)',
-)
-
-option('enable-tests', type : 'boolean', value : true,
- description : 'whether to enable tests or not (requires rapidcheck and gtest)',
-)
-
-option('tests-color', type : 'boolean', value : true,
- description : 'set to false to disable color output in gtest',
-)
-
-option('tests-brief', type : 'boolean', value : false,
- description : 'set to true for shorter tests output',
-)
-
-option('profile-build', type : 'feature', value: 'disabled',
- description : 'whether to enable -ftime-trace in clang builds, allowing for speeding up the build.'
-)
-
-option('store-dir', type : 'string', value : '/nix/store',
- description : 'path of the Nix store',
-)
-
-option('state-dir', type : 'string', value : '/nix/var',
- description : 'path to store state in for Nix',
-)
-
-option('log-dir', type : 'string', value : '/nix/var/log/nix',
- description : 'path to store logs in for Nix',
-)
-
-option('enable-docs', type : 'boolean', value : true,
- description : 'whether to build documentation',
-)
-
-option('internal-api-docs', type : 'feature', value : 'auto',
- description : 'whether to build internal API documentation (requires doxygen)',
-)
-
-# A relative path means it gets appended to prefix.
-option('profile-dir', type : 'string', value : 'etc/profile.d',
- description : 'the path to install shell profile files',
-)
diff --git a/meson/cleanup-install.bash b/meson/cleanup-install.bash
deleted file mode 100755
index 3e229cbc6..000000000
--- a/meson/cleanup-install.bash
+++ /dev/null
@@ -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/nix/parser-tab.cc" "$includedir/nix/lexer-tab.cc"
diff --git a/meson/run-test.py b/meson/run-test.py
deleted file mode 100755
index 3c5baa230..000000000
--- a/meson/run-test.py
+++ /dev/null
@@ -1,86 +0,0 @@
-#!/usr/bin/env python3
-
-"""
-This script is a helper for this project's Meson buildsystem to run Lix's
-functional tests. It is an analogue to mk/run-test.sh in the autoconf+Make
-buildsystem.
-
-These tests are run in the installCheckPhase in Lix's derivation, and as such
-expect to be run after the project has already been "installed" to some extent.
-Look at meson/setup-functional-tests.py for more details.
-"""
-
-import argparse
-from pathlib import Path
-import os
-import shutil
-import subprocess
-import sys
-
-name = 'run-test.py'
-
-if 'MESON_BUILD_ROOT' not in os.environ:
- raise ValueError(f'{name}: this script must be run from the Meson build system')
-
-def main():
-
- tests_dir = Path(os.path.join(os.environ['MESON_BUILD_ROOT'], 'tests/functional'))
-
- parser = argparse.ArgumentParser(name)
- parser.add_argument('target', help='the script path relative to tests/functional to run')
- args = parser.parse_args()
-
- target = Path(args.target)
- # The test suite considers the test's name to be the path to the test relative to
- # `tests/functional`, but without the file extension.
- # e.g. for `tests/functional/flakes/develop.sh`, the test name is `flakes/develop`
- test_name = target.with_suffix('').as_posix()
- if not target.is_absolute():
- target = tests_dir.joinpath(target).resolve()
-
- assert target.exists(), f'{name}: test {target} does not exist; did you run `meson install`?'
-
- bash = os.environ.get('BASH', shutil.which('bash'))
- if bash is None:
- raise ValueError(f'{name}: bash executable not found and BASH environment variable not set')
-
- test_environment = os.environ | {
- 'TEST_NAME': test_name,
- # mk/run-test.sh did this, but I don't know if it has any effect since it seems
- # like the tests that interact with remote stores set it themselves?
- 'NIX_REMOTE': '',
- }
-
- # Initialize testing.
- init_result = subprocess.run([bash, '-e', 'init.sh'], cwd=tests_dir, env=test_environment)
- if init_result.returncode != 0:
- print(f'{name}: internal error initializing {args.target}', file=sys.stderr)
- print('[ERROR]')
- # Meson interprets exit code 99 as indicating an *error* in the testing process.
- return 99
-
- # Run the test itself.
- test_result = subprocess.run([bash, '-e', target.name], cwd=target.parent, env=test_environment)
-
- if test_result.returncode == 0:
- print('[PASS]')
- elif test_result.returncode == 99:
- print('[SKIP]')
- # Meson interprets exit code 77 as indicating a skipped test.
- return 77
- else:
- print('[FAIL]')
-
- return test_result.returncode
-
-try:
- sys.exit(main())
-except AssertionError as e:
- # This should mean that this test was run not-from-Meson, probably without
- # having run `meson install` first, which is not an bug in this script.
- print(e, file=sys.stderr)
- sys.exit(99)
-except Exception as e:
- print(f'{name}: INTERNAL ERROR running test ({sys.argv}): {e}', file=sys.stderr)
- print(f'this is a bug in {name}')
- sys.exit(99)
diff --git a/meson/setup-functional-tests.py b/meson/setup-functional-tests.py
deleted file mode 100755
index 344bdc92e..000000000
--- a/meson/setup-functional-tests.py
+++ /dev/null
@@ -1,105 +0,0 @@
-#!/usr/bin/env python3
-
-"""
-So like. This script is cursed.
-It's a helper for this project's Meson buildsystem for Lix's functional tests.
-The functional tests are a bunch of bash scripts, that each expect to be run from the
-directory from the directory that that script is in, and also expect modifications to have
-happened to the source tree, and even splork files around. The last is against the spirit
-of Meson (and personally annoying), to have build processes that aren't self-contained in the
-out-of-source build directory, but more problematically we need configured files in the test
-tree.
-So. We copy the tests tree into the build directory.
-Meson doesn't have a good way of doing this natively -- the best you could do is subdir()
-into every directory in the tests tree and configure_file(copy : true) on every file,
-but this won't copy symlinks as symlinks, which we need since the test suite has, well,
-tests on symlinks.
-However, the functional tests are normally run during Lix's derivation's installCheckPhase,
-after Lix has already been "installed" somewhere. So in Meson we setup add this file as an
-install script and copy everything in tests/functional to the build directory, preserving
-things like symlinks, even broken ones (which are intentional).
-
-TODO(Qyriad): when we remove the old build system entirely, we can instead fix the tests.
-"""
-
-from pathlib import Path
-import os, os.path
-import shutil
-import sys
-import traceback
-
-name = 'setup-functional-tests.py'
-
-if 'MESON_SOURCE_ROOT' not in os.environ or 'MESON_BUILD_ROOT' not in os.environ:
- raise ValueError(f'{name}: this script must be run from the Meson build system')
-
-print(f'{name}: mirroring tests/functional to build directory')
-
-tests_source = Path(os.environ['MESON_SOURCE_ROOT']) / 'tests/functional'
-tests_build = Path(os.environ['MESON_BUILD_ROOT']) / 'tests/functional'
-
-def main():
-
- os.chdir(tests_build)
-
- for src_dirpath, src_dirnames, src_filenames in os.walk(tests_source):
- src_dirpath = Path(src_dirpath)
- assert src_dirpath.is_absolute(), f'{src_dirpath=} is not absolute'
-
- # os.walk() gives us the absolute path to the directory we're currently in as src_dirpath.
- # We want to mirror from the perspective of `tests_source`.
- rel_subdir = src_dirpath.relative_to(tests_source)
- assert (not rel_subdir.is_absolute()), f'{rel_subdir=} is not relative'
-
- # And then join that relative path on `tests_build` to get the absolute
- # path in the build directory that corresponds to `src_dirpath`.
- build_dirpath = tests_build / rel_subdir
- assert build_dirpath.is_absolute(), f'{build_dirpath=} is not absolute'
-
- # More concretely, for the test file tests/functional/ca/build.sh:
- # - src_dirpath is `$MESON_SOURCE_ROOT/tests/functional/ca`
- # - rel_subidr is `ca`
- # - build_dirpath is `$MESON_BUILD_ROOT/tests/functional/ca`
-
- # `src_dirname` are directories underneath `src_dirpath`, and will be relative
- # to `src_dirpath`.
- for src_dirname in src_dirnames:
- # Take the name of the directory in the tests source and join it on `src_dirpath`
- # to get the full path to this specific directory in the tests source.
- src = src_dirpath / src_dirname
- # If there isn't *something* here, then our logic is wrong.
- # Path.exists(follow_symlinks=False) wasn't added until Python 3.12, so we use
- # os.path.lexists() here.
- assert os.path.lexists(src), f'{src=} does not exist'
-
- # Take the name of this directory and join it on `build_dirpath` to get the full
- # path to the directory in `build/tests/functional` that we need to create.
- dest = build_dirpath / src_dirname
- if src.is_symlink():
- src_target = src.readlink()
- dest.unlink(missing_ok=True)
- dest.symlink_to(src_target)
- else:
- dest.mkdir(parents=True, exist_ok=True)
-
- for src_filename in src_filenames:
- # os.walk() should be giving us relative filenames.
- # If it isn't, our path joins will be veeeery wrong.
- assert (not Path(src_filename).is_absolute()), f'{src_filename=} is not relative'
-
- src = src_dirpath / src_filename
- dst = build_dirpath / src_filename
- # Mildly misleading name -- unlink removes ordinary files as well as symlinks.
- dst.unlink(missing_ok=True)
- # shutil.copy2() best-effort preserves metadata.
- shutil.copy2(src, dst, follow_symlinks=False)
-
-
-try:
- sys.exit(main())
-except Exception as e:
- # Any error is likely a bug in this script.
- print(f'{name}: INTERNAL ERROR setting up functional tests: {e}', file=sys.stderr)
- print(traceback.format_exc())
- print(f'this is a bug in {name}')
- sys.exit(1)
diff --git a/misc/bash/completion.sh b/misc/bash/completion.sh
deleted file mode 100644
index 9af695f5a..000000000
--- a/misc/bash/completion.sh
+++ /dev/null
@@ -1,22 +0,0 @@
-function _complete_nix {
- local -a words
- local cword cur
- _get_comp_words_by_ref -n ':=&' words cword cur
- local have_type
- while IFS= read -r line; do
- local completion=${line%% *}
- if [[ -z $have_type ]]; then
- have_type=1
- if [[ $completion == filenames ]]; then
- compopt -o filenames
- elif [[ $completion == attrs ]]; then
- compopt -o nospace
- fi
- else
- COMPREPLY+=("$completion")
- fi
- done < <(NIX_GET_COMPLETIONS=$cword "${words[@]}" 2>/dev/null)
- __ltrim_colon_completions "$cur"
-}
-
-complete -F _complete_nix nix
diff --git a/misc/bash/meson.build b/misc/bash/meson.build
deleted file mode 100644
index 75acce2ea..000000000
--- a/misc/bash/meson.build
+++ /dev/null
@@ -1,8 +0,0 @@
-configure_file(
- input : 'completion.sh',
- output : 'nix',
- install : true,
- install_dir : datadir / 'bash-completion/completions',
- install_mode : 'rw-r--r--',
- copy : true,
-)
diff --git a/misc/clangbuildanalyzer.nix b/misc/clangbuildanalyzer.nix
deleted file mode 100644
index d73fa8bbb..000000000
--- a/misc/clangbuildanalyzer.nix
+++ /dev/null
@@ -1,33 +0,0 @@
-# Upstreaming here, can be deleted once it's upstreamed:
-# https://github.com/NixOS/nixpkgs/pull/297102
-{
- stdenv,
- lib,
- cmake,
- fetchFromGitHub,
-}:
-stdenv.mkDerivation (finalAttrs: {
- pname = "clangbuildanalyzer";
- version = "1.5.0";
-
- src = fetchFromGitHub {
- owner = "aras-p";
- repo = "ClangBuildAnalyzer";
- rev = "v${finalAttrs.version}";
- sha256 = "sha256-kmgdk634zM0W0OoRoP/RzepArSipa5bNqdVgdZO9gxo=";
- };
-
- nativeBuildInputs = [ cmake ];
-
- meta = {
- description = "Tool for analyzing Clang's -ftrace-time files";
- homepage = "https://github.com/aras-p/ClangBuildAnalyzer";
- maintainers = with lib.maintainers; [ lf- ];
- license = lib.licenses.unlicense;
- platforms = lib.platforms.unix;
- # `long long int` != `size_t`
- # There's no convenient lib.platforms.32bit or anything, but it's easy enough to do ourselves.
- badPlatforms = lib.filter (plat: (lib.systems.elaborate plat).is32bit) lib.platforms.all;
- mainProgram = "ClangBuildAnalyzer";
- };
-})
diff --git a/misc/fish/completion.fish b/misc/fish/completion.fish
deleted file mode 100644
index c6b8ef16a..000000000
--- a/misc/fish/completion.fish
+++ /dev/null
@@ -1,36 +0,0 @@
-function _nix_complete
- # Get the current command up to a cursor.
- # - Behaves correctly even with pipes and nested in commands like env.
- # - TODO: Returns the command verbatim (does not interpolate variables).
- # That might not be optimal for arguments like -f.
- set -l nix_args (commandline --current-process --tokenize --cut-at-cursor)
- # --cut-at-cursor with --tokenize removes the current token so we need to add it separately.
- # https://github.com/fish-shell/fish-shell/issues/7375
- # Can be an empty string.
- set -l current_token (commandline --current-token --cut-at-cursor)
-
- # Nix wants the index of the argv item to complete but the $nix_args variable
- # also contains the program name (argv[0]) so we would need to subtract 1.
- # But the variable also misses the current token so it cancels out.
- set -l nix_arg_to_complete (count $nix_args)
-
- env NIX_GET_COMPLETIONS=$nix_arg_to_complete $nix_args $current_token
-end
-
-function _nix_accepts_files
- set -l response (_nix_complete)
- test $response[1] = 'filenames'
-end
-
-function _nix
- set -l response (_nix_complete)
- # Skip the first line since it handled by _nix_accepts_files.
- # Tail lines each contain a command followed by a tab character and, optionally, a description.
- # This is also the format fish expects.
- string collect -- $response[2..-1]
-end
-
-# Disable file path completion if paths do not belong in the current context.
-complete --command nix --condition 'not _nix_accepts_files' --no-files
-
-complete --command nix --arguments '(_nix)'
diff --git a/misc/fish/meson.build b/misc/fish/meson.build
deleted file mode 100644
index d54de9a13..000000000
--- a/misc/fish/meson.build
+++ /dev/null
@@ -1,8 +0,0 @@
-configure_file(
- input : 'completion.fish',
- output : 'nix.fish',
- install : true,
- install_dir : datadir / 'fish/vendor_completions.d',
- install_mode : 'rw-r--r--',
- copy : true,
-)
diff --git a/misc/flake-registry/flake-registry.json b/misc/flake-registry/flake-registry.json
deleted file mode 100644
index d83ace92b..000000000
--- a/misc/flake-registry/flake-registry.json
+++ /dev/null
@@ -1,414 +0,0 @@
-{
- "flakes": [
- {
- "from": {
- "id": "agda",
- "type": "indirect"
- },
- "to": {
- "owner": "agda",
- "repo": "agda",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "arion",
- "type": "indirect"
- },
- "to": {
- "owner": "hercules-ci",
- "repo": "arion",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "blender-bin",
- "type": "indirect"
- },
- "to": {
- "dir": "blender",
- "owner": "edolstra",
- "repo": "nix-warez",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "bundlers",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "repo": "bundlers",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "cachix",
- "type": "indirect"
- },
- "to": {
- "owner": "cachix",
- "repo": "cachix",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "composable",
- "type": "indirect"
- },
- "to": {
- "owner": "ComposableFi",
- "repo": "composable",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "disko",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-community",
- "repo": "disko",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "dreampkgs",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-community",
- "repo": "dreampkgs",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "dwarffs",
- "type": "indirect"
- },
- "to": {
- "owner": "edolstra",
- "repo": "dwarffs",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "emacs-overlay",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-community",
- "repo": "emacs-overlay",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "fenix",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-community",
- "repo": "fenix",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "flake-parts",
- "type": "indirect"
- },
- "to": {
- "owner": "hercules-ci",
- "repo": "flake-parts",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "flake-utils",
- "type": "indirect"
- },
- "to": {
- "owner": "numtide",
- "repo": "flake-utils",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "gemini",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-community",
- "repo": "flake-gemini",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "helix",
- "type": "indirect"
- },
- "to": {
- "owner": "helix-editor",
- "repo": "helix",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "hercules-ci-agent",
- "type": "indirect"
- },
- "to": {
- "owner": "hercules-ci",
- "repo": "hercules-ci-agent",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "hercules-ci-effects",
- "type": "indirect"
- },
- "to": {
- "owner": "hercules-ci",
- "repo": "hercules-ci-effects",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "home-manager",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-community",
- "repo": "home-manager",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "hydra",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "repo": "hydra",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "mach-nix",
- "type": "indirect"
- },
- "to": {
- "owner": "DavHau",
- "repo": "mach-nix",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nickel",
- "type": "indirect"
- },
- "to": {
- "owner": "tweag",
- "repo": "nickel",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nimble",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-community",
- "repo": "flake-nimble",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nix",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "repo": "nix",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nix-darwin",
- "type": "indirect"
- },
- "to": {
- "owner": "LnL7",
- "repo": "nix-darwin",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nix-serve",
- "type": "indirect"
- },
- "to": {
- "owner": "edolstra",
- "repo": "nix-serve",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nixops",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "repo": "nixops",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nixos-hardware",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "repo": "nixos-hardware",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nixos-homepage",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "repo": "nixos-homepage",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nixos-search",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "repo": "nixos-search",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nixpkgs",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "ref": "nixpkgs-unstable",
- "repo": "nixpkgs",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "nur",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-community",
- "repo": "NUR",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "patchelf",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "repo": "patchelf",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "poetry2nix",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-community",
- "repo": "poetry2nix",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "pridefetch",
- "type": "indirect"
- },
- "to": {
- "owner": "SpyHoodle",
- "repo": "pridefetch",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "sops-nix",
- "type": "indirect"
- },
- "to": {
- "owner": "Mic92",
- "repo": "sops-nix",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "systems",
- "type": "indirect"
- },
- "to": {
- "owner": "nix-systems",
- "repo": "default",
- "type": "github"
- }
- },
- {
- "from": {
- "id": "templates",
- "type": "indirect"
- },
- "to": {
- "owner": "NixOS",
- "repo": "templates",
- "type": "github"
- }
- }
- ],
- "version": 2
-}
diff --git a/misc/flake-registry/meson.build b/misc/flake-registry/meson.build
deleted file mode 100644
index 674ee8dbf..000000000
--- a/misc/flake-registry/meson.build
+++ /dev/null
@@ -1,4 +0,0 @@
-install_data(
- 'flake-registry.json',
- install_dir : datadir,
-)
diff --git a/misc/launchd/org.nixos.nix-daemon.plist.in b/misc/launchd/org.nixos.nix-daemon.plist.in
deleted file mode 100644
index 664608305..000000000
--- a/misc/launchd/org.nixos.nix-daemon.plist.in
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
-
- Label
- org.nixos.nix-daemon
- KeepAlive
- RunAtLoad
- ProgramArguments
-
- /bin/sh
- -c
- /bin/wait4path /nix/var/nix/profiles/default/bin/nix-daemon && exec /nix/var/nix/profiles/default/bin/nix-daemon
-
- StandardErrorPath
- /var/log/nix-daemon.log
- StandardOutPath
- /dev/null
- SoftResourceLimits
-
- NumberOfFiles
- 1048576
-
-
-
diff --git a/misc/meson.build b/misc/meson.build
deleted file mode 100644
index a8f09722c..000000000
--- a/misc/meson.build
+++ /dev/null
@@ -1,6 +0,0 @@
-subdir('bash')
-subdir('fish')
-subdir('zsh')
-
-subdir('systemd')
-subdir('flake-registry')
diff --git a/misc/pre-commit.nix b/misc/pre-commit.nix
deleted file mode 100644
index ea39bc21d..000000000
--- a/misc/pre-commit.nix
+++ /dev/null
@@ -1,99 +0,0 @@
-{
- /**
- Path to Lix's source, normally the flake's "self" argument
- */
- self ? pkgs.lib.cleanSource ./.,
- /**
- Already instantiated Nixpkgs
- */
- pkgs,
- /**
- pre-commit-hooks source path, normally from the flake input
- */
- pre-commit-hooks,
-}:
-let
- inherit (pkgs) lib;
- # Import pre-commit bypassing the flake because flakes don't let
- # you have overlays. Also their implementation forces an
- # unnecessary reimport of nixpkgs for our use cases.
- tools = import (pre-commit-hooks + "/nix/call-tools.nix") pkgs;
- pre-commit-run = pkgs.callPackage (pre-commit-hooks + "/nix/run.nix") {
- inherit tools;
- isFlakes = true;
- # unused!
- gitignore-nix-src = builtins.throw "gitignore-nix-src is unused";
- };
-in
-pre-commit-run {
- src = self;
- hooks = {
- no-commit-to-branch = {
- enable = true;
- settings.branch = [ "main" ];
- };
- check-case-conflicts.enable = true;
- check-executables-have-shebangs = {
- enable = true;
- stages = [ "commit" ];
- };
- check-shebang-scripts-are-executable = {
- enable = true;
- stages = [ "commit" ];
- };
- check-symlinks = {
- enable = true;
- excludes = [ "^tests/functional/lang/symlink-resolution/broken$" ];
- };
- check-merge-conflicts.enable = true;
- end-of-file-fixer = {
- enable = true;
- excludes = [
- "\\.drv$"
- "^tests/functional/lang/"
- ];
- };
- mixed-line-endings = {
- enable = true;
- excludes = [ "^tests/functional/lang/" ];
- };
- release-notes = {
- enable = true;
- package = pkgs.build-release-notes;
- files = ''^doc/manual/(change-authors\.yml|rl-next(-dev)?)'';
- pass_filenames = false;
- entry = ''
- ${lib.getExe pkgs.build-release-notes} --change-authors doc/manual/change-authors.yml doc/manual/rl-next doc/manual/rl-next-dev
- '';
- };
- check-headers = {
- enable = true;
- package = pkgs.check-headers;
- files = "^src/";
- types = [
- "c++"
- "file"
- "header"
- ];
- # generated files; these will never actually be seen by this
- # check, and are left here as documentation
- excludes = [
- "(parser|lexer)-tab\\.hh$"
- "\\.gen\\.hh$"
- ];
- entry = lib.getExe pkgs.check-headers;
- };
- # TODO: Once the test suite is nicer, clean up and start
- # enforcing trailing whitespace on tests that don't explicitly
- # check for it.
- trim-trailing-whitespace = {
- enable = true;
- stages = [ "commit" ];
- excludes = [ "^tests/functional/lang/" ];
- };
- treefmt = {
- enable = true;
- settings.formatters = [ pkgs.nixfmt ];
- };
- };
-}
diff --git a/misc/systemd/meson.build b/misc/systemd/meson.build
deleted file mode 100644
index 26e20af95..000000000
--- a/misc/systemd/meson.build
+++ /dev/null
@@ -1,25 +0,0 @@
-foreach config : [ 'nix-daemon.socket', 'nix-daemon.service' ]
- configure_file(
- input : config + '.in',
- output : config,
- install : true,
- install_dir : prefix / 'lib/systemd/system',
- install_mode : 'rw-r--r--',
- configuration : {
- 'storedir' : store_dir,
- 'localstatedir' : state_dir,
- 'bindir' : bindir,
- },
- )
-endforeach
-
-configure_file(
- input : 'nix-daemon.conf.in',
- output : 'nix-daemon.conf',
- install : true,
- install_dir : prefix / 'lib/tmpfiles.d',
- install_mode : 'rw-r--r--',
- configuration : {
- 'localstatedir' : state_dir,
- },
-)
diff --git a/misc/systemd/nix-daemon.conf.in b/misc/systemd/nix-daemon.conf.in
deleted file mode 100644
index e7b264234..000000000
--- a/misc/systemd/nix-daemon.conf.in
+++ /dev/null
@@ -1 +0,0 @@
-d @localstatedir@/nix/daemon-socket 0755 root root - -
diff --git a/misc/systemd/nix-daemon.service.in b/misc/systemd/nix-daemon.service.in
deleted file mode 100644
index 45fbea02c..000000000
--- a/misc/systemd/nix-daemon.service.in
+++ /dev/null
@@ -1,16 +0,0 @@
-[Unit]
-Description=Nix Daemon
-Documentation=man:nix-daemon https://nixos.org/manual
-RequiresMountsFor=@storedir@
-RequiresMountsFor=@localstatedir@
-RequiresMountsFor=@localstatedir@/nix/db
-ConditionPathIsReadWrite=@localstatedir@/nix/daemon-socket
-
-[Service]
-ExecStart=@@bindir@/nix-daemon nix-daemon --daemon
-KillMode=process
-LimitNOFILE=1048576
-TasksMax=1048576
-
-[Install]
-WantedBy=multi-user.target
diff --git a/misc/systemd/nix-daemon.socket.in b/misc/systemd/nix-daemon.socket.in
deleted file mode 100644
index 9ed39ffe6..000000000
--- a/misc/systemd/nix-daemon.socket.in
+++ /dev/null
@@ -1,11 +0,0 @@
-[Unit]
-Description=Nix Daemon Socket
-Before=multi-user.target
-RequiresMountsFor=@storedir@
-ConditionPathIsReadWrite=@localstatedir@/nix/daemon-socket
-
-[Socket]
-ListenStream=@localstatedir@/nix/daemon-socket/socket
-
-[Install]
-WantedBy=sockets.target
diff --git a/misc/systemv/nix-daemon b/misc/systemv/nix-daemon
deleted file mode 100755
index 3f2915632..000000000
--- a/misc/systemv/nix-daemon
+++ /dev/null
@@ -1,113 +0,0 @@
-#!/bin/sh
-#
-# nix-daemon: Starts the nix package manager daemon
-#
-# chkconfig: 345 24 02
-# description: This is a daemon which enable the multi-user mode
-# of the nix package manager.
-# processname: nix-daemon
-# pidfile: /var/run/nix/nix-daemon.pid
-
-### BEGIN INIT INFO
-# Required-Start:
-# Required-Stop:
-# Should-Start:
-# Should-Stop:
-# Default-Start: 3 4 5
-# Default-Stop: 0 1 2 6
-# Short-Description: Starts the nix daemon
-# Description: This is a daemon which enable the multi-user mode
-# of the nix package manager.
-### END INIT INFO
-
-NIX_DAEMON_BIN=/usr/bin/nix-daemon
-#NIX_DAEMON_USER="root"
-NIX_DAEMON_USER="nix-daemon"
-NIX_DAEMON_OPTS="--daemon"
-
-umask 0022
-
-if [ "$1" = 'status' ]; then
- test -x $NIX_DAEMON_BIN || exit 4
-else
- test -x $NIX_DAEMON_BIN || exit 5
-fi
-
-# Source function library.
-. /etc/init.d/functions
-
-LOCKFILE=/var/lock/subsys/nix-daemon
-RUNDIR=/var/run/nix
-PIDFILE=${RUNDIR}/nix-daemon.pid
-RETVAL=0
-
-base=${0##*/}
-
-start() {
-
- mkdir -p ${RUNDIR}
- chown ${NIX_DAEMON_USER}:${NIX_DAEMON_USER} ${RUNDIR}
-
- echo -n $"Starting nix daemon... "
-
- daemonize -u $NIX_DAEMON_USER -p ${PIDFILE} $NIX_DAEMON_BIN $NIX_DAEMON_OPTS
- RETVAL=$?
- echo
- [ $RETVAL -eq 0 ] && touch ${LOCKFILE}
- return $RETVAL
-}
-
-stop() {
- echo -n $"Shutting down nix daemon: "
- killproc -p ${PIDFILE} $NIX_DAEMON_BIN
- RETVAL=$?
- [ $RETVAL -eq 0 ] && rm -f ${LOCKFILE} ${PIDFILE}
- echo
- return $RETVAL
-}
-
-reload() {
- echo -n $"Reloading nix daemon... "
- killproc -p ${PIDFILE} $NIX_DAEMON_BIN -HUP
- RETVAL=$?
- echo
- return $RETVAL
-}
-
-restart() {
- stop
- start
-}
-
-RETVAL=0
-
-# caller switch
-case "$1" in
- start)
- start
- ;;
- stop)
- stop
- ;;
- status)
- status -p ${PIDFILE} $NIX_DAEMON_BIN
- RETVAL=$?
- ;;
- restart)
- restart
- ;;
- reload)
- reload
- ;;
- condrestart)
- if [ -f $LOCKFILE ]; then
- restart
- fi
- ;;
- *)
- echo $"Usage: $0 {start|stop|status|restart|condrestart}"
- exit 2
- ;;
-esac
-
-exit $RETVAL
diff --git a/misc/zsh/completion.zsh b/misc/zsh/completion.zsh
deleted file mode 100644
index f9b3dca74..000000000
--- a/misc/zsh/completion.zsh
+++ /dev/null
@@ -1,24 +0,0 @@
-#compdef nix
-
-function _nix() {
- local ifs_bk="$IFS"
- local input=("${(Q)words[@]}")
- IFS=$'\n'
- local res=($(NIX_GET_COMPLETIONS=$((CURRENT - 1)) "$input[@]" 2>/dev/null))
- IFS="$ifs_bk"
- local tpe="${${res[1]}%%> *}"
- local -a suggestions
- declare -a suggestions
- for suggestion in ${res:1}; do
- suggestions+=("${suggestion%% *}")
- done
- local -a args
- if [[ "$tpe" == filenames ]]; then
- args+=('-f')
- elif [[ "$tpe" == attrs ]]; then
- args+=('-S' '')
- fi
- compadd -J nix "${args[@]}" -a suggestions
-}
-
-_nix "$@"
diff --git a/misc/zsh/meson.build b/misc/zsh/meson.build
deleted file mode 100644
index 8063a5cb8..000000000
--- a/misc/zsh/meson.build
+++ /dev/null
@@ -1,10 +0,0 @@
-foreach script : [ [ 'completion.zsh', '_nix' ], [ 'run-help-nix' ] ]
- configure_file(
- input : script[0],
- output : script.get(1, script[0]),
- install : true,
- install_dir : datadir / 'zsh/site-functions',
- install_mode : 'rw-r--r--',
- copy : true,
- )
-endforeach
diff --git a/misc/zsh/run-help-nix b/misc/zsh/run-help-nix
deleted file mode 100644
index f91a304eb..000000000
--- a/misc/zsh/run-help-nix
+++ /dev/null
@@ -1,42 +0,0 @@
-emulate -L zsh
-
-# run-help is a zsh widget that can be bound to a key. It mainly looks up the
-# man page for the currently typed in command.
-#
-# Although run-help works for any command without requiring special support,
-# it can only deduce the right man page based solely on the name of the
-# command. Programs like Nix provide better integration with run-help by
-# helping zsh identify Nix subcommands and their corresponding man pages. This
-# is what this function does.
-#
-# To actually use run-help on zsh, place the following lines in your .zshrc:
-#
-# (( $+aliases[run-help] )) && unalias run-help
-# autoload -Uz run-help run-help-nix
-#
-# Then also assign run-help to any key of choice:
-#
-# bindkey '^[h' run-help
-
-while [[ "$#" != 0 && "$1" == -* ]]; do
- shift
-done
-
-local -a subcommands; subcommands=( nix3 )
-
-local arg
-for arg in "$@"; do
- if man -w "${(j:-:)subcommands}-$arg" >/dev/null 2>&1; then
- subcommands+="$arg"
- else
- break
- fi
-done
-
-if (( $#subcommands > 1 )); then
- man "${(j:-:)subcommands}"
-else
- man nix
-fi
-
-return $?
diff --git a/nix-support/binary-tarball.nix b/nix-support/binary-tarball.nix
deleted file mode 100644
index b73e59043..000000000
--- a/nix-support/binary-tarball.nix
+++ /dev/null
@@ -1,34 +0,0 @@
-{
- buildPackages,
- cacert,
- nix,
- system,
- version,
-}:
-let
- installerClosureInfo = buildPackages.closureInfo {
- rootPaths = [
- nix
- cacert
- ];
- };
-
- meta.description = "Distribution-independent Nix bootstrap binaries for ${system}";
-in
-buildPackages.runCommand "nix-binary-tarball-${version}" { inherit meta; } ''
- cp ${installerClosureInfo}/registration $TMPDIR/reginfo
-
- dir=nix-${version}-${system}
- fn=$out/$dir.tar.xz
- mkdir -p $out/nix-support
- echo "file binary-dist $fn" >> $out/nix-support/hydra-build-products
- tar cvfJ $fn \
- --owner=0 --group=0 --mode=u+rw,uga+r \
- --mtime='1970-01-01' \
- --absolute-names \
- --hard-dereference \
- --transform "s,$TMPDIR/reginfo,$dir/.reginfo," \
- --transform "s,$NIX_STORE,$dir/store,S" \
- $TMPDIR/reginfo \
- $(cat ${installerClosureInfo}/store-paths)
-''
diff --git a/nix-support/nixfmt.nix b/nix-support/nixfmt.nix
deleted file mode 100644
index b51e26295..000000000
--- a/nix-support/nixfmt.nix
+++ /dev/null
@@ -1,65 +0,0 @@
-# Copy of `nixfmt-rfc-style` vendored from `nixpkgs` master:
-# https://github.com/NixOS/nixpkgs/blob/ab6071eb54cc9b66dda436111d4f569e4e56cbf4/pkgs/by-name/ni/nixfmt-rfc-style/package.nix
-{
- haskell,
- haskellPackages,
- fetchFromGitHub,
-}:
-let
- inherit (haskell.lib.compose) justStaticExecutables;
- raw-pkg = haskellPackages.callPackage (
- {
- mkDerivation,
- base,
- cmdargs,
- directory,
- fetchzip,
- filepath,
- lib,
- megaparsec,
- mtl,
- parser-combinators,
- safe-exceptions,
- scientific,
- text,
- transformers,
- unix,
- }:
- mkDerivation {
- pname = "nixfmt";
- version = "0.6.0-unstable-2024-03-14";
- src = fetchFromGitHub {
- owner = "serokell";
- repo = "nixfmt";
- rev = "8d13b593fa8d8d6e5075f541f3231222a08e84df";
- hash = "sha256-HtXvzmfN4wk45qiKZ7V+/5WBV7jnTHfd7iBwF4XGl64=";
- };
- isLibrary = true;
- isExecutable = true;
- libraryHaskellDepends = [
- base
- megaparsec
- mtl
- parser-combinators
- scientific
- text
- transformers
- ];
- executableHaskellDepends = [
- base
- cmdargs
- directory
- filepath
- safe-exceptions
- text
- unix
- ];
- jailbreak = true;
- homepage = "https://github.com/serokell/nixfmt";
- description = "An opinionated formatter for Nix";
- license = lib.licenses.mpl20;
- mainProgram = "nixfmt";
- }
- ) { };
-in
-justStaticExecutables raw-pkg
diff --git a/package.nix b/package.nix
deleted file mode 100644
index be3bcfb35..000000000
--- a/package.nix
+++ /dev/null
@@ -1,458 +0,0 @@
-{
- pkgs,
- lib,
- stdenv,
- aws-sdk-cpp,
- # If the patched version of Boehm isn't passed, then patch it based off of
- # pkgs.boehmgc. This allows `callPackage`ing this file without needing to
- # to implement behavior that this package flat out doesn't build without
- # anyway, but also allows easily overriding the patch logic.
- boehmgc-nix ? __forDefaults.boehmgc-nix,
- boehmgc,
- nlohmann_json,
- bison,
- build-release-notes ? __forDefaults.build-release-notes,
- boost,
- brotli,
- bzip2,
- cmake,
- curl,
- doxygen,
- editline,
- flex,
- git,
- gtest,
- jq,
- libarchive,
- libcpuid,
- libseccomp,
- libsodium,
- lsof,
- lowdown,
- mdbook,
- mdbook-linkcheck,
- mercurial,
- meson,
- ninja,
- openssl,
- pkg-config,
- python3,
- rapidcheck,
- sqlite,
- toml11,
- util-linuxMinimal ? utillinuxMinimal,
- utillinuxMinimal ? null,
- xz,
-
- busybox-sandbox-shell,
-
- # internal fork of nix-doc providing :doc in the repl
- lix-doc ? __forDefaults.lix-doc,
-
- pname ? "nix",
- versionSuffix ? "",
- officialRelease ? false,
- # Set to true to build the release notes for the next release.
- buildUnreleasedNotes ? true,
- internalApiDocs ? false,
-
- # Not a real argument, just the only way to approximate let-binding some
- # stuff for argument defaults.
- __forDefaults ? {
- canRunInstalled = stdenv.buildPlatform.canExecute stdenv.hostPlatform;
-
- boehmgc-nix = (boehmgc.override { enableLargeConfig = true; }).overrideAttrs {
- patches = [
- # We do *not* include prev.patches (which doesn't exist in normal pkgs.boehmgc anyway)
- # because if the caller of this package passed a patched boehm as `boehmgc` instead of
- # `boehmgc-nix` then this will almost certainly have duplicate patches, which means
- # the patches won't apply and we'll get a build failure.
- ./boehmgc-coroutine-sp-fallback.diff
- # https://github.com/ivmai/bdwgc/pull/586
- ./boehmgc-traceable_allocator-public.diff
- ];
- };
-
- lix-doc = pkgs.callPackage ./lix-doc/package.nix { };
- build-release-notes = pkgs.callPackage ./maintainers/build-release-notes.nix { };
- },
-}:
-let
- inherit (__forDefaults) canRunInstalled;
- inherit (lib) fileset;
-
- version = lib.fileContents ./.version + versionSuffix;
-
- aws-sdk-cpp-nix = aws-sdk-cpp.override {
- apis = [
- "s3"
- "transfer"
- ];
- customMemoryManagement = false;
- };
-
- # Reimplementation of Nixpkgs' Meson cross file, with some additions to make
- # it actually work.
- mesonCrossFile =
- let
- cpuFamily =
- platform:
- with platform;
- if isAarch32 then
- "arm"
- else if isx86_32 then
- "x86"
- else
- platform.uname.processor;
- in
- builtins.toFile "lix-cross-file.conf" ''
- [properties]
- # Meson is convinced that if !buildPlatform.canExecute hostPlatform then we cannot
- # build anything at all, which is not at all correct. If we can't execute the host
- # platform, we'll just disable tests and doc gen.
- needs_exe_wrapper = false
-
- [binaries]
- # Meson refuses to consider any CMake binary during cross compilation if it's
- # not explicitly specified here, in the cross file.
- # https://github.com/mesonbuild/meson/blob/0ed78cf6fa6d87c0738f67ae43525e661b50a8a2/mesonbuild/cmake/executor.py#L72
- cmake = 'cmake'
- '';
-
- # The internal API docs need these for the build, but if we're not building
- # Nix itself, then these don't need to be propagated.
- maybePropagatedInputs = [
- boehmgc-nix
- nlohmann_json
- ];
-
- # .gitignore has already been processed, so any changes in it are irrelevant
- # at this point. It is not represented verbatim for test purposes because
- # that would interfere with repo semantics.
- baseFiles = fileset.fileFilter (f: f.name != ".gitignore") ./.;
-
- configureFiles = fileset.unions [ ./.version ];
-
- topLevelBuildFiles = fileset.unions ([
- ./meson.build
- ./meson.options
- ./meson
- ./scripts/meson.build
- ]);
-
- functionalTestFiles = fileset.unions [
- ./tests/functional
- ./tests/unit
- (fileset.fileFilter (f: lib.strings.hasPrefix "nix-profile" f.name) ./scripts)
- ];
-in
-stdenv.mkDerivation (finalAttrs: {
- inherit pname version;
-
- src = fileset.toSource {
- root = ./.;
- fileset = fileset.intersection baseFiles (
- fileset.unions (
- [
- configureFiles
- topLevelBuildFiles
- functionalTestFiles
- ]
- ++ lib.optionals (!finalAttrs.dontBuild || internalApiDocs) [
- ./boehmgc-coroutine-sp-fallback.diff
- ./doc
- ./misc
- ./precompiled-headers.h
- ./src
- ./COPYING
- ]
- )
- );
- };
-
- VERSION_SUFFIX = versionSuffix;
-
- outputs =
- [ "out" ]
- ++ lib.optionals (!finalAttrs.dontBuild) [
- "dev"
- "doc"
- ];
-
- dontBuild = false;
-
- mesonFlags =
- lib.optionals stdenv.hostPlatform.isLinux [
- # You'd think meson could just find this in PATH, but busybox is in buildInputs,
- # which don't actually get added to PATH. And buildInputs is correct over
- # nativeBuildInputs since this should be a busybox executable on the host.
- "-Dsandbox-shell=${lib.getExe' busybox-sandbox-shell "busybox"}"
- ]
- ++ lib.optional stdenv.hostPlatform.isStatic "-Denable-embedded-sandbox-shell=true"
- ++ lib.optional (finalAttrs.dontBuild) "-Denable-build=false"
- ++ [
- # mesonConfigurePhase automatically passes -Dauto_features=enabled,
- # so we must explicitly enable or disable features that we are not passing
- # dependencies for.
- (lib.mesonEnable "internal-api-docs" internalApiDocs)
- (lib.mesonBool "enable-tests" finalAttrs.doCheck)
- (lib.mesonBool "enable-docs" canRunInstalled)
- ]
- ++ lib.optional (stdenv.hostPlatform != stdenv.buildPlatform) "--cross-file=${mesonCrossFile}";
-
- # We only include CMake so that Meson can locate toml11, which only ships CMake dependency metadata.
- dontUseCmakeConfigure = true;
-
- nativeBuildInputs =
- [
- bison
- flex
- python3
- meson
- ninja
- cmake
- ]
- ++ [
- (lib.getBin lowdown)
- mdbook
- mdbook-linkcheck
- ]
- ++ [
- pkg-config
-
- # Tests
- git
- mercurial
- jq
- lsof
- ]
- ++ lib.optional stdenv.hostPlatform.isLinux util-linuxMinimal
- ++ lib.optional (!officialRelease && buildUnreleasedNotes) build-release-notes
- ++ lib.optional internalApiDocs doxygen;
-
- buildInputs =
- [
- curl
- bzip2
- xz
- brotli
- editline
- openssl
- sqlite
- libarchive
- boost
- lowdown
- libsodium
- toml11
- lix-doc
- ]
- ++ lib.optionals stdenv.hostPlatform.isLinux [
- libseccomp
- busybox-sandbox-shell
- ]
- ++ lib.optional internalApiDocs rapidcheck
- ++ lib.optional stdenv.hostPlatform.isx86_64 libcpuid
- # There have been issues building these dependencies
- ++ lib.optional (stdenv.hostPlatform == stdenv.buildPlatform) aws-sdk-cpp-nix
- ++ lib.optionals (finalAttrs.dontBuild) maybePropagatedInputs;
-
- checkInputs = [
- gtest
- rapidcheck
- ];
-
- propagatedBuildInputs = lib.optionals (!finalAttrs.dontBuild) maybePropagatedInputs;
-
- disallowedReferences = [ boost ];
-
- # Needed for Meson to find Boost.
- # https://github.com/NixOS/nixpkgs/issues/86131.
- env = {
- BOOST_INCLUDEDIR = "${lib.getDev boost}/include";
- BOOST_LIBRARYDIR = "${lib.getLib boost}/lib";
- };
-
- preConfigure =
- lib.optionalString (!finalAttrs.dontBuild && !stdenv.hostPlatform.isStatic) ''
- # Copy libboost_context so we don't get all of Boost in our closure.
- # https://github.com/NixOS/nixpkgs/issues/45462
- mkdir -p $out/lib
- cp -pd ${boost}/lib/{libboost_context*,libboost_thread*,libboost_system*} $out/lib
- rm -f $out/lib/*.a
- ''
- + lib.optionalString (!finalAttrs.dontBuild && stdenv.hostPlatform.isLinux) ''
- chmod u+w $out/lib/*.so.*
- patchelf --set-rpath $out/lib:${stdenv.cc.cc.lib}/lib $out/lib/libboost_thread.so.*
- ''
- + lib.optionalString (!finalAttrs.dontBuild && stdenv.hostPlatform.isDarwin) ''
- for LIB in $out/lib/*.dylib; do
- chmod u+w $LIB
- install_name_tool -id $LIB $LIB
- install_name_tool -delete_rpath ${boost}/lib/ $LIB || true
- done
- install_name_tool -change ${boost}/lib/libboost_system.dylib $out/lib/libboost_system.dylib $out/lib/libboost_thread.dylib
- ''
- + ''
- # Workaround https://github.com/NixOS/nixpkgs/issues/294890.
- if [[ -n "''${doCheck:-}" ]]; then
- appendToVar configureFlags "--enable-tests"
- else
- appendToVar configureFlags "--disable-tests"
- fi
- '';
-
- mesonBuildType = "debugoptimized";
-
- installTargets = lib.optional internalApiDocs "internal-api-html";
-
- enableParallelBuilding = true;
-
- doCheck = canRunInstalled;
-
- mesonCheckFlags = [
- "--suite=check"
- "--print-errorlogs"
- ];
- # the tests access localhost.
- __darwinAllowLocalNetworking = true;
-
- # Make sure the internal API docs are already built, because mesonInstallPhase
- # won't let us build them there. They would normally be built in buildPhase,
- # but the internal API docs are conventionally built with doBuild = false.
- preInstall = lib.optional internalApiDocs ''
- meson ''${mesonBuildFlags:-} compile "$installTargets"
- '';
-
- postInstall =
- lib.optionalString (!finalAttrs.dontBuild) ''
- mkdir -p $doc/nix-support
- echo "doc manual $doc/share/doc/nix/manual" >> $doc/nix-support/hydra-build-products
- ''
- + lib.optionalString stdenv.hostPlatform.isStatic ''
- mkdir -p $out/nix-support
- echo "file binary-dist $out/bin/nix" >> $out/nix-support/hydra-build-products
- ''
- + lib.optionalString stdenv.isDarwin ''
- for lib in libnixutil.dylib libnixexpr.dylib; do
- install_name_tool \
- -change "${lib.getLib boost}/lib/libboost_context.dylib" \
- "$out/lib/libboost_context.dylib" \
- "$out/lib/$lib"
- done
- ''
- + lib.optionalString internalApiDocs ''
- mkdir -p $out/nix-support
- echo "doc internal-api-docs $out/share/doc/nix/internal-api/html" >> "$out/nix-support/hydra-build-products"
- '';
-
- doInstallCheck = finalAttrs.doCheck;
-
- mesonInstallCheckFlags = [
- "--suite=installcheck"
- "--print-errorlogs"
- ];
-
- installCheckPhase = ''
- runHook preInstallCheck
- flagsArray=($mesonInstallCheckFlags "''${mesonInstallCheckFlagsArray[@]}")
- meson test --no-rebuild "''${flagsArray[@]}"
- runHook postInstallCheck
- '';
-
- separateDebugInfo = !stdenv.hostPlatform.isStatic && !finalAttrs.dontBuild;
-
- strictDeps = true;
-
- # strictoverflow is disabled because we trap on signed overflow instead
- hardeningDisable = [ "strictoverflow" ] ++ lib.optional stdenv.hostPlatform.isStatic "pie";
-
- meta.platforms = lib.platforms.unix;
-
- passthru.perl-bindings = pkgs.callPackage ./perl { inherit fileset stdenv; };
-
- # Export the patched version of boehmgc.
- # flake.nix exports that into its overlay.
- passthru = {
- inherit (__forDefaults) boehmgc-nix build-release-notes;
-
- # The collection of dependency logic for this derivation is complicated enough that
- # it's easier to parameterize the devShell off an already called package.nix.
- mkDevShell =
- {
- mkShell,
- just,
- nixfmt,
- glibcLocales,
- pre-commit-checks,
- clang-tools,
- llvmPackages,
- clangbuildanalyzer,
- contribNotice,
- }:
- let
- glibcFix = lib.optionalAttrs (stdenv.buildPlatform.isLinux && glibcLocales != null) {
- # Required to make non-NixOS Linux not complain about missing locale files during configure in a dev shell
- LOCALE_ARCHIVE = "${lib.getLib pkgs.glibcLocales}/lib/locale/locale-archive";
- };
- # for some reason that seems accidental and was changed in
- # NixOS 24.05-pre, clang-tools is pinned to LLVM 14 when
- # default LLVM is newer.
- clang-tools_llvm = clang-tools.override { inherit llvmPackages; };
-
- # pkgs.mkShell uses pkgs.stdenv by default, regardless of inputsFrom.
- actualMkShell = mkShell.override { inherit stdenv; };
- in
- actualMkShell (
- glibcFix
- // {
-
- inputsFrom = [ finalAttrs ];
-
- # For Meson to find Boost.
- env = finalAttrs.env;
-
- packages =
- lib.optional (stdenv.cc.isClang && stdenv.hostPlatform == stdenv.buildPlatform) clang-tools_llvm
- ++ [
- just
- nixfmt
- # Load-bearing order. Must come before clang-unwrapped below, but after clang_tools above.
- stdenv.cc
- ]
- ++ lib.optionals stdenv.cc.isClang [
- # Required for clang-tidy checks.
- llvmPackages.llvm
- llvmPackages.clang-unwrapped.dev
- ]
- ++ lib.optional (pre-commit-checks ? enabledPackages) pre-commit-checks.enabledPackages
- ++ lib.optional (lib.meta.availableOn stdenv.buildPlatform clangbuildanalyzer) clangbuildanalyzer
- ++ finalAttrs.checkInputs;
-
- shellHook = ''
- PATH=$prefix/bin:$PATH
- unset PYTHONPATH
- export MANPATH=$out/share/man:$MANPATH
-
- # Make bash completion work.
- XDG_DATA_DIRS+=:$out/share
-
- ${lib.optionalString (pre-commit-checks ? shellHook) pre-commit-checks.shellHook}
- # Allow `touch .nocontribmsg` to turn this notice off.
- if ! [[ -f .nocontribmsg ]]; then
- cat ${contribNotice}
- fi
-
- # Install the Gerrit commit-msg hook.
- # (git common dir is the main .git, including for worktrees)
- if gitcommondir=$(git rev-parse --git-common-dir 2>/dev/null) && [[ ! -f "$gitcommondir/hooks/commit-msg" ]]; then
- echo 'Installing Gerrit commit-msg hook (adds Change-Id to commit messages)' >&2
- mkdir -p "$gitcommondir/hooks"
- curl -s -Lo "$gitcommondir/hooks/commit-msg" https://gerrit.lix.systems/tools/hooks/commit-msg
- chmod u+x "$gitcommondir/hooks/commit-msg"
- fi
- unset gitcommondir
- '';
- }
- );
- };
-})
diff --git a/perl/MANIFEST b/perl/MANIFEST
deleted file mode 100644
index 08897647c..000000000
--- a/perl/MANIFEST
+++ /dev/null
@@ -1,7 +0,0 @@
-Changes
-Makefile.PL
-MANIFEST
-Nix.xs
-README
-t/Nix.t
-lib/Nix.pm
diff --git a/perl/configure.ac b/perl/configure.ac
deleted file mode 100644
index a02cb06c9..000000000
--- a/perl/configure.ac
+++ /dev/null
@@ -1,84 +0,0 @@
-AC_INIT(nix-perl, m4_esyscmd([bash -c "echo -n $(cat ../.version)$VERSION_SUFFIX"]))
-AC_CONFIG_SRCDIR(MANIFEST)
-AC_CONFIG_AUX_DIR(../config)
-
-CFLAGS=
-CXXFLAGS=
-AC_PROG_CC
-AC_PROG_CXX
-
-AC_CANONICAL_HOST
-
-# Use 64-bit file system calls so that we can support files > 2 GiB.
-AC_SYS_LARGEFILE
-
-AC_DEFUN([NEED_PROG],
-[
-AC_PATH_PROG($1, $2)
-if test -z "$$1"; then
- AC_MSG_ERROR([$2 is required])
-fi
-])
-
-NEED_PROG(perl, perl)
-NEED_PROG(curl, curl)
-NEED_PROG(bzip2, bzip2)
-NEED_PROG(xz, xz)
-
-# Test that Perl has the open/fork feature (Perl 5.8.0 and beyond).
-AC_MSG_CHECKING([whether Perl is recent enough])
-if ! $perl -e 'open(FOO, "-|", "true"); while () { print; }; close FOO or die;'; then
- AC_MSG_RESULT(no)
- AC_MSG_ERROR([Your Perl version is too old. Nix requires Perl 5.8.0 or newer.])
-fi
-AC_MSG_RESULT(yes)
-
-
-# Figure out where to install Perl modules.
-AC_MSG_CHECKING([for the Perl installation prefix])
-perlversion=$($perl -e 'use Config; print $Config{version};')
-perlarchname=$($perl -e 'use Config; print $Config{archname};')
-AC_SUBST(perllibdir, [${libdir}/perl5/site_perl/$perlversion/$perlarchname])
-AC_MSG_RESULT($perllibdir)
-
-# Look for libsodium.
-PKG_CHECK_MODULES([SODIUM], [libsodium], [CXXFLAGS="$SODIUM_CFLAGS $CXXFLAGS"])
-
-# Check for the required Perl dependencies (DBI and DBD::SQLite).
-perlFlags="-I$perllibdir"
-
-AC_ARG_WITH(dbi, AC_HELP_STRING([--with-dbi=PATH],
- [prefix of the Perl DBI library]),
- perlFlags="$perlFlags -I$withval")
-
-AC_ARG_WITH(dbd-sqlite, AC_HELP_STRING([--with-dbd-sqlite=PATH],
- [prefix of the Perl DBD::SQLite library]),
- perlFlags="$perlFlags -I$withval")
-
-AC_MSG_CHECKING([whether DBD::SQLite works])
-if ! $perl $perlFlags -e 'use DBI; use DBD::SQLite;' 2>&5; then
- AC_MSG_RESULT(no)
- AC_MSG_FAILURE([The Perl modules DBI and/or DBD::SQLite are missing.])
-fi
-AC_MSG_RESULT(yes)
-
-AC_SUBST(perlFlags)
-
-PKG_CHECK_MODULES([NIX], [nix-store])
-
-NEED_PROG([NIX], [nix])
-
-# Expand all variables in config.status.
-test "$prefix" = NONE && prefix=$ac_default_prefix
-test "$exec_prefix" = NONE && exec_prefix='${prefix}'
-for name in $ac_subst_vars; do
- declare $name="$(eval echo "${!name}")"
- declare $name="$(eval echo "${!name}")"
- declare $name="$(eval echo "${!name}")"
-done
-
-rm -f Makefile.config
-ln -sfn ../mk mk
-
-AC_CONFIG_FILES([])
-AC_OUTPUT
diff --git a/perl/default.nix b/perl/default.nix
deleted file mode 100644
index 7ce418402..000000000
--- a/perl/default.nix
+++ /dev/null
@@ -1,59 +0,0 @@
-{
- lib,
- fileset,
- stdenv,
- perl,
- perlPackages,
- pkg-config,
- nix,
- curl,
- bzip2,
- xz,
- boost,
- libsodium,
- darwin,
- meson,
- ninja,
-}:
-
-perl.pkgs.toPerlModule (
- stdenv.mkDerivation {
- name = "nix-perl-${nix.version}";
-
- src = fileset.toSource {
- root = ../.;
- fileset = fileset.unions ([
- ../.version
- ./lib
- ./meson.build
- ]);
- };
-
- nativeBuildInputs = [
- pkg-config
- meson
- ninja
- ];
-
- buildInputs =
- [
- nix
- curl
- bzip2
- xz
- perl
- boost
- perlPackages.DBI
- perlPackages.DBDSQLite
- ]
- ++ lib.optional (stdenv.isLinux || stdenv.isDarwin) libsodium
- ++ lib.optional stdenv.isDarwin darwin.apple_sdk.frameworks.Security;
-
- # Nixpkgs' Meson hook likes to set this to "plain".
- mesonBuildType = "debugoptimized";
-
- enableParallelBuilding = true;
-
- postUnpack = "sourceRoot=$sourceRoot/perl";
- }
-)
diff --git a/perl/lib/Nix/Config.pm.in b/perl/lib/Nix/Config.pm.in
deleted file mode 100644
index 508a15e15..000000000
--- a/perl/lib/Nix/Config.pm.in
+++ /dev/null
@@ -1,25 +0,0 @@
-package Nix::Config;
-
-use MIME::Base64;
-use Nix::Store;
-
-$version = "@PACKAGE_VERSION@";
-
-$binDir = Nix::Store::getBinDir;
-$storeDir = Nix::Store::getStoreDir;
-
-%config = ();
-
-sub readConfig {
- my $config = "$confDir/nix.conf";
- return unless -f $config;
-
- open CONFIG, "<$config" or die "cannot open '$config'";
- while () {
- /^\s*([\w\-\.]+)\s*=\s*(.*)$/ or next;
- $config{$1} = $2;
- }
- close CONFIG;
-}
-
-return 1;
diff --git a/perl/lib/Nix/CopyClosure.pm b/perl/lib/Nix/CopyClosure.pm
deleted file mode 100644
index 902ee1a1b..000000000
--- a/perl/lib/Nix/CopyClosure.pm
+++ /dev/null
@@ -1,61 +0,0 @@
-package Nix::CopyClosure;
-
-use utf8;
-use strict;
-use Nix::Config;
-use Nix::Store;
-use Nix::SSH;
-use List::Util qw(sum);
-use IPC::Open2;
-
-
-sub copyToOpen {
- my ($from, $to, $sshHost, $storePaths, $includeOutputs, $dryRun, $useSubstitutes) = @_;
-
- $useSubstitutes = 0 if $dryRun || !defined $useSubstitutes;
-
- # Get the closure of this path.
- my @closure = reverse(topoSortPaths(computeFSClosure(0, $includeOutputs,
- map { followLinksToStorePath $_ } @{$storePaths})));
-
- # Send the "query valid paths" command with the "lock" option
- # enabled. This prevents a race where the remote host
- # garbage-collect paths that are already there. Optionally, ask
- # the remote host to substitute missing paths.
- syswrite($to, pack("L{url} eq $info->{url};
- }
-
- push @{$narFileList}, $info if !$found;
-}
-
-
-sub addPatch {
- my ($patches, $storePath, $patch) = @_;
-
- $$patches{$storePath} = []
- unless defined $$patches{$storePath};
-
- my $patchList = $$patches{$storePath};
-
- my $found = 0;
- foreach my $patch2 (@{$patchList}) {
- $found = 1 if
- $patch2->{url} eq $patch->{url} &&
- $patch2->{basePath} eq $patch->{basePath};
- }
-
- push @{$patchList}, $patch if !$found;
-
- return !$found;
-}
-
-
-sub readManifest_ {
- my ($manifest, $addNAR, $addPatch) = @_;
-
- # Decompress the manifest if necessary.
- if ($manifest =~ /\.bz2$/) {
- open MANIFEST, "$Nix::Config::bzip2 -d < $manifest |"
- or die "cannot decompress '$manifest': $!";
- } else {
- open MANIFEST, "<$manifest"
- or die "cannot open '$manifest': $!";
- }
-
- my $inside = 0;
- my $type;
-
- my $manifestVersion = 2;
-
- my ($storePath, $url, $hash, $size, $basePath, $baseHash, $patchType);
- my ($narHash, $narSize, $references, $deriver, $copyFrom, $system, $compressionType);
-
- while () {
- chomp;
- s/\#.*$//g;
- next if (/^$/);
-
- if (!$inside) {
-
- if (/^\s*(\w*)\s*\{$/) {
- $type = $1;
- $type = "narfile" if $type eq "";
- $inside = 1;
- undef $storePath;
- undef $url;
- undef $hash;
- undef $size;
- undef $narHash;
- undef $narSize;
- undef $basePath;
- undef $baseHash;
- undef $patchType;
- undef $system;
- $references = "";
- $deriver = "";
- $compressionType = "bzip2";
- }
-
- } else {
-
- if (/^\}$/) {
- $inside = 0;
-
- if ($type eq "narfile") {
- &$addNAR($storePath,
- { url => $url, hash => $hash, size => $size
- , narHash => $narHash, narSize => $narSize
- , references => $references
- , deriver => $deriver
- , system => $system
- , compressionType => $compressionType
- });
- }
-
- elsif ($type eq "patch") {
- &$addPatch($storePath,
- { url => $url, hash => $hash, size => $size
- , basePath => $basePath, baseHash => $baseHash
- , narHash => $narHash, narSize => $narSize
- , patchType => $patchType
- });
- }
-
- }
-
- elsif (/^\s*StorePath:\s*(\/\S+)\s*$/) { $storePath = $1; }
- elsif (/^\s*CopyFrom:\s*(\/\S+)\s*$/) { $copyFrom = $1; }
- elsif (/^\s*Hash:\s*(\S+)\s*$/) { $hash = $1; }
- elsif (/^\s*URL:\s*(\S+)\s*$/) { $url = $1; }
- elsif (/^\s*Compression:\s*(\S+)\s*$/) { $compressionType = $1; }
- elsif (/^\s*Size:\s*(\d+)\s*$/) { $size = $1; }
- elsif (/^\s*BasePath:\s*(\/\S+)\s*$/) { $basePath = $1; }
- elsif (/^\s*BaseHash:\s*(\S+)\s*$/) { $baseHash = $1; }
- elsif (/^\s*Type:\s*(\S+)\s*$/) { $patchType = $1; }
- elsif (/^\s*NarHash:\s*(\S+)\s*$/) { $narHash = $1; }
- elsif (/^\s*NarSize:\s*(\d+)\s*$/) { $narSize = $1; }
- elsif (/^\s*References:\s*(.*)\s*$/) { $references = $1; }
- elsif (/^\s*Deriver:\s*(\S+)\s*$/) { $deriver = $1; }
- elsif (/^\s*ManifestVersion:\s*(\d+)\s*$/) { $manifestVersion = $1; }
- elsif (/^\s*System:\s*(\S+)\s*$/) { $system = $1; }
-
- # Compatibility;
- elsif (/^\s*NarURL:\s*(\S+)\s*$/) { $url = $1; }
- elsif (/^\s*MD5:\s*(\S+)\s*$/) { $hash = "md5:$1"; }
-
- }
- }
-
- close MANIFEST;
-
- return $manifestVersion;
-}
-
-
-sub readManifest {
- my ($manifest, $narFiles, $patches) = @_;
- readManifest_($manifest,
- sub { addNAR($narFiles, @_); },
- sub { addPatch($patches, @_); } );
-}
-
-
-sub writeManifest {
- my ($manifest, $narFiles, $patches, $noCompress) = @_;
-
- open MANIFEST, ">$manifest.tmp"; # !!! check exclusive
-
- print MANIFEST "version {\n";
- print MANIFEST " ManifestVersion: 3\n";
- print MANIFEST "}\n";
-
- foreach my $storePath (sort (keys %{$narFiles})) {
- my $narFileList = $$narFiles{$storePath};
- foreach my $narFile (@{$narFileList}) {
- print MANIFEST "{\n";
- print MANIFEST " StorePath: $storePath\n";
- print MANIFEST " NarURL: $narFile->{url}\n";
- print MANIFEST " Compression: $narFile->{compressionType}\n";
- print MANIFEST " Hash: $narFile->{hash}\n" if defined $narFile->{hash};
- print MANIFEST " Size: $narFile->{size}\n" if defined $narFile->{size};
- print MANIFEST " NarHash: $narFile->{narHash}\n";
- print MANIFEST " NarSize: $narFile->{narSize}\n" if $narFile->{narSize};
- print MANIFEST " References: $narFile->{references}\n"
- if defined $narFile->{references} && $narFile->{references} ne "";
- print MANIFEST " Deriver: $narFile->{deriver}\n"
- if defined $narFile->{deriver} && $narFile->{deriver} ne "";
- print MANIFEST " System: $narFile->{system}\n" if defined $narFile->{system};
- print MANIFEST "}\n";
- }
- }
-
- foreach my $storePath (sort (keys %{$patches})) {
- my $patchList = $$patches{$storePath};
- foreach my $patch (@{$patchList}) {
- print MANIFEST "patch {\n";
- print MANIFEST " StorePath: $storePath\n";
- print MANIFEST " NarURL: $patch->{url}\n";
- print MANIFEST " Hash: $patch->{hash}\n";
- print MANIFEST " Size: $patch->{size}\n";
- print MANIFEST " NarHash: $patch->{narHash}\n";
- print MANIFEST " NarSize: $patch->{narSize}\n" if $patch->{narSize};
- print MANIFEST " BasePath: $patch->{basePath}\n";
- print MANIFEST " BaseHash: $patch->{baseHash}\n";
- print MANIFEST " Type: $patch->{patchType}\n";
- print MANIFEST "}\n";
- }
- }
-
-
- close MANIFEST;
-
- rename("$manifest.tmp", $manifest)
- or die "cannot rename $manifest.tmp: $!";
-
-
- # Create a bzipped manifest.
- unless (defined $noCompress) {
- system("$Nix::Config::bzip2 < $manifest > $manifest.bz2.tmp") == 0
- or die "cannot compress manifest";
-
- rename("$manifest.bz2.tmp", "$manifest.bz2")
- or die "cannot rename $manifest.bz2.tmp: $!";
- }
-}
-
-
-# Return a fingerprint of a store path to be used in binary cache
-# signatures. It contains the store path, the base-32 SHA-256 hash of
-# the contents of the path, and the references.
-sub fingerprintPath {
- my ($storePath, $narHash, $narSize, $references) = @_;
- die if substr($storePath, 0, length($Nix::Config::storeDir)) ne $Nix::Config::storeDir;
- die if substr($narHash, 0, 7) ne "sha256:";
- # Convert hash from base-16 to base-32, if necessary.
- $narHash = "sha256:" . convertHash("sha256", substr($narHash, 7), 1)
- if length($narHash) == 71;
- die if length($narHash) != 59;
- foreach my $ref (@{$references}) {
- die if substr($ref, 0, length($Nix::Config::storeDir)) ne $Nix::Config::storeDir;
- }
- return "1;" . $storePath . ";" . $narHash . ";" . $narSize . ";" . join(",", @{$references});
-}
-
-
-# Parse a NAR info file.
-sub parseNARInfo {
- my ($storePath, $content, $requireValidSig, $location) = @_;
-
- my ($storePath2, $url, $fileHash, $fileSize, $narHash, $narSize, $deriver, $system, $sig);
- my $compression = "bzip2";
- my @refs;
-
- foreach my $line (split "\n", $content) {
- return undef unless $line =~ /^(.*): (.*)$/;
- if ($1 eq "StorePath") { $storePath2 = $2; }
- elsif ($1 eq "URL") { $url = $2; }
- elsif ($1 eq "Compression") { $compression = $2; }
- elsif ($1 eq "FileHash") { $fileHash = $2; }
- elsif ($1 eq "FileSize") { $fileSize = int($2); }
- elsif ($1 eq "NarHash") { $narHash = $2; }
- elsif ($1 eq "NarSize") { $narSize = int($2); }
- elsif ($1 eq "References") { @refs = split / /, $2; }
- elsif ($1 eq "Deriver") { $deriver = $2; }
- elsif ($1 eq "System") { $system = $2; }
- elsif ($1 eq "Sig") { $sig = $2; }
- }
-
- return undef if $storePath ne $storePath2 || !defined $url || !defined $narHash;
-
- my $res =
- { url => $url
- , compression => $compression
- , fileHash => $fileHash
- , fileSize => $fileSize
- , narHash => $narHash
- , narSize => $narSize
- , refs => [ @refs ]
- , deriver => $deriver
- , system => $system
- };
-
- if ($requireValidSig) {
- # FIXME: might be useful to support multiple signatures per .narinfo.
-
- if (!defined $sig) {
- warn "NAR info file '$location' lacks a signature; ignoring\n";
- return undef;
- }
- my ($keyName, $sig64) = split ":", $sig;
- return undef unless defined $keyName && defined $sig64;
-
- my $publicKey = $Nix::Config::binaryCachePublicKeys{$keyName};
- if (!defined $publicKey) {
- warn "NAR info file '$location' is signed by unknown key '$keyName'; ignoring\n";
- return undef;
- }
-
- my $fingerprint;
- eval {
- $fingerprint = fingerprintPath(
- $storePath, $narHash, $narSize,
- [ map { "$Nix::Config::storeDir/$_" } @refs ]);
- };
- if ($@) {
- warn "cannot compute fingerprint of '$location'; ignoring\n";
- return undef;
- }
-
- if (!checkSignature($publicKey, decode_base64($sig64), $fingerprint)) {
- warn "NAR info file '$location' has an incorrect signature; ignoring\n";
- return undef;
- }
-
- $res->{signedBy} = $keyName;
- }
-
- return $res;
-}
-
-
-return 1;
diff --git a/perl/lib/Nix/SSH.pm b/perl/lib/Nix/SSH.pm
deleted file mode 100644
index 490ba0ea9..000000000
--- a/perl/lib/Nix/SSH.pm
+++ /dev/null
@@ -1,110 +0,0 @@
-package Nix::SSH;
-
-use utf8;
-use strict;
-use File::Temp qw(tempdir);
-use IPC::Open2;
-
-our @ISA = qw(Exporter);
-our @EXPORT = qw(
- @globalSshOpts
- readN readInt readString readStrings
- writeInt writeString writeStrings
- connectToRemoteNix
-);
-
-
-our @globalSshOpts = split ' ', ($ENV{"NIX_SSHOPTS"} or "");
-
-
-sub readN {
- my ($bytes, $from) = @_;
- my $res = "";
- while ($bytes > 0) {
- my $s;
- my $n = sysread($from, $s, $bytes);
- die "I/O error reading from remote side\n" if !defined $n;
- die "got EOF while expecting $bytes bytes from remote side\n" if !$n;
- $bytes -= $n;
- $res .= $s;
- }
- return $res;
-}
-
-
-sub readInt {
- my ($from) = @_;
- return unpack("L= 0x300;
-
- return ($from, $to, $pid);
-}
-
-
-1;
diff --git a/perl/lib/Nix/Store.pm b/perl/lib/Nix/Store.pm
deleted file mode 100644
index 3e4bbee0a..000000000
--- a/perl/lib/Nix/Store.pm
+++ /dev/null
@@ -1,42 +0,0 @@
-package Nix::Store;
-
-use strict;
-use warnings;
-
-require Exporter;
-
-our @ISA = qw(Exporter);
-
-our %EXPORT_TAGS = ( 'all' => [ qw( ) ] );
-
-our @EXPORT_OK = ( @{ $EXPORT_TAGS{'all'} } );
-
-our @EXPORT = qw(
- setVerbosity
- isValidPath queryReferences queryPathInfo queryDeriver queryPathHash
- queryPathFromHashPart
- topoSortPaths computeFSClosure followLinksToStorePath exportPaths importPaths
- hashPath hashFile hashString convertHash
- signString checkSignature
- addToStore makeFixedOutputPath
- derivationFromPath
- addTempRoot
- getBinDir getStoreDir
- queryRawRealisation
-);
-
-our $VERSION = '0.15';
-
-sub backtick {
- open(RES, "-|", @_) or die;
- local $/;
- my $res = || "";
- close RES or die;
- return $res;
-}
-
-require XSLoader;
-XSLoader::load('Nix::Store', $VERSION);
-
-1;
-__END__
diff --git a/perl/lib/Nix/Store.xs b/perl/lib/Nix/Store.xs
deleted file mode 100644
index e96885e4c..000000000
--- a/perl/lib/Nix/Store.xs
+++ /dev/null
@@ -1,373 +0,0 @@
-#include "config.h"
-
-#include "EXTERN.h"
-#include "perl.h"
-#include "XSUB.h"
-
-/* Prevent a clash between some Perl and libstdc++ macros. */
-#undef do_open
-#undef do_close
-
-#include "derivations.hh"
-#include "globals.hh"
-#include "store-api.hh"
-#include "util.hh"
-#include "crypto.hh"
-
-#include
-#include
-
-
-using namespace nix;
-
-
-static ref store()
-{
- static std::shared_ptr _store;
- if (!_store) {
- try {
- initLibStore();
- _store = openStore();
- } catch (Error & e) {
- croak("%s", e.what());
- }
- }
- return ref(_store);
-}
-
-
-MODULE = Nix::Store PACKAGE = Nix::Store
-PROTOTYPES: ENABLE
-
-
-#undef dNOOP // Hack to work around "error: declaration of 'Perl___notused' has a different language linkage" error message on clang.
-#define dNOOP
-
-
-void init()
- CODE:
- store();
-
-
-void setVerbosity(int level)
- CODE:
- verbosity = (Verbosity) level;
-
-
-int isValidPath(char * path)
- CODE:
- try {
- RETVAL = store()->isValidPath(store()->parseStorePath(path));
- } catch (Error & e) {
- croak("%s", e.what());
- }
- OUTPUT:
- RETVAL
-
-
-SV * queryReferences(char * path)
- PPCODE:
- try {
- for (auto & i : store()->queryPathInfo(store()->parseStorePath(path))->references)
- XPUSHs(sv_2mortal(newSVpv(store()->printStorePath(i).c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * queryPathHash(char * path)
- PPCODE:
- try {
- auto s = store()->queryPathInfo(store()->parseStorePath(path))->narHash.to_string(Base32, true);
- XPUSHs(sv_2mortal(newSVpv(s.c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * queryDeriver(char * path)
- PPCODE:
- try {
- auto info = store()->queryPathInfo(store()->parseStorePath(path));
- if (!info->deriver) XSRETURN_UNDEF;
- XPUSHs(sv_2mortal(newSVpv(store()->printStorePath(*info->deriver).c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * queryPathInfo(char * path, int base32)
- PPCODE:
- try {
- auto info = store()->queryPathInfo(store()->parseStorePath(path));
- if (!info->deriver)
- XPUSHs(&PL_sv_undef);
- else
- XPUSHs(sv_2mortal(newSVpv(store()->printStorePath(*info->deriver).c_str(), 0)));
- auto s = info->narHash.to_string(base32 ? Base32 : Base16, true);
- XPUSHs(sv_2mortal(newSVpv(s.c_str(), 0)));
- mXPUSHi(info->registrationTime);
- mXPUSHi(info->narSize);
- AV * refs = newAV();
- for (auto & i : info->references)
- av_push(refs, newSVpv(store()->printStorePath(i).c_str(), 0));
- XPUSHs(sv_2mortal(newRV((SV *) refs)));
- AV * sigs = newAV();
- for (auto & i : info->sigs)
- av_push(sigs, newSVpv(i.c_str(), 0));
- XPUSHs(sv_2mortal(newRV((SV *) sigs)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-SV * queryRawRealisation(char * outputId)
- PPCODE:
- try {
- auto realisation = store()->queryRealisation(DrvOutput::parse(outputId));
- if (realisation)
- XPUSHs(sv_2mortal(newSVpv(realisation->toJSON().dump().c_str(), 0)));
- else
- XPUSHs(sv_2mortal(newSVpv("", 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * queryPathFromHashPart(char * hashPart)
- PPCODE:
- try {
- auto path = store()->queryPathFromHashPart(hashPart);
- XPUSHs(sv_2mortal(newSVpv(path ? store()->printStorePath(*path).c_str() : "", 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * computeFSClosure(int flipDirection, int includeOutputs, ...)
- PPCODE:
- try {
- StorePathSet paths;
- for (int n = 2; n < items; ++n)
- store()->computeFSClosure(store()->parseStorePath(SvPV_nolen(ST(n))), paths, flipDirection, includeOutputs);
- for (auto & i : paths)
- XPUSHs(sv_2mortal(newSVpv(store()->printStorePath(i).c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * topoSortPaths(...)
- PPCODE:
- try {
- StorePathSet paths;
- for (int n = 0; n < items; ++n) paths.insert(store()->parseStorePath(SvPV_nolen(ST(n))));
- auto sorted = store()->topoSortPaths(paths);
- for (auto & i : sorted)
- XPUSHs(sv_2mortal(newSVpv(store()->printStorePath(i).c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * followLinksToStorePath(char * path)
- CODE:
- try {
- RETVAL = newSVpv(store()->printStorePath(store()->followLinksToStorePath(path)).c_str(), 0);
- } catch (Error & e) {
- croak("%s", e.what());
- }
- OUTPUT:
- RETVAL
-
-
-void exportPaths(int fd, ...)
- PPCODE:
- try {
- StorePathSet paths;
- for (int n = 1; n < items; ++n) paths.insert(store()->parseStorePath(SvPV_nolen(ST(n))));
- FdSink sink(fd);
- store()->exportPaths(paths, sink);
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-void importPaths(int fd, int dontCheckSigs)
- PPCODE:
- try {
- FdSource source(fd);
- store()->importPaths(source, dontCheckSigs ? NoCheckSigs : CheckSigs);
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * hashPath(char * algo, int base32, char * path)
- PPCODE:
- try {
- Hash h = hashPath(parseHashType(algo), path).first;
- auto s = h.to_string(base32 ? Base32 : Base16, false);
- XPUSHs(sv_2mortal(newSVpv(s.c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * hashFile(char * algo, int base32, char * path)
- PPCODE:
- try {
- Hash h = hashFile(parseHashType(algo), path);
- auto s = h.to_string(base32 ? Base32 : Base16, false);
- XPUSHs(sv_2mortal(newSVpv(s.c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * hashString(char * algo, int base32, char * s)
- PPCODE:
- try {
- Hash h = hashString(parseHashType(algo), s);
- auto s = h.to_string(base32 ? Base32 : Base16, false);
- XPUSHs(sv_2mortal(newSVpv(s.c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * convertHash(char * algo, char * s, int toBase32)
- PPCODE:
- try {
- auto h = Hash::parseAny(s, parseHashType(algo));
- auto s = h.to_string(toBase32 ? Base32 : Base16, false);
- XPUSHs(sv_2mortal(newSVpv(s.c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * signString(char * secretKey_, char * msg)
- PPCODE:
- try {
- auto sig = SecretKey(secretKey_).signDetached(msg);
- XPUSHs(sv_2mortal(newSVpv(sig.c_str(), sig.size())));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-int checkSignature(SV * publicKey_, SV * sig_, char * msg)
- CODE:
- try {
- STRLEN publicKeyLen;
- unsigned char * publicKey = (unsigned char *) SvPV(publicKey_, publicKeyLen);
- if (publicKeyLen != crypto_sign_PUBLICKEYBYTES)
- throw Error("public key is not valid");
-
- STRLEN sigLen;
- unsigned char * sig = (unsigned char *) SvPV(sig_, sigLen);
- if (sigLen != crypto_sign_BYTES)
- throw Error("signature is not valid");
-
- RETVAL = crypto_sign_verify_detached(sig, (unsigned char *) msg, strlen(msg), publicKey) == 0;
- } catch (Error & e) {
- croak("%s", e.what());
- }
- OUTPUT:
- RETVAL
-
-
-SV * addToStore(char * srcPath, int recursive, char * algo)
- PPCODE:
- try {
- auto method = recursive ? FileIngestionMethod::Recursive : FileIngestionMethod::Flat;
- auto path = store()->addToStore(std::string(baseNameOf(srcPath)), srcPath, method, parseHashType(algo));
- XPUSHs(sv_2mortal(newSVpv(store()->printStorePath(path).c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * makeFixedOutputPath(int recursive, char * algo, char * hash, char * name)
- PPCODE:
- try {
- auto h = Hash::parseAny(hash, parseHashType(algo));
- auto method = recursive ? FileIngestionMethod::Recursive : FileIngestionMethod::Flat;
- auto path = store()->makeFixedOutputPath(name, FixedOutputInfo {
- .method = method,
- .hash = h,
- .references = {},
- });
- XPUSHs(sv_2mortal(newSVpv(store()->printStorePath(path).c_str(), 0)));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * derivationFromPath(char * drvPath)
- PREINIT:
- HV *hash;
- CODE:
- try {
- Derivation drv = store()->derivationFromPath(store()->parseStorePath(drvPath));
- hash = newHV();
-
- HV * outputs = newHV();
- for (auto & i : drv.outputsAndOptPaths(*store())) {
- hv_store(
- outputs, i.first.c_str(), i.first.size(),
- !i.second.second
- ? newSV(0) /* null value */
- : newSVpv(store()->printStorePath(*i.second.second).c_str(), 0),
- 0);
- }
- hv_stores(hash, "outputs", newRV((SV *) outputs));
-
- AV * inputDrvs = newAV();
- for (auto & i : drv.inputDrvs.map)
- av_push(inputDrvs, newSVpv(store()->printStorePath(i.first).c_str(), 0)); // !!! ignores i->second
- hv_stores(hash, "inputDrvs", newRV((SV *) inputDrvs));
-
- AV * inputSrcs = newAV();
- for (auto & i : drv.inputSrcs)
- av_push(inputSrcs, newSVpv(store()->printStorePath(i).c_str(), 0));
- hv_stores(hash, "inputSrcs", newRV((SV *) inputSrcs));
-
- hv_stores(hash, "platform", newSVpv(drv.platform.c_str(), 0));
- hv_stores(hash, "builder", newSVpv(drv.builder.c_str(), 0));
-
- AV * args = newAV();
- for (auto & i : drv.args)
- av_push(args, newSVpv(i.c_str(), 0));
- hv_stores(hash, "args", newRV((SV *) args));
-
- HV * env = newHV();
- for (auto & i : drv.env)
- hv_store(env, i.first.c_str(), i.first.size(), newSVpv(i.second.c_str(), 0), 0);
- hv_stores(hash, "env", newRV((SV *) env));
-
- RETVAL = newRV_noinc((SV *)hash);
- } catch (Error & e) {
- croak("%s", e.what());
- }
- OUTPUT:
- RETVAL
-
-
-void addTempRoot(char * storePath)
- PPCODE:
- try {
- store()->addTempRoot(store()->parseStorePath(storePath));
- } catch (Error & e) {
- croak("%s", e.what());
- }
-
-
-SV * getBinDir()
- PPCODE:
- XPUSHs(sv_2mortal(newSVpv(settings.nixBinDir.c_str(), 0)));
-
-
-SV * getStoreDir()
- PPCODE:
- XPUSHs(sv_2mortal(newSVpv(settings.nixStore.c_str(), 0)));
diff --git a/perl/lib/Nix/Utils.pm b/perl/lib/Nix/Utils.pm
deleted file mode 100644
index 44955a706..000000000
--- a/perl/lib/Nix/Utils.pm
+++ /dev/null
@@ -1,47 +0,0 @@
-package Nix::Utils;
-
-use utf8;
-use File::Temp qw(tempdir);
-
-our @ISA = qw(Exporter);
-our @EXPORT = qw(checkURL uniq writeFile readFile mkTempDir);
-
-$urlRE = "(?: [a-zA-Z][a-zA-Z0-9\+\-\.]*\:[a-zA-Z0-9\%\/\?\:\@\&\=\+\$\,\-\_\.\!\~\*]+ )";
-
-sub checkURL {
- my ($url) = @_;
- die "invalid URL '$url'\n" unless $url =~ /^ $urlRE $ /x;
-}
-
-sub uniq {
- my %seen;
- my @res;
- foreach my $name (@_) {
- next if $seen{$name};
- $seen{$name} = 1;
- push @res, $name;
- }
- return @res;
-}
-
-sub writeFile {
- my ($fn, $s) = @_;
- open TMP, ">$fn" or die "cannot create file '$fn': $!";
- print TMP "$s" or die;
- close TMP or die;
-}
-
-sub readFile {
- local $/ = undef;
- my ($fn) = @_;
- open TMP, "<$fn" or die "cannot open file '$fn': $!";
- my $s = ;
- close TMP or die;
- return $s;
-}
-
-sub mkTempDir {
- my ($name) = @_;
- return tempdir("$name.XXXXXX", CLEANUP => 1, DIR => $ENV{"TMPDIR"} // $ENV{"XDG_RUNTIME_DIR"} // "/tmp")
- || die "cannot create a temporary directory";
-}
diff --git a/perl/lib/Nix/meson.build b/perl/lib/Nix/meson.build
deleted file mode 100644
index 6810622e3..000000000
--- a/perl/lib/Nix/meson.build
+++ /dev/null
@@ -1,58 +0,0 @@
-store_xs_cpp = custom_target(
- input : 'Store.xs',
- output : 'Store.cc',
- command : [
- xsubpp,
- '@INPUT@',
- '-output',
- '@OUTPUT@',
- ],
- build_by_default : true,
-)
-
-soname_args = []
-if cxx.get_linker_id() in ['ld.bfd', 'ld.gold']
- soname_args = ['-Wl,-soname=Store.so']
-endif
-
-perl_libstore = shared_module(
- 'Store',
- store_xs_cpp,
- # This library does NOT get the normal libprefix. it's just `Store.so`, not `libStore.so`.
- name_prefix : '',
- dependencies : [
- libstore,
- sodium,
- perl_include,
- ],
- link_args : [
- # Nix doesn't provide a pkg-config file for libutil.
- '-lnixutil',
- soname_args,
- ],
- install : true,
- install_dir : perl_libdir / 'auto/Nix/Store',
-)
-
-config_pm = configure_file(
- input : 'Config.pm.in',
- output : 'Config.pm',
- configuration : {
- 'PACKAGE_VERSION': meson.project_version(),
- },
-)
-
-nix_perl_sources = files(
- 'Store.pm',
- 'Manifest.pm',
- 'SSH.pm',
- 'CopyClosure.pm',
- 'Utils.pm',
-)
-
-install_data(
- nix_perl_sources,
- config_pm,
- install_dir : perl_libdir / 'Nix',
- preserve_path : true,
-)
diff --git a/perl/meson.build b/perl/meson.build
deleted file mode 100644
index 75c7c2c79..000000000
--- a/perl/meson.build
+++ /dev/null
@@ -1,69 +0,0 @@
-project('lix-perl', 'cpp',
- version : run_command('bash', '-c', 'echo -n $(cat ../.version)$VERSION_SUFFIX', check : true).stdout().strip(),
- default_options : [
- 'cpp_std=c++2a',
- # TODO(Qyriad): increase the warning level
- 'debug=true',
- # FIXME(Qyriad): should this be -O2? The main nix build was switched to -O2 in 3c5234430
- 'optimization=3',
- ],
-)
-
-fs = import('fs')
-
-prefix = get_option('prefix')
-libdir = get_option('libdir')
-if not fs.is_absolute(libdir)
- libdir = prefix / libdir
-endif
-
-cxx = meson.get_compiler('cpp')
-
-# Really version 5.8.0, but Perl's version string is of the form
-# "This is perl 5, version 38, subversion 2", for 5.38.2, so as far
-# as Meson is concerned, the version of Perl we need is 8 or greater.
-perl = find_program('perl', version : '>=8')
-
-# "compiler to convert Perl XS code into C code"
-xsubpp = find_program('xsubpp')
-
-perl_version = run_command(
- perl,
- '-e',
- 'use Config; print $Config{version};',
- capture : true,
- check : true,
-).stdout()
-perl_arch_name = run_command(
- perl,
- '-e',
- 'use Config; print $Config{archname};',
- capture : true,
- check : true,
-).stdout()
-
-perl_libdir = f'@libdir@/perl5/site_perl/@perl_version@/@perl_arch_name@'
-
-perl_incdir = run_command(
- perl,
- '-e',
- 'use Config; print $Config{archlibexp};',
- capture : true,
- check : true,
-).stdout() + '/CORE'
-
-perl_include = declare_dependency(
- # This must have is_system : true, or #include "config.h" will get perl's config.h
- # instead of Nix's.
- include_directories : include_directories(perl_incdir, is_system : true),
-)
-
-sodium = dependency('libsodium', 'sodium', required : true)
-
-if cxx.get_linker_id() in ['ld.bfd', 'ld.gold']
- add_project_link_arguments('-Wl,--no-copy-dt-needed-entries', language : 'cpp')
-endif
-
-libstore = dependency('nixstore', 'nix-store', required : true)
-
-subdir('lib/Nix')
diff --git a/precompiled-headers.h b/precompiled-headers.h
deleted file mode 100644
index f52f1cab8..000000000
--- a/precompiled-headers.h
+++ /dev/null
@@ -1,60 +0,0 @@
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include
-#include