Re:Go 1.8 Release Candidate 1 is released
by mixedCase on Wednesday January 11, 2017 @12:03AM
(#13371885)
>It should not be forced to change how it works because it wants to contain some Go code.
Go is not like Python, the end result is a binary, not interpreted source code. You can simply write a build script that sets a custom GOPATH inside a temporary folder, pulls all dependencies, builds and pops out a binary ready for use; and you can either discard or save your custom GOPATH anywhere for caching purposes.
Re:Go 1.8 Release Candidate 1 is released
by Manishearth on Wednesday January 11, 2017 @12:08AM
(#13371905)
Fair.
Note that this wasn't the only reason we had to fork. Go doesn't (or didn't) provide a way to pin to a dependency, so we would have had to fork anyway, and then rewrite all the paths anyway, so I went the way of using local paths in the fork.
It's fine for a Go project, but this is not a Go project. It should not be forced to change how it works because it wants to contain some Go code.