max / alloy
- Co-Authored-By
- Claude Opus 5 (1M context) <noreply@anthropic.com>
1 file changed,
+1 insertion,
-1 deletion
| @@ -54,7 +54,7 @@ | |||
| 54 | 54 | ||
| 55 | 55 | **minisign is absent.** Both Linux release recipes call `dist/sign-artifacts.sh`, which hard-fails when minisign is not on PATH, and the recipe step aborts the run. Mechanical fix, one word in the base package block. Fedora 43 carries 0.12. Base rather than client: signing is a build-host act. | |
| 56 | 56 | ||
| 57 | - | **sccache is absent, and the tree-wide cargo config makes it mandatory.** `~/Code/.cargo/config.toml` sets `rustc-wrapper = "sccache"` unconditionally. A missing wrapper is fatal at the version probe, before any compilation starts, so on a fresh install every cargo command under `~/Code` dies instantly. Measured by pointing the wrapper at a nonexistent binary. sccache is a cargo-installed binary in `~/.cargo/bin`, not a system package, so this is a `$HOME` restore rather than an image change. The config's own comment says the two lines are removable, so dropping sccache is a real option rather than a forced dependency. | |
| 57 | + | **sccache is absent, and that is no longer fatal.** The tree-wide cargo config used to set `rustc-wrapper = "sccache"` unconditionally, and a missing wrapper is fatal at the version probe before any compilation starts, so on a fresh install every cargo command under `~/Code` died instantly. Fixed 2026-08-21: `rustc-wrapper` is out of the tracked file and `RUSTC_WRAPPER` is exported per machine from the shell profile, which is the only conditional cargo offers. A machine without sccache now builds; it just builds cold. sccache is a cargo-installed binary in `~/.cargo/bin`, not a system package, so restoring it is a `$HOME` step rather than an image change, and it is worth restoring: measured on fw13 the same day, 18273 cached objects over 13G and a 71% hit rate on a controlled cross-project test. | |
| 58 | 58 | ||
| 59 | 59 | **node and npm are absent from a default mint, and `LANGS=rust,js` is what supplies them.** Sando's `code_smoke` gate builds two frontends with `npm run build` before it creates a database or boots anything, and the config text says outright that this is the one place a frontend failure is fatal. It is fatal there because the MNW server's `build.rs` deliberately is not: with no node it emits a warning and lets the Rust build succeed against whatever `static/dist/` already holds, which would silently ship the previous build's JavaScript. Closed 2026-08-21: the `LANGS` validator carries a `js` arm now, so a machine in the build-host role mints with `LANGS=rust,js` and every other mint pays nothing. What LANGS a given machine starts from is the builder's choice, not a default this file sets. The arm installs with `install_weak_deps=False`, which leaves `nodejs-full-i18n` behind; Fedora 43's nodejs is 22.22.2 against fw13's current 24.18.0, and neither frontend declares an `engines` field, so it is still unverified that the two bundles build under 22. | |
| 60 | 60 |