-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(install): add msi #5922
feat(install): add msi #5922
Conversation
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.
Pretty good overall, but I'd recommend defaulting to a per-user install, which is congruent with your current Windows install instructions as well as other platforms' install instructions e.g., using home-brew.
@heaths the current installer is used by Winget/Scoop/Store who add the correct switches by default. Is that still a relevant change in that case? If there's an easy way to set the default, all in favor though. |
I'd still make the default per-user. One advantage of using an MSI - as long as you keep the same |
...though, more likely is someone install it via scoop or chocolatey and upgrade it via winget. The former two keep a manifest of what they installed and can upgrade, while winget will discover any MSI installed (uses the MSI APIs) and offer an upgrade based on its manifest if one is available regardless of how it's installed. That's why I've worked with partners on using MSI as the installer package rather than package manager-specific manifests: it's easy to get duplicative installs that way, but having a single registered package that dictates its default behavior works out regardless of how it's installed. |
87a3db7
to
07a657f
Compare
@heaths I think I got them all 😅 |
a7f3fdb
to
0d1b85e
Compare
0d1b85e
to
5ba39f3
Compare
Prerequisites