thanks, I think when project becomes big, all code must under GOPATH may not able to meet realworld env,
I just didn't meet this issue yet, my code are not much. 在 2017年8月19日星期六 UTC+8上午11:31:16，Maurizio Vitale写道： > > Not everybody wants to accept that all projects have to live under a > unique GOPATH. > > For instance I want to be able to clone a project and build it wherever I > want. I might even want to have more than one sandbox with the same > project. Or golang projects that are deep inside another project tree. > I achieve this by building inside a container (so in a sense inside the > container GOPATH is as the golang gods intended it). I tried other > approaches (like multiple directories in GOPATH), but ended up having even > more problems. > I still have a few problems with some tools, but mostly because I didn't > spend enough time to containerize them. > > On Fri, Aug 18, 2017 at 6:43 AM, Fino <xme...@gmail.com <javascript:>> > wrote: > >> Hello, >> >> Can I ask for a typical use case? >> >> BR fino >> >> -- >> 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...@googlegroups.com <javascript:>. >> 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.
