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
{{ message }}
This repository has been archived by the owner on Aug 14, 2020. It is now read-only.
goaci currently only supports a single package and a single executable (that which gets produced by go get <package>). Should we consider adding support for multiple packages/executables? What would this look like?
The text was updated successfully, but these errors were encountered:
I don't think supporting multiple executables in one go is sensible - it complicates things too much. My idea is as follows (and I already implemented it, so a PR is coming soon):
My assumption is that go get example.com/foo/bar will produce exactly one binary. This assumption does not hold for go get example/foo/bar/... where several binaries might be built.
For the former, goaci creates bar.aci with example.com/foo/bar as a name in manifest and with whatever binary go get buiilds.
For the latter, user has to use --use-binary option to select which binary should be put into image. Assuming that user passed --use-binary quux the result of goaci would be bar-quux.aci with example.com/foo/bar-quux as a name in manifest and with quux binary.
goaci
currently only supports a single package and a single executable (that which gets produced bygo get <package>
). Should we consider adding support for multiple packages/executables? What would this look like?The text was updated successfully, but these errors were encountered: