git-point
git-point copied to clipboard
gitpoint
Add into F-Droid
Thanks @alejandronanez <3
And thank you @KOLANICH - if you think it will be useful to have in F-droid, we'll definitely get a PR up 🙌
Hi @Lionirdeadman, from what I understand in the include policy we are not eligible because we're using react-native-device-info which includes google-play-services :-/
Ah.. I see.. are there any plans to change this or should we expect Gitpoint to never be in F-droid?
If we shouldn't expect it to be in F-droid in the future, I think we can close this issue for now.
MicroG is system-level software, it doesn't change how the application is built so no.
The application would (probably) work fine with MicroG but that is completely irrelevant to F-droid inclusion.
The application would (probably) work fine with MicroG but that is completely irrelevant to F-droid inclusion.
As I understand, an app using GSF is forbidden to inclusion into f-droid because GSF is a proprietary near-monopoly (in the sense "nearly everyone have to use that proprietary app controlled entirely by Google (and the ones who control Google) and nearly every dev relies on it and of a phone lacks it most of consumers won't buy it") and the project maintainers wanna discourage usage and promotion of that monopoly.
MicroG is free software, it is included into f-droid and in fact f-droid encourages replacing gsf with it, and in the policy it is written
(either using microg or removing non-free deps completely).
I didn't know there was a way to replace Google libraries in apps using microG. My understanding was that they simply responded to those proprietary libraries. I guess I was wrong though.
Then maybe it's possible to replace them.
Accidentally, I found it had been added(https://apt.izzysoft.de/fdroid/index/apk/com.gitpoint), which was mentioned in #204. Is it the same thing?
No, it's not.
Izzy's repository only takes APKs from Github releases. He doesn't do anything to them.
The official F-droid repository requires all non-free code to be removed (can be done through a flavour) and they build the apk from source.
@chinesedfan so what is the status here? Appbrain's library scanner reports Firebase and GCM – both are show-stoppers for F-Droid. Is there a build flavor that comes without those?
@IzzySoft Sorry not. I contacted with @housseindjirdeh to learn how to publish new release, but he was busy these days. Once there were some progresses, I will update here. And at the same time, would you please send a PR to remove Firebase and GCM? It may not be merged to master, but at least I can use it to build F-Droid specified version.
Thanks, @Chandrasekar-G! And sorry, I'm no Android dev, so I cannot make that PR. And what you're suggesting comes close to another possibility: you could use "build flavors" to provide a "fully floss" flavor for F-Droid to use – and another one for e.g. Playstore.
and another one for e.g. Playstore.
IMHO - tracking iss unacceptable even in completely proprietary apps.
We had a request open at F-Droid which I'll now have to close, unfortunately, as the dependencies are still there. Going by the permissions, it's caused by using FCM and most likely dragged in via
apply from: "../../node_modules/react-native-code-push/android/codepush.gradle"
So should you one day have a foss build flavor, be welcome to reach out to us to either revive that RFP or open a new one.
PS, to clarify again above issue: this is not about GApps vs microG being available on the device. It's about those proprietary libraries included with your app. Unfortunately, there's no FOSS drop-in-replacement for FCM available yet. But there are some push alternatives if you want to have a look (that list is far from being complete, so hints for complementations are welcome, too).