nixpkgs/pkgs/stdenv
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
..
cross stdenv/cross: remove now-redundant file nativeBuildInput on mingw 2022-06-06 11:26:46 -07:00
custom
cygwin
darwin Merge master into staging-next 2023-02-07 06:01:28 +00:00
freebsd config.contentAddressedByDefault: init option 2022-04-27 23:21:32 +03:00
generic Merge staging-next into staging 2023-02-13 12:02:05 +00:00
linux express #208478 as assertions 2023-02-20 23:20:30 -08:00
native
nix stdenv/common-path.nix: move to stdenv/generic/ 2022-07-29 18:24:00 -04:00
tests stdenv.tests: Add succeedOnFailure 2022-11-14 19:03:35 +01:00
adapters.nix treewide: add names to all setup hooks 2023-01-19 15:00:36 +00:00
booter.nix llvmPackages_*: respect cc for target when choosing C++ flavour 2022-01-07 14:42:41 +01:00
default.nix stdenv: Simplify dispatch 2022-07-29 18:34:02 -04:00