-
Notifications
You must be signed in to change notification settings - Fork 1
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
Reduce burden on users and maintainers via upgrade scripts #10
Comments
The main reason for keeping this in rust is so that the migrators can use the underlying capability provided by I am not sure about And I guess for some easy migrators that don't need all that complex stuff, we can provide an alternative way to define the script.
Definitely agree. Which is why we build the tool in |
Yeah, I fully agree that doing my suggestion would require writing a lot of bindings, the more featureful the scripts supported, the more bindings required. |
Requiring users to pull and build large dependencies for one-off upgrades is a barrier to adoption.
What if
cargo-up
support rhai or lua upgrade scripts? We only need to compile or install a pre-built binary of `cargo-up. Crates could include the scripts in pre-determined locations in crates so they can be automatically be detected and ran.The text was updated successfully, but these errors were encountered: