you could just make non-modules repos 'look like' a module with one version.
On Wednesday, 24 February 2021 at 03:23:47 UTC simon place wrote: > On Wednesday, 24 February 2021 at 02:26:39 UTC Kurtis Rader wrote: > >> On Tue, Feb 23, 2021 at 5:03 PM 'simon place' via golang-nuts < >> golan...@googlegroups.com> wrote: >> >>> nothing compiles any more! >>> >>> i seem to be being forced to add, to some projects 9 years old >>> (unnecessary) module support, or, add notes to all their docs that they >>> need to be compiled in versions older than 1.16, or have to have an obscure >>> parameter set. >>> >>> there really wasn't a non-breaking way to do this? >>> >>> seems to me this has effectively become part of the language and should >>> be implemented in accordance with the go1 backward compat. guarantee. what >>> difference does it make to a user when things stop compiling like this. >>> On Tuesday, 16 February 2021 at 19:56:37 UTC Alex Rakoczy 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. > > > 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. > > 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. > > > -- 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/ff494405-2bf7-4b16-98af-dc88c6db331cn%40googlegroups.com.
