From 1b92b7f5be8683a71c9d176d5a5fc859518143b3 Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Sat, 29 Aug 2026 18:03:57 +0200 Subject: [PATCH] Correct the dev-link help now that Plymouth follows the link omarchy-dev-link told people /usr/share/plymouth was not covered by a link and to reach for omarchy-dev-pkg-test. Since the publisher authorizes a dev-linked checkout out of the root-owned /etc/omarchy.conf, the Plymouth and SDDM themes are republished from the checkout like every other $OMARCHY_PATH-resolved tree, so the help was left describing the old behaviour. Co-Authored-By: Claude Opus 5 (1M context) --- bin/omarchy-dev-link | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/bin/omarchy-dev-link b/bin/omarchy-dev-link index ccaa404f..b09473b5 100755 --- a/bin/omarchy-dev-link +++ b/bin/omarchy-dev-link @@ -34,8 +34,12 @@ systemd, shell, or app-launcher environment; reboot to make every layer agree. Affects only \$OMARCHY_PATH-resolved trees: bin/, default/, shell/, themes/, applications/, config/. Files installed at fixed system paths (/etc/, /usr/lib/systemd/, udev rule bodies, /etc/skel after user -creation, /usr/share/plymouth) are NOT covered — for those, use -omarchy-dev-pkg-test to build and install the package from the checkout. +creation) are NOT covered — for those, use omarchy-dev-pkg-test to build +and install the package from the checkout. + +The Plymouth and SDDM themes under /usr/share are the exception: omarchy +plymouth set and omarchy refresh plymouth republish them from the checkout, +reading this link's authorization out of the root-owned /etc/omarchy.conf. Also writes $sudoers_file so sudo resolves omarchy-* from the checkout instead of the packaged copies. That part takes effect