The ISO carried only the three entry scripts launch.sh dispatches to;
tui-install.sh, its modules/ and the desktopenvs/ configs it deploys existed
solely inside the repo the installer clones at run time. A live environment
without working networking therefore ran the whole install and only failed at
the very last step, on a missing /home/<user>/Dotfiles/setup/tui-install.sh.
build.sh now embeds the entire setup/ tree at /installer (so every installer
script is on the ISO), plus a full repo snapshot — .git included, so a seeded
checkout is a real repo — at /installer/dotfiles. launch.sh moves there too
and the overlay/motd/docs follow; profiledef's file_permissions list is
repointed, which matters because mkarchiso hard-errors on an entry whose path
does not exist.
Tree resolution in both installers is now: an existing checkout, else a fresh
clone (online installs still get what is newest), else the ISO snapshot. Each
candidate is accepted only if it actually contains setup/tui-install.sh — the
old check was a bare `-d .git`, which any leftover or half-finished checkout
satisfied.
Sudo can no longer stop the install to ask for a password:
- before the chroot hands over to the TUI, the temporary NOPASSWD drop-in is
proven with `sudo -n true` and `sudo -n -v` (both forms modules rely on).
A rule that didn't apply now skips the TUI instead of stalling forever on a
hidden prompt, and the drop-in is removed on that path too rather than
being left behind as permanent passwordless sudo;
- tui-install.sh's root sudo shim moves to the top of the file, ahead of the
require_jq() bootstrap that shells out through sudo, so running it as root
straight from /installer never needs a real sudo binary.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Amir Alexander Abdelbaki
96f15c82af