add zom.im to f-droid

[anarcat]

it seems there was an effort (#98) to provide zom.im binaries on f-droid, but the app has been mysteriously disabled in the build and is not actually available in f-droid.

[n8fr8]

Hmm, not sure why it was disabled. I will check with F-Droid on that.

[stpr-dev]

@n8fr8 Any updates on this? I just read that ChatSecure reached its EOL and Zom looks interesting. Only problem is getting on f-droid. If you can get that up and running it would be great!

[takiainen]

I'd like to see this on F-Droid as well. Any news?

[ghost]

+1

[mimi89999]

@anarcat @n8fr8 Done.

[anarcat]

@anarcat @n8fr8 Done.

where? i don't see it on my f-droid client here...

[hex-m]

The metadata is in the f-droid repo. So no idea what's wrong (but curious).

[ghost]

@hex-m So is it the problem of F-droid side? 😕 hmm

[testbird]

Is this still in the works? Blocked somewhere?

[rojoweko]

According to this post Zom cannot be added to the f-droid repo because it contains JARs: https://gitlab.com/fdroid/fdroiddata/issues/914

This is the last zom build log from f-droid: https://f-droid.org/wiki/page/im.zom.messenger/lastbuild_1510019

Is there a chance to get rid of the JARs while preserving the OMEMO capabilities?

[Bubu]

I'll add this here:

There are 4 commonly used ways to deal with binary artifacts (with my subjective assessments):

• Get them from trusted Maven repositories. The most maintainable way. For example okhttp 3.5.0 is in Maven Central.
• Add libraries source code into the main app tree as Git submodules and build them along with the app itself. Consumes both build and maintenance time.
• Make build system check whether JARs are present and if not, download source tarballs and build them. This usually turns into a big and fragile shell script and is even less maintainable then previous option.
• Build JARs from source code on F-Droid side (srclibs mechanism) and use them instead of upstream-supplied ones. Rather robust but implies manual fdroiddata updates.

[relan]

Just checked that F-Droid successfully builds and verifies 15.3.0-FINAL and 15.3.1-beta-2. JARs are still the only issue preventing Zom from being on F-Droid.

[ghost]

@relan pretty sure if Zom in F-Droid, it could get rid all other privacy-first messaging apps from installation rank.

[gsantner]

@ owners is there interest into getting into fdroid mainline? if so, jars have to be removed and replaced by libs from allowed repos as said above.

[n8fr8]

Understood. We are hopefully moving to the public smack-omemo gradle dependencies instead of our builds. Just waiting for them to publish the necessary version.