README: lay-person-friendly install paths (PKG, Homebrew, install.sh) + Tahoe safety warnings #5
Loading…
Reference in a new issue
No description provided.
Delete branch "readme-installation-paths"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Rewrites the README so that anyone — including someone who has never used Terminal — can pick the right install path for their setup. Documents all three install methods that exist after PR #4 + first release
v2026.05.0:brew tap ojars/pareizrakstiba … && brew install --cask apostrofs(now installable, cask bumped to2026.05.0in homebrew-pareizrakstiba commit0856cbf).install.sh— clone-and-run per-user, no admin, immediate availability.Leads with a comparison table (install location / admin password / Tahoe behavior) so users self-select before reading procedure detail.
Key additions vs current README
Three corrections / safety notes surfaced during the 2026-05-09 packaging + activation sessions:
/Library/Keyboard Layouts/only at login. PKG and Homebrew installs require logout/login before the layout registers in the Input Sources picker. The per-user path~/Library/Keyboard Layouts/is hot-rescanned, soinstall.shworks immediately. Recommended for single-user Tahoe setups.TSMSelectInputSource→CFStringCompare(NULL)SIGSEGV — happens equally with./uninstall.sh,brew uninstall --cask apostrofs, or manualsudo rm). Loud warning + remediation (switch layout first) added immediately above the Uninstall section. The same gotcha is documented in the operator infra-docs §10 row.Structural changes
chmod +x install.shcallout for the ZIP path (git preserves the executable bit, ZIP does not)Test plan
6a7e4a8e…)brew install --cask apostrofsis real (cask is no longer placeholder; tap commit0856cbf)install.shpath verified working today (per-user install activated, Shift+3=#, Alt+4=€)Notes for reviewer
The Forgejo Actions release workflow (
release.yml) failed on thev2026.05.0tag push because${{ secrets.GITHUB_TOKEN }}does not have release-write scope on this Forgejo instance (spell-checker uses a manually-configuredFORGEJO_RELEASE_TOKENfor this reason). The release for this version was created manually via API from the operator MacBook. Will be tracked as a follow-up — not a blocker for this README PR. The README intentionally does not promise that releases happen automatically on tag push.🤖 Generated with Claude Code
Self-review (auto-Teika not wired up here per infra-docs#120)
Reviewed: 2 commits, both on this branch.
f6ae5a5— README rewrite (3 install paths + Tahoe safety warnings + shared Activate/Verify/Uninstall sections)2aa0971—uninstall.shhardening: refuses to delete.keylayoutifLatvian (apostrofs)is the currently-selected input source. Supports--forceto bypass. Verified live: ran on a system where apostrofs IS active (perdefaults read com.apple.HIToolbox AppleSelectedInputSources), got the expected loud warning +exit 1, no terminal crash. The complement to the README warning — README helps users who read docs first, the script-level guard helps everyone else.Verified live in this session
6a7e4a8e4be0e1c73e009c3916c0ec844ba44eb2ab3485842d419dee8e111c4a)brew install --cask apostrofs→ cask is2026.05.0with real SHA (homebrew-pareizrakstiba0856cbf)install.shper-user path → activated and typing correctly today (Shift+3=#, Alt+4=€)uninstall.shsafety guard → triggers correctly when active source is apostrofs, refuses with exit 1bash -n uninstall.sh→ syntax OKDiff coverage
uninstall.shchange is additive: new safety check at the top, originalrmlogic unchanged.--forceflag preserves the old behavior verbatim. Backward compatible for any scripted uninstaller.Ready to merge.