3 ms·
>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 so
by mixedCase 10y ago
>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.
- Manishearth 10y agoFair. 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.
- mixedCase 10y agoYou can probably consider unforking now that the vendor directory is a thing. I'm sure it'd be easier than rebasing on every update.