aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Matloob <matloob@golang.org>2021-04-14 22:05:42 -0400
committerMichael Matloob <matloob@golang.org>2021-04-15 16:26:43 +0000
commitcefb4a83192689464140d19cddcef0b3e6f5e882 (patch)
tree2be00366adb06675b89765bcbec0c90b986d508b
parentc52f028076c30c3e767616cbcf094604de6248b4 (diff)
downloadgo-x-proposal-cefb4a83192689464140d19cddcef0b3e6f5e882.tar.xz
design/draft-workspace.md: add idea for pushing buildlist down to workspace mods
Change-Id: I40eea072e34ad8ab91a1361e0208f6c09cc509ea Reviewed-on: https://go-review.googlesource.com/c/proposal/+/310469 Trust: Michael Matloob <matloob@golang.org> Run-TryBot: Michael Matloob <matloob@golang.org> Reviewed-by: Michael Matloob <matloob@golang.org>
-rw-r--r--design/draft-workspace.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/design/draft-workspace.md b/design/draft-workspace.md
index 43a1463..9505e99 100644
--- a/design/draft-workspace.md
+++ b/design/draft-workspace.md
@@ -605,3 +605,13 @@ versioning and releasing modules so that new versions of dependent modules
depend on new versions of the dependency modules. A tool built in the future can
use the current workspace as well as the set of dependencies in the module graph
to automate this work.
+
+### Pushing down dependencies from the build list back to the workspace modules
+
+Even though it's out of scope to update the dependencies between workspace
+modules because that requires a release, it might be useful to make dependency
+versions consistent. One idea could be to push the module versions of dependency
+modules back into the go.mod files of the dependency modules. But this could
+lead to confusion because while the dependency versions will be consistent, the
+dependencies between the workspace modules will still need to be updated
+separately.