Ryan Hughes
b887d18b84
A pass over the install scripts, dev-tools commands, and Hyprland Lua files that I had stuffed with explain-everything preambles. Most of those rationales (which files ship where, why hyprctl setenv doesn't suffice, etc.) belong in commit messages or PR descriptions, not in code people have to read forever. Kept the few comments that document genuinely non-obvious behaviour: the keybind-env reason for hl.env in envs.lua, why the runtime PAM seds stay scripted in increase-lockout-limit, the chroot/--now distinction in chroot.sh, and the dev-pkg-test split-install reason.
19 lines
597 B
Bash
19 lines
597 B
Bash
# Starting the installer with OMARCHY_CHROOT_INSTALL=1 will put it into chroot mode
|
|
chrootable_systemctl_enable() {
|
|
if [[ -n ${OMARCHY_CHROOT_INSTALL:-} ]]; then
|
|
sudo systemctl enable $1
|
|
else
|
|
sudo systemctl enable --now $1
|
|
fi
|
|
}
|
|
|
|
# Like chrootable_systemctl_enable but never passes --now. Use for services
|
|
# we shouldn't (re)start mid-install (iwd interrupts the network; docker and
|
|
# power-profiles-daemon should defer to first boot).
|
|
chrootable_systemctl_enable_only() {
|
|
sudo systemctl enable $1
|
|
}
|
|
|
|
export -f chrootable_systemctl_enable
|
|
export -f chrootable_systemctl_enable_only
|