From: Jay Conrod <jayconrod@google.com>
Date: Tue, 28 Apr 2020 15:58:33 +0000 (-0400)
Subject: doc/go1.15: add notes for GOMODCACHE, modcacheunzipinplace
X-Git-Tag: go1.15beta1~329
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=495a287f0bd9d3294b9ef7533dc8165527b29c0e;p=gostls13.git

doc/go1.15: add notes for GOMODCACHE, modcacheunzipinplace

For #36568
For #34527

Change-Id: Ieea4b4a7644e9c957f48d08d2e172e39b571502f
Reviewed-on: https://go-review.googlesource.com/c/go/+/230537
Reviewed-by: Michael Matloob <matloob@golang.org>
Reviewed-by: Bryan C. Mills <bcmills@google.com>
---

diff --git a/doc/go1.15.html b/doc/go1.15.html
index 9d10092ffa..97479d1537 100644
--- a/doc/go1.15.html
+++ b/doc/go1.15.html
@@ -78,6 +78,26 @@ TODO
   directory of each individual test).
 </p>
 
+<h4 id="module-cache">Module cache</h4>
+
+<p><!-- https://golang.org/cl/219538 -->
+  The location of the module cache may now be set with
+  the <code>GOMODCACHE</code> environment variable. The default value of
+  <code>GOMODCACHE</code> is <code>GOPATH[0]/pkg/mod</code>, the location of the
+  module cache before this change.
+</p>
+
+<p><!-- https://golang.org/cl/221157 -->
+  A workaround is now available for Windows "Access is denied" errors in
+  <code>go</code> commands that access the module cache, caused by external
+  programs concurrently scanning the file system (see
+  <a href="https://golang.org/issue/36568">issue #36568</a>). The workaround is
+  not enabled by default because it is not safe to use when Go versions lower
+  than 1.14.2 and 1.13.10 are running concurrently with the same module cache.
+  It can be enabled by explictly setting the environment variable
+  <code>GODEBUG=modcacheunzipinplace=1</code>.
+</p>
+
 <h2 id="runtime">Runtime</h2>
 
 <p>