Hello guys, Apologies if this has already been discussed but I couldn't find it.
I've just converted a server to use modules. I did it by "go mod init example.com/server-name" in the directory where "package main" is. I then got the latest module for each dependency by doing "go get -u". The resulting dependency list showed me which packages are not yet Go module enabled, and where I have work to do: module example.com/server-name require ( github.com/coreos/bbolt v1.3.0 // indirect github.com/daviddengcn/go-colortext v0.0.0-20180409174941-186a3d44e920 // indirect golang.org/x/sys v0.0.0-20190109145017-48ac38b7c8cb // indirect ) So, I see that I've got some work to do to request that go-colortext converts to a Go module, or at least makes a semver tag. And also, it made me come here to search for how/when to expect golang.org/x/sys to act like a real module. Thanks for any pointers to an explanation of the Go team's plans for golang.org/x packages. -jeff -- 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. For more options, visit https://groups.google.com/d/optout.