cpp-netlib is unmaintained in both nixpkgs and upstream (last commit
september 2023). it requires us to pin several old versions, such as
llvm/clang 18 and boost 1.86. most of the changes in nixpkgs in recent
years have been treewides and zhf-style changes. this is not likely to
be sustainable going forward, and since it's a leaf, let's simply drop
this and avoid the trouble.
The aggregates evaluated every constituent twice, once inside a
single evaluator worker and once as its own job. Evaluating the
mergeable aggregate alone drops from 1.3 GB / 15 s to 73 MB / 0.4 s.
The unstable and darwin-tested aggregates still reference their constituents as derivations.
This forces the evaluation of ~47 jobs plus all stdenv bootstrap-tool sets
into the single evaluator worker that evals the aggregate.
On top of evaluating them again as their own jobs.
The NixOS jobsets switched to named constituents a while ago.
Hydra resolves the strings after evaluation and rewrites the aggregate to depend on the resolved builds,
so channel gating works as before.
Evaluating just the unstable aggregate drops from 1.5 GB / 19 s to 77 MB / 0.4 s:
nix-instantiate --eval --strict -A unstable.drvPath pkgs/top-level/release.nix
Note that nix-build -A unstable no longer builds the constituents, same as NixOS jobsets.
Tk 8.5 is end-of-life, and after the preceding commits nothing in the tree
asks for it.
The `broken` line in `generic.nix` goes too: it marked Tk on Darwin broken
when built against Tcl 8.5, which is now unreachable.
Assisted-by: Claude Code (Claude Opus 5)
Superseded by `mozart2`, which installs the same `oz`, `ozc`,
`ozemulator`, `ozengine` and `ozwish`, but builds 2.0.1 from source and is
maintained. This package was a binary snapshot of `2.0.0-alpha.0` from
2018, with no maintainers and `hydraPlatforms = [ ]`, and nothing in the
tree depended on it.
It was also the last consumer of Tcl/Tk 8.5 that could not be moved: as a
prebuilt binary, `bin/ozwish` has `DT_NEEDED` on `libtcl8.5.so` and
`libtk8.5.so`, so it could not be pointed at a newer Tcl.
Assisted-by: Claude Code (Claude Opus 5)
No in-tree use anymore; unclear if anything but monotone itself has a world-readable monotone network server
Local checkouts or locally adapted and vendored versions of fetchmtn are probably better option for any plausible use now
