feat: publish the corrected platform files

export_native now writes into exports/ by default, and beside each
platform's corrected file a report naming every change, where the run
printed five per kind. A new site page lists each platform with its
original file, a download of the corrected one and every corrected,
filled or withheld value. Each platform page links to its row.
This commit is contained in:
Abdessamad Derraz committed 2026-10-20 09:20:02 +02:00
1 parent 71b59eb2a3
commit ca13e6036d
8 files changed
+317 -7

No files matched your search

+8 -2
View File
@@ -339,10 +339,16 @@ the truth knows and the platform lacks are added.
```bash
python scripts/export_native.py --platform batocera --fetch # batocera-systems
python scripts/export_native.py --platform recalbox --fetch # es_bios.xml
python scripts/export_native.py --all --fetch --output-dir dist/upstream/
python scripts/export_native.py --all --fetch # every platform, into exports/
```
Seven of the formats carry code as well as data - Batocera's and ROCKNIX's
The corrected files are committed under `exports/<platform>/`, and
`exports/<platform>.json` names every change the run made. The site's
[corrected platform files](../exports.md) page is built from those reports:
one row per platform, a download link, and each corrected hash, filled hash
and withheld correction listed in full.
Seven of the formats carry code as well as data: Batocera's and ROCKNIX's
scripts, EmuDeck's shell library, BizHawk's C# database, RetroDECK's
component manifests, MiSTer's BiosDB, RetroPie's scriptmodules. Those are
patched from the platform's own file, which `--fetch` downloads once into