Repository navigation
Conversation
6f47089 to
6dba7e7
Compare
The Install submenus offer their entries on every machine, but Omarchy's repositories publish x86_64 only and Arch Linux ARM does not build everything extra does. The entries carry a disabled: guard, which dims software already installed; nothing asks whether it can be installed at all. On aarch64 those entries run omarchy-pkg-add against a name pacman cannot resolve: a terminal opens, pacman reports the target as missing, and the entry is still there to pick again. From pacman.log, none of these is followed by a transaction: Running 'pacman -S --noconfirm --needed lmstudio-bin' Running 'pacman -S --noconfirm --needed ollama' Running 'pacman -S --noconfirm --needed ghostty' omarchy-pkg-available asks the sync databases the same question omarchy-pkg-add will put to pacman, so a when: guard drops an entry only where the install could not have worked. Ghostty and LM Studio have nothing to fall back to on aarch64 -- lmstudio-bin is arch=x86_64, and ghostty has no -bin package and a nightly that is x86_64 only -- so they are hidden there and untouched everywhere else. The other three terminals are guarded the same way and stay visible wherever their package resolves. Ollama does have a fallback. ollama-bin packages upstream's official linux-arm64 release and provides ollama, so the entry stays and the install reaches for it when the repo has nothing. That moves the GPU selection out of the menu action and into omarchy-install-ai-ollama, beside the other AI installers. Only entries whose installer is pacman-only and whose package lives in a repository are guarded. The AUR-backed entries are left alone: pacman -Si never resolves an AUR package, so guarding those would hide them on x86_64 too. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ALLhsWEVznJX5Js4CM59ZV
6dba7e7 to
0d0ec35
Compare
Automated AI review
Outcome: Remove > AI > Ollama leaves the fallback's Removing Ollama leaves
|
|
Nice ARM/out-of-tree package gate — |
The Install submenus offer their entries on every machine, but Omarchy's own repositories publish x86_64 only and Arch Linux ARM does not build everything
extradoes. Each entry carries adisabled:guard, which dims software already installed — nothing asks whether it can be installed at all.On aarch64 those entries run
omarchy-pkg-addagainst a name pacman cannot resolve: a terminal opens, pacman reports the target as missing, and the entry is still sitting there to pick again. From/var/log/pacman.log— none of these is followed by a transaction:omarchy-pkg-availableasks the sync databases the same questionomarchy-pkg-addwill put to pacman, so awhen:guard drops an entry only where the install could not have worked.Ghostty and LM Studio have nothing to fall back to on aarch64 —
lmstudio-binisarch=('x86_64'), and ghostty has no-binpackage whileghostty-nightly-binisarch=(x86_64). Both are hidden there and untouched everywhere else. The other three terminals are guarded the same way and stay visible wherever their package resolves.Ollama does have a fallback:
ollama-binisarch=('x86_64' 'aarch64'), packages upstream's officialollama-linux-arm64release, andprovides=("ollama"). The entry stays and the install reaches for it when the repo has nothing, which moves the GPU selection out of the menu action intoomarchy-install-ai-ollama, beside the other AI installers.disabled:is untouched throughout, so installed software still reads as installed rather than disappearing from the list it was installed from.Scope
Only entries whose installer is pacman-only and whose package lives in a repository are guarded. The AUR-backed entries (
brave-bin,zen-browser-bin,cursor-bin,visual-studio-code-bin,nordvpn-bin,once-bin, …) are deliberately left alone:pacman -Sinever resolves an AUR package, so guarding those would hide them on x86_64 too.That leaves an open question I can't answer from an aarch64 machine: if the
[omarchy]repo republishes those*-binpackages for x86_64, they'd be guardable as well. Myomarchy.dbis an empty 381-byte file because there's no aarch64 content, so someone on x86_64 would need to confirm before extending it.test/clipasses, includingall executable bins have slim self-documenting metadata, andomarchy install ai ollamaroutes alongside the other AI installers.🤖 Generated with Claude Code
https://claude.ai/code/session_01ALLhsWEVznJX5Js4CM59ZV