Enable building standalone package on macOS #315
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Are you wanting to build a macOS package yourself? I can't do it myself, since I'd have to be on Mac. What benefit would changing the native format to |
|
Yes, I've been building the package myself, but don't want to have to keep rebasing it every release before I build it. |
added 2 commits
April 21, 2019 13:21
The `installer` native type builds both 3rd party `pkg` and another intended for sending to the Mac App Store. That's generally not needed, so just build the 3rd party `pkg` by default.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
installeron macOSYou may want to consider changing the native format to
installeron all platforms (msi on Windows, pkg on macOS, RPM/DEB on Linux), rather thanimageon Windows (exe), but I didn't want to change that unilaterally.