Marcelo Alcantara
caac8448be
omacom/omarchy#13362 sets HOOKS per platform inside 00-omarchy-hooks.conf, with no column-0 HOOKS= line, so the aarch64 build failed on it; settings-dev tracks quattro automatically and would break as soon as it lands. Wrap only a single-line HOOKS=(...), refuse any other column-0 HOOKS=, then source the shipped files onto a Mac line and a stock line: the Mac line must come through unchanged and the stock one must not. Back up 00-omarchy-hooks.conf when it ships, and refuse it without the omarchy-hw-platform copy it asks. The test now uses the real v4.0.4 hooks file, #13362's two files and omarchy-mac-boot's 90-94 fragments, and covers upgrades over a hand-restored file.
19 lines
878 B
Plaintext
19 lines
878 B
Plaintext
# Plymouth draws the disk password prompt and the boot splash, as on x86
|
|
# Omarchy. It goes right after systemd so its initrd units order correctly,
|
|
# only when the hook is installed, and never twice.
|
|
if [[ -f /usr/lib/initcpio/install/plymouth && " ${HOOKS[*]} " != *" plymouth "* ]]; then
|
|
_omarchy_mac_plymouth_hooks=()
|
|
_omarchy_mac_plymouth_added=false
|
|
for _omarchy_mac_plymouth_hook in "${HOOKS[@]}"; do
|
|
_omarchy_mac_plymouth_hooks+=("$_omarchy_mac_plymouth_hook")
|
|
if [[ $_omarchy_mac_plymouth_hook == systemd && $_omarchy_mac_plymouth_added == false ]]; then
|
|
_omarchy_mac_plymouth_hooks+=(plymouth)
|
|
_omarchy_mac_plymouth_added=true
|
|
fi
|
|
done
|
|
if [[ $_omarchy_mac_plymouth_added == true ]]; then
|
|
HOOKS=("${_omarchy_mac_plymouth_hooks[@]}")
|
|
fi
|
|
unset _omarchy_mac_plymouth_hooks _omarchy_mac_plymouth_added _omarchy_mac_plymouth_hook
|
|
fi
|