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.
One run of profile_sync --all --rebase-refs --fresh. Every guard held:
no ref to review, no prose left under an older pin, no file name or hash
literal gained in a cited file since the pin, no built_by pin and no pin
keyed by build mode. The site's record of cited source paths is rebuilt
with them.
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.
Every cited block was read again at HEAD: no ref left to review, no
file name or hash literal added to a cited file since the pin
(--detect-new-files --watch-hashes), refs recaled with their pins.
Profiles built by a platform at a fixed commit, or whose bump would
leave prose under an older pin, stay where they were.
Profiles that read two repositories, a libretro port and its upstream,
now prefix each citation with source or upstream, decided by which tree
carries the cited value at its pin. The emulator pages use the word to
tell libretro glue, emulator code as the port carries it, and the
upstream emulator apart.
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.
same_cdi's cdi.cpp is 494 lines; the profile cited 574-640 and 662-820,
which are upstream MAME's numbers. The fork carries four sets and none
of the Quizard game ROMs, and the refs say so now.
fsuae cited fsuaePaths.py and fsuaeGenerator.py against libretro-fsuae,
where they have never been: they are Batocera's, which is what the note
already said in prose.
Cores that load files from system_dir subdirectories (same_cdi/bios/,
neocd/, cannonball/, Citra/sysdata/, mame2003/, etc.) need path: on
each file entry so cross-reference and pack generation place files at
the correct destination. Also fixes neocd.yml using non-standard dest:
field instead of path:.
Closes#41
Created desmume2015.yml with files: [] (code doesn't load BIOS).
Removed desmume2015 from desmume.yml cores list.
Removed cdi2015 from same_cdi.yml (separate profile exists).
Frozen snapshots must have their own profiles because their
firmware behavior differs from the current version.
Every profile now has:
- profiled_date: date of source code analysis
- core_version: version from libretro-core-info .info files
- display_name: human-readable name from .info files
260/260 profiles complete. 294/294 libretro cores covered.
Standalone emulators (cemu, rpcs3, xemu, vita3k) versioned manually.
- Added profiled_date field to all 204 existing profiles for update tracking
- Created 56 alias profiles for cores that share BIOS with a parent
(e.g., mednafen_psx -> beetle_psx, fbalpha2012 -> fbneo)
260 total profiles covering all 294 libretro cores (204 unique + 56 alias).