Skip to content
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

Merged
merged 1 commit into from
Nov 23, 2024
Merged

feat(install): add msi #5922

merged 1 commit into from
Nov 23, 2024

Conversation

JanDeDobbeleer
Copy link
Owner

Prerequisites

  • I have read and understood the contributing guide.
  • The commit message follows the conventional commits guidelines.
  • Tests for the changes have been added (for bug fixes / features).
  • Docs have been added/updated (for bug fixes / features).

@JanDeDobbeleer JanDeDobbeleer marked this pull request as draft November 23, 2024 08:53
Copy link

@heaths heaths left a 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.

packages/msi/README.md Outdated Show resolved Hide resolved
packages/msi/README.md Outdated Show resolved Hide resolved
packages/msi/oh-my-posh.wxs Outdated Show resolved Hide resolved
packages/msi/oh-my-posh.wxs Outdated Show resolved Hide resolved
@JanDeDobbeleer
Copy link
Owner Author

@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.

@heaths
Copy link

heaths commented Nov 23, 2024

@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 UpgradeCode and change the ProductCode and ProductVersion (any of the first 3 fields; the 4th is ignored) with each revision - no matter how a user gets it, it'll always be installed or upgraded. Don't depend on a single chained or package manager. Someone could install it via widget but upgrade it later via scoop. And different package managers require different managers or even default per-user or per-machine contexts differently. Let the MSI dictate the defaults.

@heaths
Copy link

heaths commented Nov 23, 2024

...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.

@JanDeDobbeleer
Copy link
Owner Author

@heaths I think I got them all 😅

@JanDeDobbeleer JanDeDobbeleer force-pushed the windows-msi branch 3 times, most recently from a7f3fdb to 0d1b85e Compare November 23, 2024 17:18
@JanDeDobbeleer JanDeDobbeleer marked this pull request as ready for review November 23, 2024 17:18
@JanDeDobbeleer JanDeDobbeleer merged commit 6bc8756 into main Nov 23, 2024
9 checks passed
@JanDeDobbeleer JanDeDobbeleer deleted the windows-msi branch November 23, 2024 19:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants