Hi, Thanks for the positive feedback. I'm currently doing some research.
As far as I understand, it's currently not possible to run a user-defined docker container for builds for f-droid. Thus, we would have to recreate the build-environment to run in the containers that the f-droid build environment uses.
But first let's see if I get the build setup that subsurface uses: * The whole android build runs in a docker container as defined in https://github.com/subsurface/subsurface/blob/master/scripts/docker/android-build-container/Dockerfile o This is basically installing QT (currently 5.15.1) and android SDK/NDK (currently platform 21) * then the build script is executed: packaging/android/qmake-build.shSince F-Droid (the repository) seems to be quite restrictive about how the software should be built (must be built on their own infrastructure using only source code - so no pre-built QT for example), another way could be to create a F-Droid repository for subsurface using the github build artifacts. This would not help with visibility (since it's not visible in F-Droid without installing the repository), but would enable automatic updates for F-Droid users.
If this would be the way forward, I think two repositories would make sense: * Nightly (automatically updated from the nightly github builds) * current / weekly / release (the releases that are currently on the webpage)Since these APKs are the same that are also linked on the webpage, it should(tm) be possible to switch over from manually installed to F-Droid.
Here I have the question: How is the release-process for the "current" builds? I've seen that there are basically some APKs in a download folder, but I couldn't find any information if they are manually copied or if there is some automation going on.
Christof On 24.05.24 04:04, Michael Keller via subsurface wrote:
Hi Christof. On 24/05/24 12:10, Dirk Hohndel via subsurface wrote:I definitely think that there would be interest. I have tried to go through the process a couple of years ago and couldn't figure it out.But yeah, if you want to get a working build put together, I'd love that. /DOn May 23, 2024, at 12:01, Christof Arnosti via subsurface <[email protected]> wrote:Hi,I currently only half-heartedly follow the mailing list, so please excuse if I missed some discussion.As far as I understood, subsurface is not published on Play Store anymore due to the ever-changing requirements, which make it hard to actually publish it. This got me thinking: As far as I know all components needed to create a working subsurface APK are open source. This means that subsurface should manage to meet the Inclusion Policy of F-Droid (https://f-droid.org/en/docs/Inclusion_Policy/).Thus I wanted to ask if there would generally be some interest to include Subsurface in the F-Droid store. If yes, I could try to take some time to check if I manage to get a working build of subsurface for F-Droid (no promises about finding the time and technical success tho!)Yes, I think it's definitely a good idea.From having a quick look at the F-Droid page, they seem to be requiring a fully automated build of the application on their infrastructure. To get this going, the piece de resistance will be the Qt build.For Android, we are currently using a docker-image with a manually pre-built Qt installation (https://hub.docker.com/r/subsurface/android-build, which uses the Qt installation from https://hub.docker.com/r/subsurface/android-build-container). So unless F-Droid allows the use of docker images for their builds the Qt install on these images will have to be replicated in an automated way.Cheers Michael Keller _______________________________________________ subsurface mailing list [email protected] To unsubscribe send an email [email protected]
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ subsurface mailing list -- [email protected] To unsubscribe send an email to [email protected]
