-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Provide pure-floss build flavor #54
Comments
|
Gradle checks dependency before building, so it will try to find play-services and fail, because we dont have it on the buildserver. I can try to sort things out on our end, but having two separate build flavours is most likely the cleanest way to do it. |
|
I'll be creating two different builds of the application this summer as part of the v0.4.2 release. |
|
This is really appreciated! Many thanks! |
|
any word on that 0.4.2 release? can't wait! |
|
I've created a special fdroid branch and removed the GCM and billing deps from that branch. |
|
Thanks, should build tonight: https://gitlab.com/fdroid/fdroiddata/commit/cba5e67c |
|
@krt16s: You might want to remove push notifications from the app description, since the F-Droid version doesn't actually have those (no GCM). |
|
You are right, should be fixed tomorrow. |
|
@krt16s: You'll also probably want to remove that last "and". |
This app includes Google's proprietary play-services depedency, what is it used for? Could you provide a pure-floss gradle flavor that does not require this (e.g. by stripping functionality or using floss alternatives)?
The text was updated successfully, but these errors were encountered: