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

Support standard macOS pkg distribution method #61

Open
ygini opened this issue Aug 16, 2019 · 2 comments
Open

Support standard macOS pkg distribution method #61

ygini opened this issue Aug 16, 2019 · 2 comments
Assignees

Comments

@ygini
Copy link

ygini commented Aug 16, 2019

Hello,

Current distribution method of Kitura CLI is based on homebrew or npm, booth solution with security issue, poor respect of the macOS file system, and 0 mass deployment capabilities.

Please, support distribution of standard macOS package for Kitura CLI using github release system. This will allow sysadmin to automatically distribute and keep Kitura CLI updated on a whole fleet using the well know autopkg/munki or autopkg/jamf setup.

If for some reasons, you can't comply with this request, consider as an alternative to publish Kitura CLI with MacPort instead or in addition to homebrew. MacPort has a more robust distribution design and is able to create pkg from an admin workstation to distribute on a fleet without having to install it on the fleet itself.

Or eventually do both, macOS pkg with github release and MacPort support, that would be the best option.

@ianpartridge
Copy link
Contributor

Hi, thanks for raising this. We do plan to do exactly as you request, and offer releases via GitHub releases!

@djones6
Copy link
Contributor

djones6 commented Aug 19, 2019

@ygini I am updating the release process for the CLI in #62 - as part of that, the macOS binary (standalone executable) will now be attached to each GitHub release in a .tar.gz.

This is the source for the Homebrew formula but can also be manually installed. It could form the basis of a macOS pkg, but that's beyond the scope of the work I'm doing here.

If you feel motivated to build on #62 to generate a (signed or unsigned) pkg as another installation option, then you'd be most welcome to raise a PR.

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

No branches or pull requests

3 participants