Moderators: Mug UK, Zorro 2, Greenious, spiny, Sorgelig, Moderator Team
zomgugoff wrote:I am getting the atari5200 core downloaded when it's not specified in my filter. I'm assuming that's because it's mixed in with the atari800 repo. Is there a way to just get the atari800 core?
Locutus73 wrote:It’s difficult to tell without knowing your filter (the whole ini would be better), but yours seems a good guess.
zomgugoff wrote:It can be replicated with just this:
REPOSITORIES_FILTER="atari800"
The output shows 'Checking Atari800' twice. The first time it downloads atari800.rbf into 'computer'. The second time, it downloads atari5200.rbf into 'console'.
seastalker wrote:This is indeed a great script. Please forgive if it has been answered, but is there a setting or something I must do if I do not want the script to set the sd card as read-only?
seastalker wrote:Sorry, I was not replying directly to the Atari800 core part of the discussion but as a thank you and feedback to the core as a whole. I tried out the LATEST updater script and it is great that it can auto-download cores. In my case it made everything on the sd card Read-only.
Locutus73 wrote:You're right, the REPOSITORIES_FILTER is a filter by repository name and https://github.com/MiSTer-devel/Atari800_MiSTer is the repository for both Atari 800XL and Atari 5200 core. I didn't think to this back then. I don't know, I could bake something specific for that, any idea?
zomgugoff wrote:Locutus73 wrote:You're right, the REPOSITORIES_FILTER is a filter by repository name and https://github.com/MiSTer-devel/Atari800_MiSTer is the repository for both Atari 800XL and Atari 5200 core. I didn't think to this back then. I don't know, I could bake something specific for that, any idea?
If the script grabs the newest .rbfs from each repo, then maybe do a partially filename string match to determine which .rbf to keep? E.g. filter=atari800, do string match from repo for 800(or atari800) and keep that file only.
Locutus73 wrote:The string match is performed only on the repository name, not on the rbf files.
The updater first downloads https://github.com/MiSTer-devel/Main_MiSTer/wiki, then it applies the REPOSITORIES_FILTER string match to the repositories (the ones you can read on the right of the page) and finally it navigates all the filtered repositories in search of the latest rbf files. Just for the Atari800 repository it searches both for the 800 and 5200 rbf core files. But the filter is applied before navigating all repositories in order to make the script quicker (if a filter is applied).
zomgugoff wrote:How about a flag to disable downloading both 800 and 5200 cores if either is found in the filter?
zomgugoff wrote:How about a flag to disable downloading both 800 and 5200 cores if either is found in the filter?
Locutus73 wrote:I was thinking that DOWNLOAD_NEW_CORES="false" or DOWNLOAD_NEW_CORES="_New Cores" could satisfy your need.
When set to false it won't download cores which are already on your SD so, with REPOSITORIES_FILTER="atari800", just delete the core you don't need from the SD and it won't be downloaded again. If you use DOWNLOAD_NEW_CORES="_New Cores" all new cores which aren't already on the SD will be downloaded in the _New Cores directory (remove the underscore if you don't want it listed by main MiSTer core browser)... that's my personal choice.
RabidWookie wrote:Are there arcade cores that do not get added by the updater script? I've seen people playing Commando but I don't seem to have it after running the script.
vanfanel wrote:Do you guys know if its possible to add Mr-X repository so his Arcade cores are updated too? He has some exclusive cores he has made, like Solomons Key, etc...
Where should it be added? Which format should I use?
kitrinx wrote:vanfanel wrote:Do you guys know if its possible to add Mr-X repository so his Arcade cores are updated too? He has some exclusive cores he has made, like Solomons Key, etc...
Where should it be added? Which format should I use?
Pulling cores from outside the official repository is a bad practice. Only the things in the official repo are guaranteed to remain compatible, and encouraging fragmentation of the codebase is not something it would be wise to do by supporting tons of ancillary repositories. Mr X puts all his cores in the official repo, so it would be best to simply wait for them to end up there, and then they will be updated by our tools.
RabidWookie wrote:Will Jotego's cores be added to the official script?
Users browsing this forum: No registered users and 5 guests