You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment the bundling produces a ".app", however its possible with golang to produce a ".pkg" so that the end user gets a decent install experience, and we are developers get control about where things are places and file ACLS assigned etc.
It will also help with getting projects into a CI and CB pipeline, and prepare for continuous updates if we want to integrate that later.
Great resources, thanks @joeblew99. We should definitely provide a good bundling option. It seems like there are three possible build artifacts that we might want to output: .app, .pkg, and .dmg. For UI applications that ultimately end up in /Applications, it seems like it's standard to have a .dmg containing a .app. Given that, do you think we also need a .pkg option?
Also, pkgbuild will build a .pkg, but do you know whether that pkg will eventually install the executable go binary directly on the user's computer, or will it ultimately install a .app containing the go binary?
i noticed the recent work on the bundling at https://github.com/alexflint/gallium/blob/master/cmd/gallium-bundle/bundle.go
looking awesome !
At the moment the bundling produces a ".app", however its possible with golang to produce a ".pkg" so that the end user gets a decent install experience, and we are developers get control about where things are places and file ACLS assigned etc.
It will also help with getting projects into a CI and CB pipeline, and prepare for continuous updates if we want to integrate that later.
This is the way the golang team does it and its quite simple.
https://github.com/golang/build/blob/master/cmd/release/releaselet.go#L149
It will only build on OSX.
it calls out to pkgbuild & then productbuild for final signing for users.
Its described well here:
http://thegreyblog.blogspot.de/2014/06/os-x-creating-packages-from-command_2.html
I think its very complete.
Please let me know what you think....
The text was updated successfully, but these errors were encountered: