-
Notifications
You must be signed in to change notification settings - Fork 68
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
Predictable release #108
Comments
Loading custom cores will still always be an option though, right? |
Yes, just stick them in ludo/cores directory.
Radius made a libretro-meta repo with some of these goals. We should really consider tagging releases of cores to help the situation. Running nightly all the time can be problematic. |
That's not bad. On my side, I've tried setting up travis+github releases on cores. See my PR in the snes9x repo. It works well most of the time. We just need to convince the libretro team to use it. |
This should already check that the core was downloaded #142 |
The Makefile currently downloads the latest cores from the libretro buildbot during the build.
These cores may be at some point in time buggy.
We need to find a way to always pull an exact version of these cores.
In Ludo, the user shouldn't be in charge of testing and choosing the right cores and core versions. We have to do it for them in a reliable way.
The text was updated successfully, but these errors were encountered: