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 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" aware of protoc and (optionally/when needed) able to > generate the .pb.go as needed ? and maybe a generalization, go get have > some way to read some manifest/makefile-ish description telling it to run > some (safe/approved) code generation step) > > Thanks ! > Laurent > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
