Spencer Bull
f6b9267b3b
A copy under /usr/lib/node_modules belongs to pacman, and upstream's updater refuses to write there, so neither `openclaw update` nor the Control UI's Update Gateway worked. The package now carries the release instead: the sha256-pinned npm tarball and the install-cli.sh that came in it, from which Omarchy seeds a copy under ~/.openclaw that updates itself.
18 lines
837 B
Plaintext
18 lines
837 B
Plaintext
post_install() {
|
|
printf "%s\n" \
|
|
"==> This is the release a self-updating OpenClaw starts from." \
|
|
"==> Set it up under ~/.openclaw: omarchy-install-openclaw-cli --now"
|
|
}
|
|
|
|
post_upgrade() {
|
|
# Earlier releases of this package were OpenClaw itself, under
|
|
# /usr/lib/node_modules/openclaw, and which of those a machine is leaving
|
|
# cannot be told from the version alone, since the upstream sync moves it.
|
|
# A root pacman hook has no session bus to move a user's OpenClaw, so
|
|
# Omarchy's migration does, and this says what happens either way.
|
|
printf "%s\n" \
|
|
"==> OpenClaw runs from ~/.openclaw and updates itself: openclaw update" \
|
|
"==> This package only sets the release new installs start from;" \
|
|
" omarchy update moves an OpenClaw still running from /usr there."
|
|
}
|