I mean "to use the pakckages under vendor folder and from module cache at the same time".
I have one question, is it better to add a "go mod cache-locally" command to save the dependency modules in a "module-cache" folder in the current project, so that "go build -use-local-module-cache" can use the packages in the old "vendor" folder and the "module-cache" folder? On Tuesday, September 10, 2019 at 8:59:28 AM UTC-4, T L wrote: > > I maintain an private old Go project, which depends many many old packages. > Before the module mode, I put all these dependency packages under the > vendor folder. > In the developing process, from time to time, I modified some of > dependency packages. > > Meanwhile, I plan to migrate the project to modules mode and need to > import some new module packages. > I found I encountered an embarrassing situation. > If I delete the vendor folder and run "go mod vendor" in modules mode to > rebuild the vendor, > the command will fail. One reason is some dependency packages disappeared. > The other reason is many packages are updated and broke capabilities. > And I don't want the new download to overwrite my local modifications for > some dependency packages. > > So, is there a way to let me continue use the these old dependency > packages and use some new modules based packages? > > -- 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/a19c1fbf-fca8-4171-b830-01a226577f36%40googlegroups.com.
