add void and chimera support

[tungstengmd]

title, i use void linux [and am planning to move to chimera] and this looks awesome, coude you maybe make the install script support them ?

[Nomadcxx]

I love void, been thinking about void and BSD/GhostBSD support for awhile but need some headspace to think about it, have been deep into another project (jellywatch) that will hopefully make it easier for people to migrate from plex to jellyfin with a few commands, tis more complex than expected.

I'll look into it man.

[Nomadcxx]

Investigation complete — Void is viable as the first target.

Summary

• Void Linux: greetd, cage, kitty, niri, sway all in official repos. Main gaps: installer only supports systemd (Void uses runit), no xbps detection, and no gSlapper package. Cage Lite (feat: Cagebreak greeter path + Hyprland deprecation (draft) #78) sidesteps the gslapper gap.
• Chimera: greetd + kitty in user repo, sway in main, uses apk + dinit — Phase 2 after Void.
• GhostBSD/FreeBSD: cage/sway/kitty in ports, but greetd port is very new (Jan 2026) and init is rc.d not systemd. Phase 3 / manual docs first.

Void gotcha: official greetd package uses user _greeter not greeter.

Design spec: docs/superpowers/specs/2026-06-18-issue-53-void-chimera-bsd-design.md

Recommended Phase 1: xbps + runit + Cage Lite default for Void.

[Nomadcxx]

Draft PR: Void Linux installer support (Phase 1)

#79

Phase 1 of this issue is implemented in the Go installer on branch feat/issue-53-void-bsd-investigation:

• Platform detection (systemd vs runit)
• xbps package installs (greetd, kitty, cage, niri, sway)
• Void _greeter account + /var/lib/_greeter path handling
• runit enable via /var/service/greetd symlink + agetty-tty1 disable
• gSlapper skip when cage is selected (recommended on Void)
• Docs: docs-src/getting-started/void-linux.md
• Static verify script: scripts/verify-void-installer.sh

Runit caveat — not runtime-validated yet

The PR is intentionally left as a draft because runit integration is the highest-risk piece and has not been tested on real Void hardware yet:

• greetd under runit (service start, run script, VT handoff)
• _greeter path substitution edge cases
• niri/sway path still requires gSlapper source build on Void

The verify script only checks source structure — it does not start services or exercise greetd at runtime. Expect iteration after someone runs the installer on an actual Void box.

Still out of scope (later phases)

• Chimera Linux (apk + dinit) — Phase 2
• GhostBSD / FreeBSD (pkg + rc.d) — Phase 3

Test plan (from PR)

• Fresh Void VM, go run ./cmd/installer/
• Confirm _greeter, greetd config paths, /var/service/greetd
• Reboot → sysc-greet on vt1
• Login with cage (TUI backgrounds)
• Optional: niri + gSlapper source build

Feedback from anyone running this on Void is very welcome before we undraft the PR.