gobin
gobin copied to clipboard
myitcv
gobin is an experimental, module-aware command to install/run main packages.
This way the version information will be compiled into the binary and, when https://go-review.googlesource.com/c/go/+/144220 lands, we will be able to use that for `gobin version`.
At the moment the binaries themselves are uploaded as release assets. However, this means when downloaded they don't have execute permissions. So storing in an archive probably makes sense. But...
If the user uses `gobin` to install a main package that is _not_ part of a module, then by definition the dependencies of that package are "unstable" (probably a better...
It already appears to be a common situation (well, for me at least 👍) to have some tools installed as dependencies of a module in some situations, with a global...
Currently (well, once #32 is merged to be precise), `gobin foo.com/bar@$revision` will be the only form of `gobin` that always hit the network. We can do better here by caching...
Otherwise we are a bit blind on what's working/not working.
Per https://github.com/myitcv/gobin/pull/19#discussion_r228750595
Otherwise disks will start to fill... Ideas include: * use the existence of a module within the module download cache as an indicator of when to evict
Would effectively be the equivalent of: ``` GOPROXY=file://$GOPATH/pkg/mod/cache/download go list -m -versions $module ``` i.e. would be local only. With the `-g` flag it would be the equivalent of: ```...