> Docker add, or whatever is pushing files into your container is probably not respecting timestamps so the .a files are older with respect to .go files (pkg sorts above src)
I'm bind-mounting the pkg dir in there so it shouldn't be a question of timestamps (not ruling out something going on there). Those are the "real" files. > Why do you want to build inside a container, is that just adding an extra level of indirection to what is a simple process? Using containers gives us a lot of control over the build without mandating a lot of set-up on each developer's machine (they need make and docker installed). For example, using a container locks the build to the correct libc and version of go and it ensures the that project documents (in code) all the required dependencies and doesn't depend on local dev environment. It also lets developers use Linux Mac or Windows and still be able to build the product in the right environment. Beyond that, it lets us build all kinds of artefacts that previously would have required several dedicated (crufty) build machines: we can use a container to build debs and RPMs, on a Mac, for example. On Wednesday, December 7, 2016 at 9:57:51 PM UTC, Dave Cheney wrote: > > Docker add, or whatever is pushing files into your container is probably > not respecting timestamps so the .a files are older with respect to .go > files (pkg sorts above src) > > Why do you want to build inside a container, is that just adding an extra > level of indirection to what is a simple process? > -- 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.
