Three cores the buildbot ships have no .info a frontend can find.
nSide has one, under the name the core used to have. The file already says
nSide inside - display_name, corename and version all name it - but it is
still called higan_sfc_balanced_libretro.info, while every platform builds the
core as nside_sfc_balanced. A frontend matches the info by the core's file
name, so it never finds this one, and the core shows up as a bare filename
with no system, no extensions and no database. Renamed, contents untouched.
Omicron and Video Processor have no file at all. Both are built for linux
aarch64 and x86_64 (Video Processor being Linux-only by nature, Omicron also
on Windows), and both have been nameless in the frontend for as long as they
have been shipped. The two new files are written from the cores' own sources -
extensions, no-content support, save states, core options and hardware render
are what retro_get_system_info and retro_set_environment actually do - and the
notes carry the two things a user cannot find out by looking: that Omicron
loads a JVM from JAVA_HOME and will not start without a Java runtime on the
machine, and that Video Processor does not declare no-content support, so a
file still has to be picked even though it is ignored and the capture device
comes from the core options.
higan_sfc_libretro.info is left alone. It names a core that is not built on
any platform any more - the accuracy profile is refused in nSide's own source
- but removing it is a separate decision from naming the one that is built.
