This is one area that the Go ecosystem leaves me wanting a bit more. Idiomatic Go says that my package should be go-gettable, which AFAIK just uses `go install` command after fetching dependencies.
Is there an idiomatic way to include build options/tasks, while remaining go-gettable?
I guess that's pretty reasonable. Especially coupled with sensible defaults for your variables like "unreleased" in the article. If you're building for a release you're probably a lot more up-to-speed on the needs for a release build anyway.
Is there an idiomatic way to include build options/tasks, while remaining go-gettable?