mirror of
https://github.com/Abdess/retroarch_system.git
synced 2026-10-10 13:33:24 -05:00
docs: state what separates two platform packs
This commit is contained in:
1 parent
1ceb4b0c5a
commit
1be50e056f
1 file changed
+5
-3
@@ -147,9 +147,11 @@ entries that are out of scope here.
|
||||
## Pack grouping
|
||||
|
||||
Platforms that produce identical packs are grouped automatically.
|
||||
RetroArch and Lakka share the same files and `base_destination` (`system/`),
|
||||
so they produce one combined pack (`RetroArch_Lakka_BIOS_Pack.zip`).
|
||||
RetroPie uses `BIOS/` as base path, so it gets a separate pack.
|
||||
Two platforms share a pack when they declare the same files and run the same
|
||||
emulators. RetroArch and Lakka do, so they produce one combined pack
|
||||
(`RetroArch_Lakka_BIOS_Pack.zip`). RetroPie inherits RetroArch's systems but
|
||||
ships its own package list, standalone emulators included, so it gets a
|
||||
separate pack and a separate install manifest.
|
||||
With `--target`, the fingerprint includes target cores so platforms
|
||||
with different hardware filters get separate packs. Emulator and system packs
|
||||
also retain system identity, `variant_group` and requested region; same-named
|
||||
|
||||
Reference in new issue
Block a user