| commit | ad6fd61f94f8fdf6926f5dee6e45bdd13add2f9f | [log] [tgz] |
|---|---|---|
| author | Heschi Kreinick <heschi@google.com> | Wed Mar 08 19:46:19 2023 -0500 |
| committer | Gopher Robot <gobot@golang.org> | Thu Mar 09 18:38:19 2023 +0000 |
| tree | 9aed1a9806e3f1f0fddc76e062d2cd67ab560833 | |
| parent | 69aa7acea306dfd277ec48fcc687ef8fa0f2bdb4 [diff] |
zip: fix on Windows Zip paths are slash-delimited, so using filepath with them is incorrect. Change-Id: I5ad1ee90dea97427b9b291b6fbc52e5bdaf0b678 Reviewed-on: https://go-review.googlesource.com/c/mod/+/474815 TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Heschi Kreinick <heschi@google.com> Auto-Submit: Heschi Kreinick <heschi@google.com> Reviewed-by: Bryan Mills <bcmills@google.com>
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.