On 20 Jan 2019, at 20:20, Tycho Andersen <ty...@tycho.ws<mailto:ty...@tycho.ws>> wrote:
That's how I have it now. The problem with this is that in the face of modules, it re-writes the go.mod and go.sum files to not include the deps of the binary it's not currently building, so you end up with a bunch of unnecessary churn there. So it really does need to be in one go command. This is the central problem of yours, but it isn’t how the toolchain works for me and I don’t think it’s how it’s intended to work. Clearly you should be able to build individual packages inside a module without losing dependency information. Are you sure you don’t have a step in your makefile that removes the go.mod? Can you share a complete module that exhibits this behavior for you? //jb -- 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.
