-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide Github downloadable release #1256
Comments
What about the nightly builds? |
Would it not be possible to make use of the unattended app update API the same way Signal and Newpipe for example manage theirs? |
How do they do it? OpenTracks gives you four options (beside self compiling):
|
PlayStore releases are build by me. Quick question: why should the builds by the original devs be better? I would not trust my machine too much myself - so why would you trust it? Problem with F-Droid: it is kind of slow (5-10 days delay is normal), but that's not a real problem. And I would not use the GitHub Actions builds for anything critical (as it is not my Infrastructure that builds it). |
Same old argument: it boils down to who's infrastructure you want/ have to trust. If you want build from the developers of OpenTracks:
Or you use the one that is build by Github for almost every commit: https://github.com/OpenTracksApp/OpenTracks/actions?query=workflow%3A%22Build+nightly%22++ But as long as we don't have reproducible builds (#418), you have to trust somebody. |
You can't use e.g. obtainium or other apps to fetch the nightly builds from github. Usually apps are published under /releases/ but not the nightlies |
I often prefer getting my apps directly from devs and for the majority of my apps I use a feed app to track releases using githubs ability to append .atom to the release URL to notify of new releases. It would be great if you could provide a build on your release page too for this purpose to remove the dependency on F-Droid or using your repo page without the ability to track updates.
The text was updated successfully, but these errors were encountered: