potential-improvement — found while implementing #7.
New installs clone to ~/.local/share/omacase/repo so caches (generated/, backgrounds/, upstream/) sit beside the worktree. Existing public installs that already have .git in ~/.local/share/omacase are kept in place on purpose (zero users, forced migrate not worth the risk).
.gitignore is only defense in depth. Those machines still write theme caches into the updater checkout.
What would help
A documented, opt-in move:
git -C ~/.local/share/omacase is a worktree.- Move that worktree to
~/.local/share/omacase/repo.
- Leave
generated/, backgrounds/, upstream/ where they are (they become siblings).
- Relink
/opt/homebrew/bin/omacase at the new path.
omacase doctor (see sibling issue) can detect the old layout and print the recipe. Do not auto-migrate in boot.sh.
potential-improvement — found while implementing #7.
New installs clone to
~/.local/share/omacase/reposo caches (generated/,backgrounds/,upstream/) sit beside the worktree. Existing public installs that already have.gitin~/.local/share/omacaseare kept in place on purpose (zero users, forced migrate not worth the risk)..gitignoreis only defense in depth. Those machines still write theme caches into the updater checkout.What would help
A documented, opt-in move:
git -C ~/.local/share/omacaseis a worktree.~/.local/share/omacase/repo.generated/,backgrounds/,upstream/where they are (they become siblings)./opt/homebrew/bin/omacaseat the new path.omacase doctor(see sibling issue) can detect the old layout and print the recipe. Do not auto-migrate inboot.sh.