i had a similar experience where i ended up pull-requesting the addition of mod&sum into a dependency. fair enough for actively maintained packages or packages you've contributed to before but could be problematic otherwise. (insert any linux/bsd talk about contributing changes upstream here)
it is not really reasonable to expect everyone to indefinitely maintain everything they put out there. this is a breaking change for old code in practice...even if it's more the toolchain than the source and consistent with the compatibility promise when carefully read. to be clear: i'm not criticising the change and like that i need to take action(s) now as opposed to an unknown time later. so a suggestion: a tool to scan for not-updated projects that does the mod&tidy, tests it, and sends a pull request. logistically that's a lot for an individual but should be workable for the go team (i am guessing). this would also have the advantage of finding truly orphaned projects -- if a maintainer doesn't reply in a week/month/whatever to an obviously-automatic-and-official request to fix something the package really should be forked. can't cover everything but whatever is on pkg.go.dev is a kind of all you can expect. and if anybody from the hosting/ci providers is here: providing free credits for this would be a nice way to show support for the ecosystem. or maybe this is just going to cause noise for a week and then every actively used package will be sorted or forked-and-then-sorted. On Wed, Feb 24, 2021 at 11:34 AM Kurtis Rader <kra...@skepticism.us> wrote: > On Tue, Feb 23, 2021 at 7:24 PM 'simon place' via golang-nuts < > golang-nuts@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/CABx2%3DD8gGZOwnY%3D_gcs%2BayGeZgDjpCM%3DuHTe6HSuw9n945Qvow%40mail.gmail.com > <https://groups.google.com/d/msgid/golang-nuts/CABx2%3DD8gGZOwnY%3D_gcs%2BayGeZgDjpCM%3DuHTe6HSuw9n945Qvow%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CABZtUk6npWS3BoZWQ7%3DWdP5uzbCWtormsBR_7Rf47_n3Xn6A0w%40mail.gmail.com.
