nixpkgs/pkgs
Adam Joseph d7aad24531 express #208478 as assertions
PR #208478 added a lot of documentation about which packages were
rebuilt in each stage of the stdenv bootstrap.  However nothing
checks that these comments agree with reality; they can bitrot over
time.  This PR rewrites those comments as assertions, so they cannot
bitrot.

This conversion did expose some ambiguity in our scheme for naming
the stages.   Suppose that `pkgs.stdenv.name=="stdenv-stage4", then
which of these is "the stage4 coreutils"?

```
pkgs.coreutils
pkgs.stdenv.__bootPackages.coreutils
```

The choice is arbitrary, and both choices have confusing corner
cases.  We should revisit this at some point.
2023-02-20 23:20:30 -08:00
..
applications Merge staging-next into staging 2023-02-13 18:01:55 +00:00
build-support Merge staging-next into staging 2023-02-13 18:01:55 +00:00
common-updater
data Merge master into staging-next 2023-02-13 06:01:30 +00:00
desktops Merge master into staging-next 2023-02-13 06:01:30 +00:00
development gtest: ensure C++17 support for aarch64 (#215767) 2023-02-13 15:31:27 -05:00
games
misc Merge master into staging-next 2023-02-12 12:01:29 +00:00
os-specific Merge pull request #214207 from Artturin/ssytemdbuildbash1 2023-02-13 22:34:23 +02:00
pkgs-lib
servers Merge staging-next into staging 2023-02-13 18:01:55 +00:00
shells Merge #214010: staging-next 2023-02-01 2023-02-13 15:42:23 +01:00
stdenv express #208478 as assertions 2023-02-20 23:20:30 -08:00
test
tools Merge staging-next into staging 2023-02-13 18:01:55 +00:00
top-level Merge staging-next into staging 2023-02-13 18:01:55 +00:00