mirror of
https://github.com/archr-linux/Arch-R.git
synced 2026-07-12 18:19:42 -07:00
4a6cb841db
Original F5 plan was "one commit per emulator, refactor every hardcoded /storage/.config/<emu> reference". Audit showed that path appears across 22+ device quirk files, multiple start scripts and a handful of compiled-in patches per emulator. Mass refactor would be a huge diff with real regression risk and zero FHS gain on the running system because, with the bridge installed, the FHS path already resolves correctly. Pivot: install two umbrella bridges in the archr meta-package: /var/lib/archr/config -> /storage/.config /var/lib/archr/data -> /storage/.local/share Flip the ARCHR_CONFIG and ARCHR_DATA exports in 010-archr-fhs to the FHS paths so downstream scripts that already use the variables get the Arch-friendly surface for free. Update archr(7) ENVIRONMENT section: both variables now describe the FHS location as the actual address, with /storage/... noted as the rw-overlay substrate. Net effect: every /var/lib/archr/config/<emu> and /var/lib/archr/data/<emu> path exists at runtime and is writable. Inspection tools see a normal Arch layout. Hardcoded /storage/.config references in JELOS-inherited quirks and start scripts keep working because the symlink resolves both ways — writes through either path land in the same overlay file. Per-emulator refactors stay possible later, as incremental PRs, without a single big-bang. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>