mra files in the repo.json?
neil-morrison44 opened this issue · 2 comments
What’re your thoughts on including the (converted) mra files in the repo.json? (I’m sure someone will upload them somewhere)
If you’re alright with that then I guess bios would make more sense as files or some other more generic name?
If not, then I suggest adding support for an (optional) custom json file kept on the pocket which can pull in other repos & files - maybe even referencing other json files on the web which someone else is keeping up to date.
Custom JSON support would also be handy for testing things before putting them in the main repo, I guess.
Those would be for arcade cores right? I think that makes sense. We should rename bios to deps.
While we're at it, are there any situations in which a dependency would need be processed (specifically unpacked from an archive)? If so then path should just be used to copy single files and we can have a separate install_dir as an implicit instruction to try and unpack an archive there.
What do you think?
for arcade cores yeah, all the recently added ones need converted .mra files to function.
deps makes sense.
As for post-processing I’d recommend adding something like “process” alongside ”path” & ”url” in deps as an optional way to say the file needs post-processing - could start off as having ”unzip” & ”unrar” then add more in the future if needs be