chore: merge origin/main

This commit is contained in:
Abdessamad Derraz committed 2026-11-10 00:50:05 +01:00
commit 2dc427d5d0
106 files changed
+5458 -13655

No files matched your search

+20 -5
View File
@@ -175,11 +175,11 @@ how many files are missing, how much they weigh, how many are in place and how
much space is free, before anything is written.
The other choices sit one press away. **Choose systems** ticks the consoles to
keep, with the total to download under the list. A long list opens on **None**:
A or Enter there unticks every system, and A on a system then takes that one alone. A
on a system (**Continue**) always opens the confirm screen, which counts the choice
before **Install**: it never installs by itself. Back with nothing ticked keeps the ticks
the list opened with. **Options** sets the
keep, with the total to download under the list. It opens on its first system,
every system ticked: A or Enter ticks or unticks the one in focus, and **All** and
**None** (`a` and `n`) sit at the end of the list. B or Esc (**Done**) takes the
choice back to the plan, which counts it before **Install**: the list never installs
by itself, and Done with nothing ticked is refused. **Options** sets the
preferred regions, game data, the installed cores only, the cores, the parallel
downloads, the folder and, for a list with files read from the frontend's save
directory, that directory. Each row names the option it sets, and **Show the
@@ -1467,6 +1467,15 @@ elsewhere. A custom BIOS directory is still named directly:
python install.py --platform retroarch --dest /storage/emulated/0/RetroArch/system
```
An install on Android leaves an empty `.nomedia` in the BIOS folder. Android's
media scanner hides a folder holding one, and every folder below it
(MediaProvider, `FileUtils.java` `isDirectoryHidden`), so the samples,
overlays and videos of the BIOS folder stay out of the gallery and music
apps. RetroArch writes none. A run that finds one already there leaves it,
and `--check` and `--dry-run` write nothing. The RetroArch pack, unzipped on
Android as on other systems, carries the same empty `.nomedia` beside
`README.txt`. A pack built for a target other than Android does not.
## On a handheld { #on-a-handheld-the-retrobios-port }
RetroBIOS also runs on the handheld itself, in the
@@ -2005,6 +2014,12 @@ opened from Windows, an exFAT card), one overwrites the other. The installer
checks the folder first, keeps one file per name there and lists the ones it
left out.
FAT, exFAT and every Windows drive also refuse `< > : " | ? *` in a name
(Linux `fs/fat/namei_vfat.c:201-207`, `fs/exfat/nls.c:396-403`). RetroDECK's
list names three files with a colon, like `zxs:48.rom`. Before writing such a
name, the installer creates one in the BIOS folder: on an ext4 card it goes
in, on an exFAT card the installer leaves those files out and names them.
### Packs and their parts
`scripts/download.py --list` and `scripts/download.sh --list` print the packs of
+16
View File
@@ -169,6 +169,22 @@ Running `verify.py --emulator <core> --verbose` shows the emulator-level ground
It reaches only as far as the profiles do. Files no profile states a value for are platform-only, and nothing can be said about their content. The footer of the platform report gives that ratio as `Ground truth: N/M files have emulator validation`.
## Why do BIOS pictures and sounds show in a phone's gallery?
Android's media scanner indexes every image, sound and video in shared
storage, and the RetroArch BIOS folder holds 3,842 of them (FBNeo samples,
overlays, PPSSPP assets, sdlpal's videos). An empty file named `.nomedia` in
the BIOS folder hides it and every folder below it. The installer writes one
on Android and the RetroArch pack carries one: see [Android](installer.md#android).
Copied by hand without either, the folder needs that empty file created by hand.
## Why were files left out on an exFAT card?
FAT, exFAT and Windows refuse `< > : " | ? *` in a name, and RetroDECK's list
names three files with a colon, like `zxs:48.rom`. The installer leaves those
out on such a card and names them. An ext4 card holds them. See
[Upper and lower case](installer.md#upper-and-lower-case).
## Next steps
- [Reference](index.md), every reference page in one list
+1 -1
View File
@@ -59,7 +59,7 @@ Every module in `tests/`, by the area it guards.
| Packs and manifests | synthetic + real packs | `test_artifact_lock`, `test_atomic_artifacts`, `test_batocera_cores`, `test_core_data_trees`, `test_deterministic_zip`, `test_emulator_pack_counts`, `test_finalize_pack_names`, `test_large_file_cache`, `test_libretro_layout`, `test_manifest_entry`, `test_minui_platform`, `test_no_game_data`, `test_pack_conformance_dirs`, `test_pack_core_extras`, `test_pack_counts`, `test_pack_destinations`, `test_pack_failures`, `test_pack_file_names`, `test_pack_grouping`, `test_pack_integrity`, `test_pack_member_identity`, `test_pack_readme`, `test_platform_inheritance`, `test_platform_keys`, `test_release_packs`, `test_required_only_archives`, `test_required_only_twins`, `test_save_root`, `test_split_extras`, `test_split_names`, `test_split_pack`, `test_system_pack_extras`, `test_system_pack_parity`, `test_torrentzip`, `test_which_pack` |
| Slots and regions | synthetic + profiles | `test_region`, `test_region_agnostic_scan`, `test_region_groups`, `test_region_held`, `test_region_platform_index`, `test_region_required_only`, `test_slot`, `test_slots`, `test_slots_shipped_file` |
| Hardware targets and systems | synthetic + target files | `test_amberelec_targets`, `test_emuelec_targets`, `test_extract_targets`, `test_lakka_targets`, `test_libretro_slugs`, `test_system_ids`, `test_system_selection`, `test_target_names`, `test_target_scrapers`, `test_target_systems`, `test_target_verify` |
| Installer and downloads | loopback server | `test_check_release`, `test_download`, `test_install`, `test_install_cores`, `test_install_experience`, `test_install_app`, `test_install_from`, `test_install_games`, `test_install_offline`, `test_install_selection`, `test_install_tui`, `test_pypi_package` |
| Installer and downloads | loopback server | `test_check_release`, `test_download`, `test_install`, `test_install_cores`, `test_install_experience`, `test_install_filesystems`, `test_install_app`, `test_install_from`, `test_install_games`, `test_install_journeys`, `test_install_offline`, `test_install_selection`, `test_install_tui`, `test_pypi_package` |
| Handheld launchers | a pty as the console, fake installer and firmware tools, stubbed PortMaster dialogs | `test_handheld_launchers`, `test_port` |
| Running cores | parsers on fixed inputs, a libretro core built from C in the test when a compiler exists | `test_core_probe` |
| Measurement records | synthetic record files, the committed `measurements/` against HEAD, the **Proof** line naming the BIOS a core ran, and that no page shows a Tested block, a region outcome or a time per frame | `test_measurements` |