commit | 5f2f164f8ff796d1d1629130855616db9cf40ca9 | [log] [tgz] |
---|---|---|
author | Bryan C. Mills <bcmills@google.com> | Mon Nov 22 11:11:59 2021 -0500 |
committer | Bryan C. Mills <bcmills@google.com> | Mon Nov 22 17:40:44 2021 +0000 |
tree | 6d58b56dced9c8ce71876fe179ecec22aeabe843 | |
parent | 3a5865c02020dc883ab0b88fe3185b05e57a84ea [diff] |
zip: skip tests that run 'git init' and 'git config' on plan9 The plan9 'git' command empirically doesn't support one or more of the commands we need to run to create a test repository (https://build.golang.org/log/627dacbfca9e0dfe6b84cf597411e63898b68ec8). Rather than trying to coax it into working with a non-standard git command, just skip the tests that need it. Change-Id: Id20fd21d4a4b9d2d683ba7bdada5efbc17ac08bb Reviewed-on: https://go-review.googlesource.com/c/mod/+/366035 Trust: Bryan C. Mills <bcmills@google.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Bryan C. Mills <bcmills@google.com> TryBot-Result: Go Bot <gobot@golang.org>
This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.
It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages.
The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.