4 ms·
Today I'm working on a project A which depends on B, which depends on C, which depends on D. In order to fix a bug in D, it seems that I need to make a personal
by Shish2k 12y ago
Today I'm working on a project A which depends on B, which depends on C, which depends on D. In order to fix a bug in D, it seems that I need to make a personal copy of B and C in order to rewrite their import statements, and then I'm responsible for keeping all those packages up to date :/
(Unless I'm missing something, I am pretty new to Go. I really hope I am missing something...)
- NateDad 12y agoSo, assuming that upstream will accept your changes, the easiest thing to do is create a branch of D in the same on-disk location as the original code (so, $GOPATH/src/github.com/D-team/D for example). You then make your modifications there... the import statements still work because they still refer to the same place on disk. Read this: http://blog.natefinch.com/2014/03/go-and-github.html http://blog.natefinch.com/2014/03/go-and-github.html