![]() Personally I think that RetroArch should on all platforms just start downloading automatically assets if it starts and the assets are missing. And without assets the icons are missing but the text is displayed and enough to navigate to the Online Updater, which is where the user will find the assets and also cores to be downloaded. Just to comment from a user's perspective, I think starting RetroArch with no assets is not as bad as it sounds as the same will happen if the user changes the assets directory in the settings. If the dev decides that is acceptable (and maybe F-Droid gives an exemption I guess), the app can get on F-Droid right away. Without it users need to manually download assets using built-in updater to make the app behave normally. ![]() We are stuck at the reproducibility issue of RetroArch assets which update too fast and therefore cannot generate a checksum to satisfy F-Droid requirement. But I think the command itself should extract it to the right place, i.e. Honestly speaking idk about these questions, hopefully some RetroArch dev working on Android part can answer this. There were no reports that my test APKs are broken, so not sure how this works. I forgot to ask, where (relative to the repo root) does the assets folder needs to be? media/assets/ ? media/ ? If not, the process should generate a hash to make APKs reproducible. can you tell how the assets at are updated? If the asset update is triggered by commits, it should be easy. I wanted to put the hash sum of the file so we can check it before built, that's not feasible now Speaking of those, F-Droid likes to have APKs reproducible if possible so having the APK contents match your own is a goal. ![]() But maybe we/you can specify the exact commit that the project is using exactly? eg is using what?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |