I think it should be slightly special, in that the vast majority of cases people will want to run this command is when they're about to do init. For the sake of pedagogy (and making people Update Update Update), it would be nice if update just ran init for you by default. As such I propose the following slightly weird semantics:
[x] By default this should assume it should only be run in a dir you could run cargo dist init in
[x] Add an --only-bins flag or something to opt out of this requirement
[x] If installed (or if no updates needed), re-exec as the new binary and run init
[ ] Add a --reinstall flag or something to force the updater to assume the application is out of date and should be refetched (useful for testing)
[x] Add a --version flag to pick a version to install (useful for testing)
[ ] Add a --??? flag to say "hey generate an installer script and use that instead of fetching"
Gankra
commented
3 months ago
Add
cargo dist updatecommand.I think it should be slightly special, in that the vast majority of cases people will want to run this command is when they're about to do
init. For the sake of pedagogy (and making people Update Update Update), it would be nice ifupdatejust raninitfor you by default. As such I propose the following slightly weird semantics:cargo dist initin--only-binsflag or something to opt out of this requirementinit--reinstallflag or something to force the updater to assume the application is out of date and should be refetched (useful for testing)--versionflag to pick a version to install (useful for testing)--???flag to say "hey generate an installer script and use that instead of fetching"