-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
fix(bundler): store and remove old main binary on updates if main binary name has change #10962
Conversation
…ary name has change
Package Changes Through 7e5d257There are 2 changes which include tauri-bundler with prerelease, tauri-cli with prerelease Planned Package VersionsThe following package releases are the planned based on the context of changes in this pull request.
Add another change file through the GitHub UI by following this link. Read about change files or the docs at github.com/jbolda/covector |
33c85f2
to
ce11113
Compare
@@ -637,6 +637,15 @@ Section Install | |||
WriteRegStr SHCTX "${UNINSTKEY}" $MultiUser.InstallMode 1 | |||
!endif | |||
|
|||
; Remove old main binary if it doesn't match new main binary name | |||
ReadRegStr $0 SHCTX "${UNINSTKEY}" "MainBinaryName" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this delete the binary on each install? since the v2 installer also uses the same key.. maybe we should use a different one for v2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no this key will be removed when running the uninstaller, so it is only valid when doing updates. It has to be the same key for every installer (whether v1 or v2) so it can detect main binary name changes on updates
ref: #10952