Yes I understand. I was just wondering if the GOCACHE flag is permanent or as a temp safety in case someone encounters a bug in the caching.
On Mon, Feb 19, 2018, 21:35 Ian Lance Taylor <i...@golang.org> wrote: > On Mon, Feb 19, 2018 at 12:08 PM, Henrik Johansson <dahankz...@gmail.com> > wrote: > > Ah, that's not what I meant but GOCACHE var itself and if it will be > > permanent as a way to disable the cache. > > Sorry, I'm not sure exactly what you are saying. There is no way to > permanently disable the cache, other than always setting the GOCACHE > environment variable every time you run the go tool. > > Ian > > > On Mon, Feb 19, 2018, 21:00 Ian Lance Taylor <i...@golang.org> wrote: > >> > >> On Sun, Feb 18, 2018 at 11:00 PM, Henrik Johansson < > dahankz...@gmail.com> > >> wrote: > >> > > >> > Why I wondered was because to build script (a tiny settings file > really) > >> > for > >> > Archlinux uses this flag to build it's Go packages. > >> > Is it available as a paranoia "i really need all the tests run"? Will > it > >> > be > >> > removed later on? > >> > >> Sorry, I don't know. I don't know who wrote that script or why it sets > >> GOCACHE. > >> > >> Ian > >> > >> > >> > sön 18 feb. 2018 kl 23:04 skrev Ian Lance Taylor <i...@golang.org>: > >> >> > >> >> On Sun, Feb 18, 2018 at 11:22 AM, Henrik Johansson > >> >> <dahankz...@gmail.com> > >> >> wrote: > >> >> > The GOCACHE variable. What is it's effect when building Go itself? > >> >> > It doesn't disable test caching when using the resulting go tools > >> >> > right? > >> >> > >> >> Right. > >> >> > >> >> Ian > -- 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.
