-
Notifications
You must be signed in to change notification settings - Fork 76
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
Setting the archive binary name #42
Comments
magni-
added a commit
to rainforestapp/go-github-selfupdate
that referenced
this issue
Jul 19, 2021
This will default to the existing behavior: using the name of the currently running executable. Fixes rhysd#42
magni-
added a commit
to rainforestapp/go-github-selfupdate
that referenced
this issue
Jul 20, 2021
This will default to the existing behavior: using the name of the currently running executable. Fixes rhysd#42
magni-
added a commit
to rainforestapp/go-github-selfupdate
that referenced
this issue
Jul 20, 2021
This will default to the existing behavior: using the name of the currently running executable. Fixes rhysd#42
uubulb
pushed a commit
to uubulb/go-github-selfupdate
that referenced
this issue
Dec 5, 2024
This will default to the existing behavior: using the name of the currently running executable. Fixes rhysd#42
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please excuse me if I have overlooked something, but is there a way to manually specify the binary name in the downloaded archive?
Currently it appears to be hardcoded to the running binary name, however if
myapp
was renamed locally tomyapp-dev
, then the update fails because "myapp-dev" doesn't exist in the archive.Ideally there should be a way to set the binary name the updater should look for in the archive, so that
myapp-dev
would get updated with themyapp
binary in the archive.The text was updated successfully, but these errors were encountered: