The go get <https://golang.org/ref/mod#go-get> command ensures that all packages transitively imported by the named package(s) are provided by some module in the module dependency graph. The go mod tidy <https://golang.org/ref/mod#go-mod-tidy> subcommand does the same for all packages transitively imported by your module (not just the dependencies of a specific package).
If go mod tidy is a no-nop for your module, then your dependency graph should not be missing any packages, even if your direct dependencies do not specify explicit requirements for them. On Saturday, May 22, 2021 at 7:06:11 AM UTC-4 peppy...@gmail.com wrote: > Hey guys, > > I am reading upon the module's compatibility with non-module repositories > https://golang.org/ref/mod#non-module-compat and few things are unclear > to me: > > It says that Go will synthesize a go.mod file which only contains a module > directive and the module that depends on such a repository may need to add > indirect dependencies. > > For example, golang.org/x/te...@v0.3.6 <http://golang.org/x/text@v0.3.6> > depends on golang.org/x/tools v0.0.0-20180917221912-90fa682c2a6e which > does not have a go.mod file yet the x/test does not have any indirect > requirements. What is the guarantee that the dependency graph is complete > and the x/text module is not missing any indirect dependencies? > > Kindly, > Peter. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/53b66ae9-9010-4426-a9db-622ddf5aa8f3n%40googlegroups.com.
