-
Notifications
You must be signed in to change notification settings - Fork 4
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
add Fdroid repo #6
Comments
I, personally, don't like the F-Droid approach regarding packaging. The fact that they recompile and re-sign the application bothers me. On some previous projects, I had some issues reported due to the distribution of an incorrect APK on their repository. However, feel free to submit a request for packaging on the F-Droid tracker. |
I opened a Request For Packaging here: https://gitlab.com/fdroid/rfp/issues/952 |
Thank you for submitting the RFP @Poussinou. I'll keep this issue open until the RFP on the F-Droid tracker is closed |
For those who want to install this with f-droid, it's available from IzzyOnDroid's repo: https://apt.izzysoft.de/fdroid/index/apk/com.geekorum.ttrss.free To add the repo: https://apt.izzysoft.de/fdroid/index.php |
@fbarthelery it seems there are some issues with the F-Droid inclusion (reference). Quote:
Firebase would be a general show-stopper (but if I understood correctly, the special flavor should exclude it). Are the sources for geekdroid available publically, so we could make that a |
I still have some work to do before publishing the geekdroid libraries and make it usable. (it wasn't really on my todo list). Would it be enough if I just dump the sources in a Github repository? |
as I cannot tell exactly: @Rudloff @licaon-kter ? |
@fbarthelery yes, even better if pull them as a gitmodule or how will you use them? |
I think I'm going to keep using a prebuilt jar or use JitPack for now |
@fbarthelery with a prebuilt Jar, inclusion in F-Droid won't be possible. JitPack would be fine. |
@fbarthelery Adding jitpack.io but still fails
ignore the line number since I'm cleaning non-FOSS libs |
Sources for the |
Oh, didn't know...will try... |
More info here if you are interested |
@licaon-kter Alternatively, you can set a the Let me know if there is anything else I can do to help. |
@fbarthelery by the way, you forgot to adjust versionCode and versionName for 1.5.0. APK still identifies as
Can you please fix that (and create a new tag with an APK attached)? Thanks! |
Good catch @IzzySoft ! Looks like I uploaded an older apk instead. I edited the release to attach the correct apk. Thank you |
Thanks for the fast fix @fbarthelery! Updated it in my repo (will show up in about 7 hours with the next sync). |
@fbarthelery I'm guessing this can be closed, since the app was successfully published to F-Droid. |
Things got piled up, I didn't get around to retest....but no, this is not in F-Droid atm. |
Oh, my bad, after checking I downloaded it from Izzy's repo. |
Looks like my repo got that popular people confusing it with F-Droid already, wow 🤣 I take that as compliment, thanks! |
The F-Droid app just makes it so convenient to not even have to think where the apps are coming from once you import the repos 😂, but yeah, you should totally take it as a compliment, your repo and the way you automated it are pretty cool. |
Decentralization is an F-Droid goal, so @IzzySoft is doing a great service ;) |
So what @erazemkokot just wrote is a compliment to both 🥳 🍾 Thanks! |
|
I have to remove it it should not be needed anymore.
Play services plugin is not applied on free variant. Same for firebase dependencies
navigation-dynamic-features-* are on Apache 2 license according to this @licaon-kter let me know if I'm wrong |
Is this fixed? https://issuetracker.google.com/issues/237574816?pli=1 if not, then its deps are not FOSS ;)
Guess we can |
Great! I'll publish it in one of the approved repos for next release |
I just released 1.6.5 and I think it can be the one finally going to F-droid! I had to publish my fork of Google oss license plugin to Gradle plugin portal. As tested previously by @licaon-kter it should make the build reproducible. I added a json file containing information about released versions. See here for details. Let me know if further changes are required. |
Empty? https://github.com/fbarthelery/geekttrss/blob/1.6.5/versions/version_codes.json |
Your 1.6.5 apk is built from |
The file is updated after a release is made. So it was empty on the tag
Right, I guess it was a mistake on my side |
The version needs to be in the tagged tree, if you follow the commits maybe you can |
Come to think of it, if it's just an off-by-one (always!) then we can do +1 in the recipe |
I'm not sure I understand what you said. +1 to what ? version code? I'm trying to improve my release workflow, so let me try to recap. For a release, we should have a commit history looking like this:
The version tag is put on 1323. I'll build the apk on 1323 (not like this release where I build on 1324). I can make the tag after updating |
The tagged tree for 1323 needs to contain version.json and inside it must say... 13230000 (or whatever version code you want) |
Eg. https://github.com/fbarthelery/geekttrss/blob/1.6.5/versions/version_codes.json should have had 1.6.5 and 165082 or whatever the version was |
Ok I think I got a release workflow that will make this doable. you'll get
|
This builds reproducibly:
I'll make a merge request based on this, but Autoupdates need to be tested on next release I guess :) |
Sounds good 👍 I'll keep this opened until Autoupdates is fixed |
This is needed #28 and if merged now (in hg....repo) it won't mess with Reproducibility |
Merged and pushed to hg repo |
Oh ffs, I forgot about your rolling version code based on commit counting.... :( :) |
@fbarthelery when is this downloaded? https://github.com/fbarthelery/geekttrss/blob/1.6.5/app/src/main/java/com/geekorum/ttrss/articles_list/ArticleCard.kt#L310 What is |
@Preview functions are only run in Android studio to preview some ui components. They should normally be stripped from the final APK but I think I disabled stripping of unnecessary code s long time ago Write sync settings is used to enable the mechanism to synchronize all the articles from the server to the device |
The application is now available on F-Droid. Thanks for everyone who contributed to make it happen 🙏 I'll keep this open until we test auto update for the next release. |
kind reminder that v1.6.6 hasn't been pushed to fdroid (current latest is v1.6.5). Thanks! |
yes, because https://github.com/fbarthelery/geekttrss/blob/master/versions/version_codes.json should be sorted with highest on top... |
manually updated now https://gitlab.com/fdroid/fdroiddata/-/commit/462a4e0477b363be764a38ea9bbe6d04d9962255 but in the next release @fbarthelery pls sort them in reverse 😄 |
I'll think about it for next time 😄 but you should check the latest field if you can. |
@fbarthelery the regex stuff is not that advanced |
Looks like f-droid automatically update to 1.6.7 release this time 🎉 |
i'm fine with Play Store, but you would certainly gain users there
The text was updated successfully, but these errors were encountered: