Hi, in Tux Paint we have the stamps collection that amounts about 200MB of images, sounds, metadata and sound descriptions.
I’ve generated some APKs with sound descriptions(3 to 32 MB) and one APK(35MB) with the images metadata,etc.
https://provant.freeddns.org/pere/public_html/tuxpaint-stamps/20210806/ all in all 13 APK files coming from the same source.
The 2 problems I am seeing in order to add them to fdroid are that currently, to generate each one of those APKs,
- fdroid server would have to download everything again and again.
- The generated zip source files are as big as the whole git repo, they would be nearly identical for each apk except the stamps.zip asset autogenerated in the prebuild step and the fdroid server would have to store all of them
Would all this overload be acceptable?
Is there a way to tell fdroid server to reuse a download in order to compile other APKs?, or to generate different APKs from one metadata file? if possible, that would reduce drastically the network footprint.
Is there a way to tell fdroid server that the zip source file generated for one APK is also valid for other APKs?
Is there a way to tell the fdroid server to limit the ZIP files generation to the directory where the Android code is stored?
Any other ideas to not overload the fdroid servers?
One build entry from one metadata yml looks currently like this, I just need to adapt the versionName and gradle fields and the package_stamps.sh call to get the other APKs
- versionName: 0.0.1-images
- cd …/
- ./package_stamps.sh images