Modules rarely disappear but when they do it can have a profound impact on a project. I am really paranoid so I sometimes fork a project to a private repo just to have it on hand just in case. I have used git submodules from the git command line as a solution. I still do, but I would not recommend it to anyone. I just do it because i know how and i am too lazy to figure out a better way.
On Wednesday, August 22, 2018 at 5:34:14 PM UTC-5, Conor Hackett wrote: > > Hey Guys, > > So, adding your "vendor" directory to SCM is a contentious topic at best. > > I personally would rather not vendor the dependencies but I do need to > keep the required code in my control and I consider third party repos out > of my control. > > Similar to how maven works (and others I am sure), is there some tooling > that will enable me to cache/store/save third party dependencies on my > local machine/server etc in order to > > a) reduce operational risk of a repo/code disappearing > b) potentially speeding up build time > > This post is more of a sanity check -- I have been searching for such > tooling for a while now and am about to spin up a new project do something > along these lines. > > Thanks in advance. > -- 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. For more options, visit https://groups.google.com/d/optout.
