bernardo/Nomarchy
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(install): carry the full system build closure on the ISO

Browse Source 
Round 6 still hit a from-source cascade: every per-machine drv (units,
initrd pieces, dbus config, modules-shrunk) needs its own build tools
(lndir, builder.pl, kmod-dev, nuke-refs, libxslt-bin, …), one level
deeper than targeted inputDerivation pins reach. Use the documented
mechanism instead: system.includeBuildDependencies = true on the
representative install pin. Bigger ISO, networkless installs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Bernardo Magri
2026-06-10 19:41:37 +01:00
parent ecf94e84ab
commit 609bb7e7dc
1 changed files with 10 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
flake.nix
View File

@@ -229,6 +229,14 @@
(./templates/downstream + "/hardware-configuration.nix")
(./templates/downstream + "/system.nix")
({ lib, ... }: {
# The whole BUILD closure rides along: a real
# install rebuilds the per-machine drvs (etc,
# units, initrd, …) whose builders need tools
# from no runtime closure. This is the documented
# offline-rebuild mechanism; it is what makes the
# ISO big and the install networkless.
system.includeBuildDependencies = true;
nomarchy.system.snapper.enable = true;
nomarchy.system.greeter.autoLogin = username;
swapDevices = [{ device = "/swap/swapfile"; }];
@@ -250,15 +258,8 @@
representativeInstall.config.system.build.toplevel
template.homeConfigurations.${username}.activationPackage
# A real install rebuilds the few drvs that embed the
# user's hostname/username/UUIDs (etc, initrd, toplevel,
# HM activation). Their BUILDERS need tools that are in
# no runtime closure (etc uses python3-minimal, the
# initrd its packing tools) — inputDerivation pins each
# drv's full build inputs.
representativeInstall.config.system.build.toplevel.inputDerivation
representativeInstall.config.system.build.etc.inputDerivation
representativeInstall.config.system.build.initialRamdisk.inputDerivation
# The HM activation is rebuilt per-username in the
# installer chroot; pin its build inputs too.
template.homeConfigurations.${username}.activationPackage.inputDerivation
# …and one representative disko script: its tool closure