Preserve data across the Straywild transition

This commit is contained in:
Alexander Sellite 2026-08-25 22:18:20 -04:00
parent 737d1cf2e0
commit 98a27e2f53
28 changed files with 577 additions and 94 deletions

View file

@ -47,6 +47,10 @@ directory. The templates in `scripts/portmaster/` are authoritative.
upgraded. Device-local data, configuration, and cache remain under
`straywild/conf/data`, `straywild/conf/config`, and
`straywild/conf/cache`.
- A rebrand upgrade copies an existing `netfishing/conf/` tree into the new
`straywild/conf/` tree when the latter does not exist. It also reuses an
existing `ports/saves/netfishing/` data root rather than creating an empty
replacement. New installations use straywild paths exclusively.
- The archive must not contain `conf/`, saves, identities, logs, source files,
`.git`, or `.godot` content.
- Release downloads must publish only the canonical `straywild.zip` for this
@ -101,9 +105,9 @@ device directory and run:
--offline --no-check install ./straywild.zip
```
Before upgrading an existing installation, preserve
`/mnt/mmc/ports/straywild/conf/` and `/mnt/mmc/ports/saves/straywild/` on the
device. After installation:
Before upgrading an existing installation, preserve either the current
`/mnt/mmc/ports/straywild/` paths or the former `/mnt/mmc/ports/netfishing/`
paths on the device. After installation:
1. Confirm the installed executable and PCK hashes match the staged release.
2. Confirm HarbourMaster added its `# PORTMASTER:` installation signature to