On Sun, Mar 3, 2024 at 1:25 PM Jeffery Carr <basilarc...@gmail.com> wrote: > > Has this been deprecated or maybe it is broken in debian sid, but: > > bash$ GO111MODULE=off go get -v go.wit.com/apps/test > go: modules disabled by GO111MODULE=off; see 'go help modules' > basj$ go version > go version go1.22.0 linux/amd64 > > this doesn't work anymore. Also, 'go help modules' is less than helpful. > > Is there some other way to download the actual sourcecode into > ~/go/src/mything/ anymore? >
I think you may be seeing a bad error message. `go get go.wit.com/apps/test` doesn't work whether you are in module mode or not. With Go 1.21 I get > GO111MODULE=off ~/go1.21/bin/go get -v go.wit.com/apps/test package go.wit.com/apps/test: unrecognized import path "go.wit.com/apps/test": parse https://go.wit.com/apps/test?go-get=1: no go-import meta tags () I filed https://go.dev/issue/66080 for the odd difference in error messages. > This functionality was _PERFECT_ in my experience. I can't even imagine why > it would be deprecated. How in the world are you all developing complicated > software using GO without this working? Is this why everyone has gazillions > of internal/ packages and massive git repos? Most people simply use modules with no internal packages and with git repos that contain only their own code. That's kind of the point of modules, in fact. When I want to see the source code of an imported module, I build the package using `go build`, and then look in $GOPATH/pkg/mod. Ian -- 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/CAOyqgcU9OvSsdA8m6qXwcwuF8a-B4MxKVhaeHGPvVsM3ceAkvQ%40mail.gmail.com.
