This core should use upstream dosbox support for config file onions on upstream dosbox.
If you don't know, if you pass a conf file in dosbox starts with the settings on it and runs the autoexec section. But not only that: if you start it with:
dosbox -userconf -conf dosbox.conf
the -userconf setting will make it start with the default conf settings first (the one in your .dosbox folder in unix) and then override the settings set on the local dosbox.conf passed in -conf, then run the first autoexec, then run the second autoexec.
You can use this to keep minimal conf files for games and a central place to set up 'default' dosbox options.
Apparently libretro already has a core configuration system that is similar, and this is fine (if you don't want to support to dump a default dosbox.conf on the bios folder), but the core should support overriding these with a local conf and this override should be treated the same because these local 'conf' files are often part of the game packaging and fundamental to running them.
I'd argue in fact, that the scanner shouldn't be scanning for execs at all as a starting point of the core for the playlists, considering that all of the important configuration information is on a conf file. I understand that they not having a fixed crc is problematic for your metadata system, but you really should have a way to separate the identifier file from what's passed to the core on the playlist system and this is one reason.
This core should use upstream dosbox support for config file onions on upstream dosbox.
If you don't know, if you pass a conf file in dosbox starts with the settings on it and runs the autoexec section. But not only that: if you start it with:
dosbox -userconf -conf dosbox.confthe -userconf setting will make it start with the default conf settings first (the one in your .dosbox folder in unix) and then override the settings set on the local dosbox.conf passed in-conf, then run the first autoexec, then run the second autoexec.You can use this to keep minimal conf files for games and a central place to set up 'default' dosbox options.
Apparently libretro already has a core configuration system that is similar, and this is fine (if you don't want to support to dump a default dosbox.conf on the bios folder), but the core should support overriding these with a local conf and this override should be treated the same because these local 'conf' files are often part of the game packaging and fundamental to running them.
I'd argue in fact, that the scanner shouldn't be scanning for execs at all as a starting point of the core for the playlists, considering that all of the important configuration information is on a conf file. I understand that they not having a fixed crc is problematic for your metadata system, but you really should have a way to separate the identifier file from what's passed to the core on the playlist system and this is one reason.