Clarify Snapper packaging ownership

This commit is contained in:
Ryan Hughes
2026-06-21 02:25:11 -04:00
parent 78e5cc8195
commit ba0292e4cb
+7 -6
View File
@@ -19,9 +19,9 @@ conflicts=('omarchy-settings')
# limine + limine-mkinitcpio-hook + limine-snapper-sync + snapper are NOT in
# depends because this package gets installed into the live ISO env (for
# plymouth / /etc/skel seeding) where there is no ESP and the mkinitcpio hook
# would fail trying to deploy Limine. The bootloader stack is pulled in by
# the omarchy package on the target install, and by EARLY_BOOTSTRAP_PACKAGES
# in omarchy-iso/orchestrator/phases_impl.py for the target chroot.
# would fail trying to deploy Limine. The target omarchy package pulls in the
# full bootloader/snapshot stack; omarchy-iso only installs the early Limine
# pieces needed before the runtime package lands.
depends=(
'bash'
'curl'
@@ -252,9 +252,10 @@ EOF
done
fi
# default/** ships to /usr/share/omarchy/default/. The snapper template is
# additionally installed to /etc/snapper/config-templates/ below so snapper
# can pick it up at install time without separate handling.
# default/** ships to /usr/share/omarchy/default/. The Snapper template is
# additionally installed to /etc/snapper/config-templates/ for the standard
# Snapper template location; Omarchy target setup copies the default into the
# live root config.
install -d "$pkgdir/usr/share/omarchy/default"
cp -a default/. "$pkgdir/usr/share/omarchy/default/"