F-Droid version is outdated

[CrimsonFork]

It's still 1.1.1.0

[hrydgard]

The F-Droid build is not maintained by the project, it was done by some volunteer. It would be great if a new one would step up.

[CrimsonFork]

Well, I don't know how it works, but is it really so complicated?

[hrydgard]

It's probably not complicated, I just don't really know what exactly F-droid is or how it works, other than it being some sort of repository for open source Android apps. Hasn't really been on my radar.

[0x647262]

I'm looking into this.

[CrimsonFork]

Finally! Someone! Our fate rests upon you!

[0x647262]

@hrydgard

If you have a few minutes, I've been doing some digging...

https://f-droid.org/wiki/page/Inclusion_Policy

• We cannot build apps using Google's proprietary "play-services". Please talk to upstream about an untainted build flavor (either using microg or removing non-free deps completely).
• We cannot build apps using proprietary tracking/analytic dependencies like Crashlytics and Firebase. Please talk to upstream about an untainted build flavor (either using a FLOSS analytics software like ACRA or by removing non-free deps completely).
• We cannot build apps using proprietary ad libraries. We have nothing against advertisements (see AntiFeatures), but they must be provided by a FLOSS compatible way.
• We cannot build apps requiring non-free buildtools, including Oracle's JDK or some pre-release toolchains.

If I remember correctly, PPSSPP used (might still be using) analytics libraries? I'm not sure I can answer the rest of those without digging into the code a bit more...

That said, moving the build system over from those ab.cmd and ab.sh scripts would be quite useful... Moving to something like Android Studio would allow simplified building from the command line with tools like Gradle.

Links:

• https://developer.android.com/studio/build/building-cmdline.html

• https://developer.android.com/studio/intro/migrate.html

[Orphis]

We have an experimental branch to build with Gradle + CMake actually. It's waiting on some packages with bug fixes we need being promoted from beta to release. Then, you will be able to build using Gradle. But the aforementioned scripts are simple enough, even if they aren't standard. What issues do you have with them?

[0x647262]

No problems, just increased simplicity.

More "standardized".

[hrydgard]

PPSSPP no longer use anything from Google Play services. No analytics. So we should be fine there.

[0x647262]

"Blocker" - https://github.com/hrydgard/ppsspp/pull/9038 has been merged.

I'll start work on this shortly.

[hrydgard]

Hm, so what APK signing is used on f-droid? Debug signing or what? If you need to add an additional "flavor" to the gradle file with some special signature that's alright.

[0x647262]

@hrydgard would you be opposed to me migrating the build system over to gradle?

Additional deatils (as they pertain to ppsspp) here: https://developer.android.com/studio/intro/migrate.html

[hrydgard]

@Krakn The current build system for Android is already gradle+cmake (though we do keep the old ant/Eclipse build as well). Or do you mean just switching the f-droid build to use gradle? Go right ahead. I'm not sure how f-droid does signing, btw?

[0x647262]

I was using my outdated fork that was missing the cmake + gradle commits... My bad on that one.

I'm looking into how F-Droid handles signing now.

[hrydgard]

There's support in the gradle scripts for using a certificate specified in .gradleproperties, if f-droid uses its own cert. If debug keys is enough, just do gradle assembleOptimized.

[0x647262]

Status:

• [x] Building on local machine
• [x] F-Droid build environment set up
• [x] Building with F-Droid's build servers
• [ ] Published to F-Droid's repositories

[ghost]

@devopsdeluxe Any news?

[0x647262]

I had some large life changes recently and this fell off my radar. :(

I'll see if I can get things completed this weekend!

[ghost]

Sorry to hear..

Well, I hope you get things going! Thanks.

[0x647262]

Update: https://gitlab.com/fdroid/fdroiddata/issues/1030

[0x647262]

I just need to test the built apk and we should be in business. I'll ping hrydgard if I need signing materials.

See: https://gitlab.com/fdroid/fdroiddata/issues/1030

For details.

[0x647262]

I've picked this up again and am nearing completion: https://gitlab.com/fdroid/fdroiddata/issues/1030

I'm hoping to have the build published by the end of this week.

[unknownbrackets]

Just a warning: we're planning to release v1.6.0 sometime in the near future. See #10773.

-[Unknown]

[0x647262]

@unknownbrackets Thanks for the head up!

Assuming I created a sane metadata entry on fdroid's side, the version bump (1.5.4 -> 1.6.0) should just be a quick copy & paste job.

[0x647262]

https://gitlab.com/fdroid/fdroiddata/merge_requests/3083

[CrimsonFork]

Yay

On July 10, 2018 12:18:56 PM GMT+02:00, Emulatorer [email protected] wrote:

UP

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/hrydgard/ppsspp/issues/9112#issuecomment-403773921

-- Sent from my Android device with K-9 Mail. Please excuse my brevity.

[0x647262]

I work in Valve™ time :sob:

Awaiting further review: https://gitlab.com/fdroid/fdroiddata/merge_requests/3083

[0x647262]

@hrydgard

https://gitlab.com/fdroid/fdroiddata/merge_requests/3083#note_106964068

I'm not an Android guru, is there anything we can do about that module? As far as I am aware, it would prevent PPSSPP's inclusion in F-Droid (don't quote me on that, I'll need to check with their upstream... It might just be an anti-feature).

I will also be bumping the F-Droid version to 1.7.

[Florin9doi]

Stubs for com/bda/controller ?

https://github.com/Florin9doi/ppsspp/commit/b0ec49309eadc1218652b7be5a513e2a7cd2494f ?

[unknownbrackets]

That seems like an option imho (assuming it works.) Though not sure about "Maga". Maybe "MogaStubs" would be better, or something.

-[Unknown]