Hi, Joonas, On 08/28/2018 08:53 PM, Joonas Kylmälä wrote: > Hi, > > I tried to draft patches for the RepWifi ticket over here: > https://redmine.replicant.us/issues/1887. Please see them as > attachments.
I hope I'll be able to test your patches during September. For now, thank you for taking care of the issue! I think building RepWifi from within Replicant's source tree is ideally the best choice for various reasons.. Still, I'm convinced that shipping the F-droid APK is the most reasonable compromise to allow users to keep it up-to-date, until we find an efficient way of shipping updates without the need to install a new system image each time. That's why I originally proposed this approach. > What do you think will happen when we update the RepWifi > app next time in Replicant and the user has already upgraded it with > F-Droid? I honestly don't have a clue, and never thought about that.. It should be easy for me to test.. Soon as I have a little time, I'm merging your patches and probing some test cases, comprising the one you suggested. Thank you for pointing it out. > Also will this just start piling up > fil.libre.repwifiapp_{9,10,11,12,13...}.apk files during each Replicant > upgrade until storage is full? I'm not sure what you're referring to, can you please explain what you mean? If you refer to the target's onboard storage, then I think that the android system itself automatically cleans up APKs if duplicates or older versions are found when the app is launched (at least that's the impression I got by reading adb's debug messages sometimes..) Cheers, Fil > > Joonas
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Replicant mailing list Replicant@osuosl.org https://lists.osuosl.org/mailman/listinfo/replicant