The three builds the platforms ship are 5f301c8 (Recalbox), 6a34ec0
(EmuELEC) and 0f6a767 (AmberELEC): 5f301c8 is an ancestor of 6a34ec0,
itself an ancestor of 0f6a767. 0f6a767 is no longer on the rewritten
branch and is fetched by its sha. The profile was held at 799060b,
which none of them builds, so EveryBuildReferenceNamesThePin failed.
At 0f6a767 and its two ancestors the same 26 BIOS roots are registered
with the same contents. aleck64, atarisy1, cedmag and coh1002v are not
among them and leave the profile with the Aleck64 and Cedar Magnet
systems, and hng64 (src/drivers/hng64.c:1425-1431, 1718) joins it.
Every ref is moved with the pin and read again. Each cited line holds
the same text at 6a34ec0 and 5f301c8, except advance/osd/video.c:1787,
1795: Recalbox's 5f301c8 compiles those tables from blitmax.h and
startup.h, now said in the notes. The doc/advmame.d citations, worded
otherwise in the older builds, give way to the code that does it
(advance/linux/file.c:87-99, src/romload.c:167-204), and the artwork
refs to src/artwork.c, the loader of this revision.
Manifests: AmberELEC and Recalbox gain hng64.zip and lose aleck64.zip,
cedmag.zip and coh1002v.zip at their BIOS root. EmuELEC loses
cedmag.zip from arcade and mame, its other three stay for MAME 2010
and 2003-Plus, and hng64.zip takes the copy holding the advancemame
members. profile_sync: 0 to review, config_reads BUILD_OK at 6a34ec0.
RetroPie clones amadvance/advancemame at the branch tip with no
revision (scriptmodules/emulators/advmame.sh:16, 39-41 at 427e762), so
advmame is profiled at 96237a5 (v5.0-484), built_by retropie and held
by pin_follows. RetroPie's advmame now resolves to it, advancemame
keeping EmuELEC, AmberELEC and Recalbox.
The MAME workflow at 96237a5: 28 BIOS roots registered in
mame/mamedriv.c (macs2bios is not), the eight ZN roots under their MAME
names (coh1000c, coh3002c, coh1002m, coh1000t, coh1002e, coh1001l,
coh1000w, coh1000a), modern Neo Geo members, coh1000w's CAT702, and 15
device archives that BIOS_LOAD reads first (atarisy1, coh3002t, m1comm,
midssio, namcoc65/68/69/71/74, s_smp, saa5050, sente6vb, sns_dsp1bleg,
t5182, v4bios). bctvidbs declares no ROM of its own. Three laserdisc
player programs are opened by name outside any ROM list, with a fatal
length, CRC32 and SHA1 check: pr8210, 22vp931 and simutrek.
pin_build accepts pin_follows in the schema, and bump_commit advances a
built_by profile that follows the tip.
Manifests: RetroPie gains 24 archives at its BIOS root, the ZN ones
under their new names, and nss.zip moves to the copy holding
nss-c.dat and nss-ic14.02. The other platforms do not change.
verify --all keeps its counts. profile_sync: 0 to review.
amadvance/advancemame rewrote the tip of master: e291032 is no ancestor
of the branch any more, and 799060b replaces it (same parent abfc3c8,
same message). The two differ in makefiles and the removed jedutil
sources only, none of the files the profile cites, so the refs keep
their lines at 799060b (v5.0-453-g799060b).
From e1a9aad5 the branch renames the Sony ZN BIOS archives after MAME
(cpzn1 becomes coh1000c, zn.c BIOS() at 4801) and loads firmware with
BIOS_LOAD. EmuELEC (6a34ec0), AmberELEC (0f6a767) and Recalbox
(5f301c8) build earlier revisions that read the names the profile
lists, so the pin is held with pin_frozen and the two other builds join
pin_build. RetroPie builds the branch tip (advmame.sh:16, 39-41).
profile_sync: 0 to review. Manifests do not change.
EmuELEC builds AdvanceMAME at 6a34ec0 (package.mk PKG_VERSION, v4.8).
At that build advmame.rc is read from the home, host and data folders
(advance/osd/emu.c:754-757, 779-791) and the dir_* keys set each search
folder (advance/osd/fileio.c:72-86, 798-815). With the config_reads the
launcher evidence rule asks for, EmuELEC's advmame.sh dir_rom records
bind again: its manifest gets back the 29 sets in roms/arcade and the
29 in roms/mame.
EmuELEC starts AdvanceMAME for arcade, mame and cps1-3 (es_systems.json).
advmame.sh sets dir_rom to /storage/roms/arcade for arcade and keeps
/storage/roms/mame for every other system (advmame.sh:26-30, 80), so an
arcade set is read in both. A binding gave each entry one place: an entry
launched both for a system a record names and for one it does not now
takes the place of each, in the pack, the manifest and verify. A system
the platform's list or machines put the entry under stands for the
entry's own ids, so XRoar's coco3.rom stays in RetroBat's bios/coco alone.
The AdvanceMAME sets are filed under arcade as well as their board.
A second-pass copy outside the BIOS tree now carries its layout path and
resolves by it, as the first pass does: EmuELEC's roms/mame/stvbios.zip
took bios/Arcade/MAME's set by that tail, roms/arcade/stvbios.zip the
Arcade/Arcade one.
Manifests: EmuELEC gains the 29 sets in roms/arcade, each the file
roms/mame holds. roms/mame/stvbios.zip changes from bios/Arcade/MAME to
bios/Arcade/Arcade/stvbios.zip, the copy the entry resolves to. Nothing
else moves.
AdvanceMAME reads its sets from dir_rom, a list of folders
(advance/osd/fileio.c:74, doc/advmame.d:680,699-701). EmuELEC's
advmame.rc sets dir_rom /storage/roms/mame (advmame.rc:11), and
advmame.sh rewrites /roms/mame to /roms/arcade when it is started for
the arcade system (advmame.sh:26-30). The extractor kept the keys under
the BIOS root alone: it now records those under the roms root too, and
a key the script rewrites gives one record for arcade and one for every
other system. A configgen record carries the systems it is written for.
The profile lays its 29 sets out at the top of dir_rom. On EmuELEC they
land in roms/mame. The 12 root archives AdvanceMAME alone claimed there
now hold the copies of the cores that also declare them (mame, geolith),
none of them lost.
A destination outside the BIOS tree is no proof of content: the moved
entry resolves by its layout path alone. roms/mame/konamigv.zip took
bios/Arcade/MAME/konamigv.zip, MAME 0.289's set, by that tail.
core_version is read at each pin where version_basis says. MAME 2014,
2015, MESS 2015 and CDi 2015 state 0.159 in src/version.c (the libretro
wrapper reports 0.160), MAME/MESS sits on the 0.289 makefile of its pin,
FinalBurn Neo states 1.0.0.03 in src/burn/version.h, FB Alpha 2012 and
its CPS-3 build 0.2.97.30. mame_version of MAME 2014 and 2015 follows,
as MESS 2015 and UME 2015 already said.
Upstream registered the Aleck64 PIF BIOS as a NOT_A_DRIVER set at src/drivers/aleck64.c:776, loading pifdata.bin. The pin moves from the force-pushed dcf44cc to 8167047.
Same chain as the first pass: no ref to review, no file name or hash
literal added to a cited file since the pin, no profile a single
platform builds at a fixed commit, refs recaled with their pins, and the
written prose read again.
ebe8322 adds the Video System PSX driver with its coh1002v root set (src/drivers/zn.c:4062-4068, 4692). The new hashes in pgm.c and the other drivers belong to game sets (killbldp, kovsh, svg, oldsplus...); the pgm BIOS ROM_START is unchanged.
EmuELEC, AmberELEC and KNULLI launch standalone emulators by the name
their launch code dispatches on (HATARISA, PPSSPPSDL, FBNEOSA) and ship
32-bit or patched builds of libretro cores under their own .so names
(flycast_32b, mupen64plus_next_alt, genesis_plus_gx_cart_special,
mame0139, flycast-xtreme). Each name joins the profile of the project
its package builds. fceumm_mod reads gg.rom, not gamegenie.nes, and
never opens it, so it gets its own profile.
Entries without a system in multi-system profiles were left unattributed by the truth model, and four System.dat additions left the export. Each system is read from the core's code at its pin. hiscore.dat, cheats and history serve every running machine (mame2000 cpuintrf.c:664-666, mame2003 cpuexec.c:280-282, mame2003_plus cpuexec.c:296-298, fbneo hiscore.cpp:154-161 gated on BDF_HISCORE_SUPPORTED), all arcade in those builds, so arcade. BIOS sets take the id their driver gives in the other MAME profiles, and bctvidbs is barcrest-mpu4 everywhere. Files serving several systems of one build (groovymame data files, raine) keep no system. Core resolution is unchanged on every platform.
Each platform's own packages were read at the revision our data pins, for every emulator and core it ships: Batocera, Recalbox, RetroPie, ROCKNIX, Lakka, RetroDECK, RetroBat and EmuDeck. Files a package installs where the emulator reads them are recorded with installed_on, and files a release bundles but a package leaves out with not_bundled_on, so each platform's pack brings what its users lack and nothing they already have. The standalone profiles never checked before were held against their releases the same way. Batocera's imame4all is the mame2000 core. The primary neogeo.zip was a 7.7 KB placeholder no platform pins and no pack served: removed, the real dumps stay in .variants.
Profiles, the wiki, comments, docstrings, command output and schema descriptions carried em-dashes, clause-joining semicolons, unicode arrows, box-drawing banners and check-mark glyphs. Each sentence was rewritten rather than having its character swapped. Hashes, paths, source_ref values and every cited file:line are unchanged, which a comparison of each parsed profile against the previous revision confirms.
validate_pr comments now say PASS and FAIL in words, and source_ref values in a profile's structured blocks render as code. test_prose_style fails if any of these comes back, in tracked files or in the generated site.
The new-format hiscore.dat was served by name to cores whose parser reads
only legacy lines. Eight cores now pin the hiscore.dat their own
repository ships, four revisions newly collected.
Abdessamad Derraz