gallium icon indicating copy to clipboard operation
gallium copied to clipboard

feature request - bundle as a .pkg

Open joeblew99 opened this issue 8 years ago • 2 comments

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

joeblew99 avatar Nov 17 '16 14:11 joeblew99

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?

alexflint avatar Nov 18 '16 17:11 alexflint

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?

alexflint avatar Nov 18 '16 21:11 alexflint