Hallo,
it is not about to pass a container to users. The benefit would be to pass
* a routine to developers to reliable create a package for their applications
* have an environment to verify if the kivy applications can be build at all
Coming to the point, if it is practical to create the full environment for each built?
1) I am not sure, if this is really the case , as reading the docs, there seems to be an option to cache files between builds
2) Even if not, it still would give one a reliable build environment
Please keep in mind, that this forum is full of user reported buildozer problems.
My preferred solution would be a single action which archives the following
* Checkout the repository (as required by github)
* Run a pre user script to prepare the sources and copy them to a tempory folder (customizable and part of the user git repository)
* Install the build requirements
* Copy the buildozer.spec file (customizable and part of the user git repository)
* Perform the build
* Run a post user script to (customizable and part of the user git repository)
* This single script should be tested against the showcase example from the kivy examples. Maybe a further examaple which includes gstreamer and atlas creation
* This script should build for for the main android versions (6,7,8,9,10) /apis (editable)
* This script should build for windows as well (multi platform is one of the main features of github actions)
* This script should build for OSX as well (multi platform is one of the main features of github actions)
* Not shure if it would be possible to build for IOS as well
If the script builds from specified versions (and not Master! not p4a Master) if could be a solution to reliable build kivy apps to several versions, without tweaking around without Virtual images and versions.
I know , this I a big ask with a lot of work to spent, but in my opinion worth the work
Cheers
Carsten