Closed IzzySoft closed 4 years ago
jmastr
commented
4 years ago @IzzySoft it is meant as a direct drop-in like on other platforms e.g. iOS. However we use a close source framework called Felgo, so there is no way to get that version into F-Droid. The „old“ Android app (2.x) is not maintained anymore and replaced by this app (3.x).
Does that answer your question?
IzzySoft
commented
4 years ago @jmastr thanks and yes, this perfectly answers my question – though not exactly as I hoped…
As the app itself is still under a FOSS license (GPL-2.0), maybe I can offer a "middle way": If you could provide the APKs (e.g. attaching them to releases/), I could serve them via my repo. I'd then update the app description(s) accordingly so it's clear what's going on. Wouldn't be the first app dealt with this way (see e.g. FBReader).
jmastr
commented
4 years ago @micuintus Could you provide the APK?
micuintus
commented
4 years ago As the app itself is still under a FOSS license (GPL-2.0), maybe I can offer a "middle way": If you could provide the APKs (e.g. attaching them to releases/), I could serve them via my repo. I'd then update the app description(s) accordingly so it's clear what's going on. Wouldn't be the first app dealt with this way (see e.g. FBReader).
@IzzySoft Cool, that'll be amazing! Thanks for the offer!
@jmastr: Done -> https://github.com/micuintus/harbour-Berlin-Vegan/releases/tag/3.5.1
IzzySoft
commented
4 years ago @micuintus Thanks, done! Will turn up here with tomorrow's sync (in about 23 hours; just missed today's sync by a few minutes).
I've also created a MR at F-Droid to include the hint into the description there as well. I've not seen that 3rd-party-repos (like mine) are referenced from descriptions in the official repo – so though I'm one of the maintainers myself, I didn't merge that yet but prefer waiting for one more maintainer (and the owner) to approve; IMHO that's a decent thing to do.
Furthermore: my repo running on "private resources" (without any funding; donations, if there are any coming in, do not even remotely cover costs), I've limited the listing to a single architecture – picking the ARMv7 build (that should cover ~90% AFAIK). Updates will be fetched automatically within 24h of your tagging a release and having an *armv7*.apk attached to it.
Hope that makes everyone happ(y|ier) now :smile: I'm proud being able to contribute to a great project this way!
PS: Why not pointing out from the README where to get the app (i.e. links to AppStore, Play Store etc)? Feel free to include a link to my repo then as well :wink:
If there are any questions, don't hesitate asking. I'm closing this issue now; though not solved by updating the official repo, this is as far as we can get this currently. If you think otherwise, just reopen.
Thanks again!
micuintus
commented
3 years ago Hey @IzzySoft ,
Version 3.6 of the Berlin-Vegan Guide has been released this week --- and it seems your update mechanism has worked just flawlessly. :1st_place_medal: Thanks again for your effort, I/we really appreciate it!
I've limited the listing to a single architecture – picking the ARMv7 build (that should cover ~90% AFAIK).
FYI: According to Googe Play Console, the ARM64_v8a variant runs on 4,752 devices and the ARMv7 variant on 12,713. Probably the ARM64_v8a bucket is a true subset of the ARMv7 one. On the 64 bit devices, the ARM64_v8a runs way smoother though. But, of course, I can totally understand that you want to spare your private resources! Thanks for the donation of those ;)
PS: Why not pointing out from the README where to get the app (i.e. links to AppStore, Play Store etc)? Feel free to include a link to my repo
Thanks, that is a splendid idea --- I am also gonna ask Sandy to put a link on the BV website!
IzzySoft
commented
3 years ago Glad to read! For the link, I meanwhile can offer a badge if you need it :smiley:
As for architectures: Yes, v8 devices can run v7 code fine (just not the other way around), hence my decision. I'm aware that there might be a performance increase with "native code", but we can't have it all unfortunately. I gladly do what I can to support FOSS (preferring FOSS myself), but as pointed out my resources are limited.
BTW: That MR at F-Droid was merged meanwhile.
As this app uses the same package name as its "former Android version": is it intended as a direct (drop-in) replacement? Or is it rather a fork? Asking because the former one is listed on F-Droid and was last updated in February. So should we see if we can switch to this new repo? Or would you rather switch to a new package name for a separate listing?