New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
F-Droid: Missing data #16126
Comments
Where do the assets come from? https://buildbot.libretro.com/assets/frontend/assets.zip Are those per version so I can have a hashsum or rolling ever changing? What are the licenses of that content? Which files from that archive we need, and put where during the build process? |
@davidhedlund I'm asking the void not you specifically 😛 |
Not what I've asked, see last question. |
Thanks for taking on some packaging! Good to have F-Droid because the Google Play Store install can get old quickly.
Each repo should contain the license info. If not, then it's likely under what's in https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository .
The versions are usually up to when the RetroArch release was made, but the assets should work across all versions no problem.
Sometimes there's a |
Thank you very much for helping him with the F-Droid release. |
licenses vary on the shaders, and they change pretty frequently. The overlays change less often. We made that minimal, static asset package already, and we could always add more stuff to it, if needed. |
If I remember correctly, assets are not included in the F-Droid build because the constant updates were preventing from make the build reproducible, this was discussed here. The current minimal_assets.zip apparently only have the standard GLUI Menu Driver for Android, but obviously they are still missing assets necessary for a good experience on Android, such as gamepad overlays needed for the touch controls (related issue). Even with more assets included by default, it would be nice to add a note at the top of the RetroArch page in F-Droid, like NOTE: Use Online Updater to update assets on first launch if needed or something like this. |
@licaon-kter Together, these roughly double the size of the minimal assets package (i.e., from 1.2 MB to 2.8 MB) but make a usable system without having to update anything out of the box. If this works for you guys, I can have @LibretroAdmin replace the old with the new. |
We have a Makefile for the retroarch-assets. It would likely be possible to write a Can the F-Droid package use make? |
IIRC, one of the issues they had was that the checksum of the bundle would change if anything were added/removed on each release, and that would mess up one of their integrity checks(?), so a static bundle was preferred. |
I added this to https://gitlab.com/fdroid/rfp/-/issues/1933#note_1731005305 :
"The package maintainer should add the assets, .info files, shaders, everything." - Rob Loach, RetroArch administrator - #16087 (comment)
The text was updated successfully, but these errors were encountered: