F-Droid build failed #2

linsui commented 2025年04月25日 08:40:13 +02:00

 implementation(libs.play.services.wearable)
 implementation(libs.kotlinx.coroutines.play.services)

These libs are not FOSS. Could you please add a flavor without them? Thanks!

``` implementation(libs.play.services.wearable) implementation(libs.kotlinx.coroutines.play.services) ``` These libs are not FOSS. Could you please add a flavor without them? Thanks!

jexner commented 2025年04月25日 09:27:59 +02:00

Uff, that is an aspect I had not thought about.

v1.1.1 is all about that, and only that: share processes with a Wear OS device.

Let me think...

Uff, that is an aspect I had not thought about. v1.1.1 is all about that, and only that: share processes with a Wear OS device. Let me think...

jexner commented 2025年04月25日 09:37:43 +02:00

So MicroG may have a replacement for the first one: https://github.com/microg/GmsCore/tree/master/play-services-wearable, that's a good start

So MicroG may have a replacement for the first one: https://github.com/microg/GmsCore/tree/master/play-services-wearable, that's a good start

jexner commented 2025年04月25日 10:04:27 +02:00

And the other one may not be needed.

(削除) Let's do this! (削除ここまで)

If I get it right, using MicroG is not possible on standard Android phones. So that's that plan out the window.

@linsui : my only other option is to maintain two versions, correct? One that is 100% FOSS, and another that can work with the wearable libs.

And the other one may not be needed. ~~Let's do this!~~ If I get it right, using MicroG is not possible on standard Android phones. So that's that plan out the window. @linsui : my only other option is to maintain two versions, correct? One that is 100% FOSS, and another that can work with the wearable libs.

licaon-kter commented 2025年04月25日 14:08:48 +02:00

It's not about the use of microG of the users, but about replacing the Google proprietary lib with microG libs, and those might work with both Play Services or microG, or none, whatever the user has.

(Note: I'm not sure how much or if microG covers your case here though) :)

It's not about the use of microG of the users, but about replacing the Google proprietary lib with microG libs, and those might work with both Play Services or microG, or none, whatever the user has. (Note: I'm not sure how much or if microG covers your case here though) :)

jexner commented 2025年04月25日 14:53:39 +02:00

OK, that makes sense.

Trying a build now.

OK, that makes sense. Trying a build now.

jexner commented 2025年04月25日 15:32:50 +02:00

Nope, no luck. It looks like the whole sync stuff around wearables is missing, DataClient, CapabilitesClient, ...

Nope, no luck. It looks like the whole sync stuff around wearables is missing, DataClient, CapabilitesClient, ...

linsui commented 2025年04月25日 16:08:42 +02:00

It doesn't build or it doesn't work?

It doesn't build or it doesn't work?

jexner commented 2025年04月25日 17:11:41 +02:00

A lot of the classes I need do not exist in MicroG, so it doesn't compile :-(

Next step: find out how I can manage two flavours with as little overhead and hassle as possible...

A lot of the classes I need do not exist in MicroG, so it doesn't compile :-( Next step: find out how I can manage two flavours with as little overhead and hassle as possible...

jexner commented 2025年04月26日 14:59:58 +02:00

Fixed by 46a591c870

Fixed by 46a591c87021ab1ebc70ebc1857808163a4a8113