From 620941e18b19c6c92d8a239b175d7ab6786f216c Mon Sep 17 00:00:00 2001 From: dingo Date: Mon, 10 Aug 2026 17:37:31 +0700 Subject: [PATCH] install-assets: say which recipe installs the binaries, now that one does The header said the binaries were out of scope because `cargo` installs them. That was true when they were built by hand in three separate checkouts. The top-level justfile now installs all three, so the sentence pointed at the wrong thing -- someone looking for where cosmic-conf lands would have gone to cargo and found nothing. The scope is unchanged; only the reason was stale. --- tools/install-assets.sh | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/tools/install-assets.sh b/tools/install-assets.sh index 1c77e0c..80ae85e 100755 --- a/tools/install-assets.sh +++ b/tools/install-assets.sh @@ -24,8 +24,10 @@ # Per-user files. `cosmic-conf import-theme --assets` writes those, because they # depend on the installed theme and on $HOME; see PER_USER below for the list # and its owner. The cosmic-conf, cosmic-session and cosmic-comp binaries are -# also out of scope -- they are build outputs, so `cargo` installs them and -# comparing them byte-for-byte would only ever report a rebuild. +# also out of scope. The top-level justfile installs them -- cosmic-conf from +# its own `install` line, the other two from their component's recipe -- and +# they are build outputs, so comparing them byte-for-byte here would only ever +# report a rebuild. # # Usage: # tools/install-assets.sh install (needs write access to PREFIX)