CTCCI exists
Alright, would it be possible to at least create a README.md in that folder and but a comparative table of which module is included on which package ?
Though for now I'll settle for a package which contains all modules.
Any server
Actually, I don't only volunteer to create the app but also to host it.
Any backend built for this should have strict requirements on how it does things like caching, or overall build resource usage.
Would you guide me through this ?
Since I'm not experienced at all on APK builds, the only optimization I'd implement by myself is preventing from rebuilding APKs for a combination of modules that already have been built.
I do not have a non-Linux dev environment, and sadly do not have an interest at the time to try and maintain CTCCI for more than just linux.
Even if you'd maintain CTCCI for non-Linux environments, the final objective wouldn't be reached : it will still require a computer, minimal developer skills, and won't be user-friendly.
you’re still looking at a potentially huge amount of power to dedicate
That's not an issue for me. Plus, I won't allow more than a single simultaneous build anyway.
This is something I may be willing to sponsor, though I’m not interested in developing this right now
I don't need anyone to either sponsor it nor develop it. The only thing I need is assistance for using CTCCI.
it concerns me regarding updates
I don't start end-user projects that I wouldn't intend to keep up to date. And it will be FLOSS anyway.
also about patches that clash, patches that require a specific application order, patches that rely on each other etc.
That will be what I'll need help for. If you can guide me through these specifications, I'll make my app behave the right way.
friends etc do request their own builds sometimes, which do get added
This this a perfect example to demonstrate the inequality I'm going to solve.
Thanks !