discuss: production & development

[mattn]

Note: This may be early discussion.

AFAIK, dep install all of dependencies into vendor directory without looking build constraints. This is useful to build binaries for each targets. But there are people who want to build with build tag.

https://github.com/mattn/go-sqlite3

In the case of go-sqlite3, dependencies changes with build tag. I believe this use-case is not a little. For example, Ruby's Gemfile support to separate installing gems for production or development. gom also. ex: Using postgresql on the production, using sqlite3 on development.

One of the way to support this, changing format of manifest.json. to separate sturecture by named with build tags. The second is separate filename for the build tags like manifest-$(buildtag).json or manifest-$(SOME_ENVIRONMENT_VARIABLE).json

Additional

Another way: separate branches for production & development. And manage differerent manifest.json on each branches.

[sdboyer]

i'm gonna close this one up. i get how it makes sense in other languages, but it just hasn't seemed to be relevant in Go - in the last ten months, i don't think it's come up more than one or two offhand times in discussions (outside of this issue).