From cf9f2745f3b8088652b767de3dc9e4085cb13577 Mon Sep 17 00:00:00 2001 From: Ryan Hughes Date: Wed, 20 May 2026 23:10:30 -0400 Subject: [PATCH] .automated_script.sh: arch-chroot pacman -S omarchy-base.packages after pacstrap omarchy's hard depends are now just the bricking set, not the full default install. After archinstall pacstraps the meta packages (which populates /etc/skel before user creation), install the rest of omarchy-base.packages in the chroot before running omarchy-install. --- configs/airootfs/root/.automated_script.sh | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/configs/airootfs/root/.automated_script.sh b/configs/airootfs/root/.automated_script.sh index 03971cf..ce462a7 100644 --- a/configs/airootfs/root/.automated_script.sh +++ b/configs/airootfs/root/.automated_script.sh @@ -47,10 +47,15 @@ install_arch() { } install_omarchy() { - # omarchy-installer (and its depends omarchy + omarchy-settings + omarchy-limine) - # are pacstrap'd by archinstall via the configurator's packages list, so they - # land BEFORE archinstall creates the user — meaning /etc/skel/.config is in - # place and the user's $HOME is seeded with the Omarchy defaults at creation. + # archinstall pacstrap'd omarchy + omarchy-installer (which pulls + # omarchy-settings + omarchy-limine) so /etc/skel is populated before user + # creation. But omarchy itself only hard-depends on the bricking set; the + # rest of the default install set lives in omarchy-base.packages and gets + # installed here in the chroot. + arch-chroot /mnt bash -c ' + mapfile -t pkgs < <(grep -v "^#\|^$" /usr/share/omarchy/install/omarchy-base.packages) + pacman -S --noconfirm --needed "${pkgs[@]}" + ' # Run the installer's offline path. omarchy-install execs /usr/share/omarchy/ # install.sh; OMARCHY_INSTALL_MODE=offline tells it the chroot install rules.