Re: [go-nuts] go get and protos (protoc; grpc)

2017-07-29 Thread Timothy Raymond
I've used `go generate` and typically check in the generated *.pb.go. There's some formatting weirdness when contributers have different versions of the `protoc` binary, but nothing that causes anything to break. -- You received this message because you are subscribed to the Google Groups "gol

Re: [go-nuts] go get and protos (protoc; grpc)

2017-07-28 Thread Henrik Johansson
The consensus seems to be to generate and checking artefacts such as this. It does help with reproducibility and doesn't force the enduser to install all kinds of possibly weird tools. fre 28 juli 2017 kl 20:46 skrev 'Laurent Demailly' via golang-nuts < golang-nuts@googlegroups.com>: > This might

[go-nuts] go get and protos (protoc; grpc)

2017-07-28 Thread 'Laurent Demailly' via golang-nuts
This might be a FAQ or just my newcomer to go lack of knowledge, please kindly point me in the direction if this is the case: Is there any way today or work in the future to make "go get" work with projects that have .proto files, without checking in the .pb.go generated file ? (ie have "go get