On Thursday, 9 January 2020 08:38:56 UTC, T L wrote: > > Yes, when I change the "go 1.13" directive to "go 1.14", it suggests I > need to run 'go mod vendor' to sync. > After the sync, it works. Thanks for the help. > > So if the directive is 1.13, no default "-mod=vendor" compiler flag is > set? And not any message is suggested? > > On Wednesday, January 8, 2020 at 11:51:59 AM UTC-5, Sean Liao wrote: >> >> works for me when tested with gp1.14beta1, are you sure your go.mod has >> the "go 1.14" directive? >> go's tooling currently assumes vendor is a full local copy of all code >> needed to build a module >> with modules the recommended way is to have your patched / unavailable >> module somewhere else >> and point to it with either standard require or a replace >> > > This should work, but it is to tedious, for there are tons of old > dependency packages. > I need to create tons of go.mod files under those package folders and add > tons of replace lines in the main go.mod file. > > If Go SDK 1.14+ also support a special folder vendor_legacy, then things > would become simpler. >
Things would be much, much, simpler if we kill off the vendor folder. It always was a horrible hack. -- 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/4e3cc8b9-1bae-4af2-bff8-01de048b005d%40googlegroups.com.
