Publish on F-Droid?
IzzySoft opened this issue ยท 10 comments
As far as I can see, there are no show-stoppers for publishing your app on F-Droid (which is THE place for Android FOSS apps). Assuming you are interested, I've opened a Request For Packaging ("RFP") for your app โ so if you agree, F-Droid would build your app from your sources, and include it with its index (see here).
Would you support that? Thanks in advance!
Hi.
F-Droid looks suitable for this open-source app. Ofc you can build and share.
In addition here's the Google Play link: https://play.google.com/store/apps/details?id=com.tht.k3pler
Thanks a lot, @KeyLo99! Until it's build and available in the official repo, I just made it available in mine: http://apt.izzysoft.de/fdroid/index/apk/com.tht.k3pler (so it can already be found with the F-Droid client if the user has my repo enabled in it).
Thanks a lot! Pinged our "integrators" to pick it up. And adjusted my updater to fetch the APK from the tags ๐
Hey there! How can I update the APK on F-Droid?
@KeyLo99 just tag a new release. Metadata say that will be noticed, fetched and built automatically (then pushed into the review queue for approval, signing and finally publication).
Taken literally: you cannot update the APK, as F-Droid builds it from source ๐
No idea why it's not even picked up in Metadata yet. Sometimes it takes a couple of days. Should above link still not show the new version within a week, feel free to ping me again (or ask on IRC #fdroid
at freenode yourself; I'm not involved nor familiar with builds, so that's what I'd do then anyway).
Just to let you know you now made updates impossible in this commit: changing the package ID is a very bad idea. There can't and won't be any future updates in F-Droid. Users must re-install your app.
Was that intended? Then you need to apply for a new listing of the new package name. If not: either revert the change of package name back to what it was, or add a specific build flavor explicitly setting applicationId "com.tht.k3pler"
so we can point our build process to that.