mirror of
https://github.com/Abdess/retroarch_system.git
synced 2026-11-15 14:33:47 -06:00
chore: merge origin/main
This commit is contained in:
commit
025fd08a72
16 files changed
+484
-9
No files matched your search
@@ -40,6 +40,15 @@ irm https://abdess.github.io/retrobios/i.ps1 | iex
|
||||
Always type the `https://`: without it the first request goes out in clear
|
||||
text, and anyone on the way could answer with another script.
|
||||
|
||||
With Python 3.8 or newer, the same installer is a package:
|
||||
|
||||
```bash
|
||||
uvx retrobios
|
||||
```
|
||||
|
||||
`pipx run retrobios` works too, or `pip install retrobios` and then
|
||||
`retrobios`. Options follow the command: `uvx retrobios --check`.
|
||||
|
||||
`i` and `i.ps1` are `install.sh` and `install.ps1` as of the commit the site
|
||||
was built from, set to download `install.py` from that same commit. The
|
||||
fingerprint they check and the installer they fetch never come from two
|
||||
|
||||
+17
-2
@@ -110,8 +110,8 @@ scripts stay Python.
|
||||
`platforms/**`, `emulators/**`, `schemas/**`, `scripts/**`, `tests/**`,
|
||||
`install.py`, `install.sh` or `install.ps1` (the bootstraps pin the
|
||||
installer's SHA-256, so editing one without the other fails the run),
|
||||
`ports/**` (the handheld port bundles the installer), or any input of the site
|
||||
build. The path lists are spelled out once per event because the workflow
|
||||
`ports/**` (the handheld port bundles the installer), `packaging/**` (the PyPI
|
||||
package is built from it), or any input of the site build. The path lists are spelled out once per event because the workflow
|
||||
parser reads no YAML anchor, and a test holds the two equal.
|
||||
|
||||
**Concurrency.** Per-PR group on a pull request, per-ref on a push. A pull
|
||||
@@ -312,6 +312,21 @@ git status --short
|
||||
git add release.json README.md install/*.json install/targets/*.json
|
||||
git commit -m "chore: record release v${DATE}" && git push
|
||||
|
||||
# 5b. The PyPI package, `uvx retrobios`: install.py and its command. The
|
||||
# version is the UTC date of the last commit that changed install.py
|
||||
# (2026-11-09 gives 2026.11.9, the third change that day 2026.11.9.3),
|
||||
# so an unchanged install.py keeps its version and PyPI refuses it
|
||||
# again. Publishing is not tied to a release: any push that changes
|
||||
# install.py can be published. The build replaces any earlier one in
|
||||
# tmp/pypi-dist. `uv build` builds it with the flit_core backend the
|
||||
# project pins, dated by that commit (SOURCE_DATE_EPOCH), so a rebuild
|
||||
# gives the same bytes. Build, run the wheel, then upload the two files. The
|
||||
# token stays in its file: never in the repository, a script or a log.
|
||||
python scripts/build_pypi.py --output-dir tmp/pypi-dist
|
||||
python -m unittest tests.test_pypi_package
|
||||
uvx --from tmp/pypi-dist/retrobios-*.whl retrobios --help
|
||||
uv publish --token "$(cat ~/.config/retrobios/pypi-token)" tmp/pypi-dist/*
|
||||
|
||||
# 6. Keep only the new release plus large-files: an older pack carries hashes
|
||||
# the platforms no longer check, so it misleads more than it helps
|
||||
gh release list --json tagName,createdAt \
|
||||
|
||||
@@ -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` |
|
||||
| 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` |
|
||||
| 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` |
|
||||
|
||||
Reference in new issue
Block a user