Go modules were introduced back in 2018, so we have had a good few years to migrate. In most cases migrating simply means running go mod init, and commiting the go.mod and go.sum files. Migrating does cause a small amount of pain. But it will improve your life as a developer.
The existence of both GOPATH and Module modes has been a source of confusion in the Go world. So obliterating GOPATH, and its bizarre stipulations about how you need to organise your home directory is welcome, and long overdue. On Wednesday, 24 February 2021 at 03:34:32 UTC Kurtis Rader wrote: > On Tue, Feb 23, 2021 at 7:24 PM 'simon place' via golang-nuts < > golan...@googlegroups.com> wrote: > >> >> Insufficient information. What command did you run? What was the output? >>> Note that module mode is now the default with Go 1.16. You can get the Go >>> 1.15 behavior by exporting GO111MODULE=auto. However, that will just punt >>> the problem down the road. At some point in the future GOPATH mode will no >>> longer be supported. You're probably better off biting the bullet now and >>> switching to Go modules. >>> >> >> thanks, but i did read the tread. >> > > What did you read? The thread that you originally replied to simply > announced a new Go release. Something that happens roughly every six months > and always has the potential of disrupting existing users of the Go > toolchain. > > >> > Insufficient information. What command did you run? What was the output >> >> you seem to not get it, i provide the go SOURCE in a repo, who ever wants >> to use it package will try to compile and now with 1.16 all will fail, >> without me retrospectively changing them all. >> > > If you are publishing your Go project(s) you should be using modules. > Regardless, you still haven't provided any information that would allow the > Go community to help you. Provide a link to your repo and/or describe the > structure of your repo and how you expect it to be used. > > i guess i won't do anything, shame, just way too much work, i'll just have >> to rely on people knowing they need <1.16, (or the parameter) at least this >> will be so common a problem it will probably be well enough known. >> >> things like this, and i do this, if a new package doesn't work first >> time, i walk away. >> >> but then, thinking about it, what happens when you have a project with a >> mixture of moduled and non-moduled imports, very hard to get working? so if >> i don't put in the, completely unnecessary, work i may as well just scrap >> the lot. >> > > I get the sense you're not really asking for help; you're just interested > in expressing unhappiness that the world has changed. > > -- > Kurtis Rader > Caretaker of the exceptional canines Junior and Hank > -- 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/e51219b0-4cdb-48f1-be0d-beb95b6878d7n%40googlegroups.com.
