MEMetaCosm·May 31, 2013
I don't understand, so explain it to me like I am a child, I am certain I am missing something basic and the developers on the project aren't as dumb as it seems.
Seriously, it seems so goddamn basic. I am going to walk you through step by step how I would add an external library to my Go project.
#1. Switch to the go project directory
#2. Fork for the new feature (adding_mux)
#3. Run go get github.com/gorilla/mux
#4. Add import "github.com/gorilla/mux" to my code, use mux for great goodness
#5. Commit my code (this is commit of ./src which includes two things, the addition of the new github.com/gorilla/mux/* and my code using that new library)
#6. Merge
#7. Push
At this point, the commit that was just checked in doesn't need a change to its import path, will never break and will work as it was committed FOREVER. git clone FOO; go build
Read the rest
BAR -- victory!
If at some point I want to update that library (new cool feature!)
#1. Switch to go project directory
#2. Fork for updating library (update_mux)
#3. Run go get -u github.com/gorilla/mux
#4. Write code using new awesome features
#5. Commit my code (again, "my code" in this case is both the update to the mux library, and my new usage of it, again committed together for great goodness!)
#6. Merge
#7. Push!
I feel like one of us is bat shit insane, and at this point, I am just hoping it isn't me.
EDIT: Another cool side effect of this is you end up with localized hermetic copies of your code with references for posterity to where you got it, bonus points!
EDIT 2: For reference, there are various forks of the source he "released" (abandoned? Sold for 28k? whatever) ... I think you can start looking at the github network from here: https://github.com/runningwild/haunts