-
Notifications
You must be signed in to change notification settings - Fork 15
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
Install DraStic directly into cores instead of requiring a migration script #67
Comments
The migration process is a bit obfuscated, but let me try to break it down: Compile Time
Run Time
The version of Drastic is included in the migration name as a hack so that when Drastic is updated, we can rename the migration and existing installations will re-run the migration. For updating Drastic, you can simply rename all references of drastic-1.7 to 1.8, update the download link, and test that the launch.sh patch still works. |
Should emulators be installed/updated via migrations? These seem fairly slow to run and kinda frustrating for a first-time user to perform. |
You're right, maybe Drastic should be bundled. |
Ditto for the other migrations actually. I first booted it up and it started running them and seemed to stall but it wasn't clear where (the text output by the launch scripts isnt output anywhere). |
8928bac updates DraStic to 1.8. I'll leave this issue open for moving DraStic into cores directly instead of through a migration. |
Is there a way to upgrade emulators? I'd like to contribute an update of drastic and I see references to migrations and such, so its not super clear how to go about this...
The text was updated successfully, but these errors were encountered: