You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2022. It is now read-only.
Using the default GOPATH (not explicitly setting it) results in an error saying that git is not in PATH (it is):
> retool do
retool: syncing
retool: downloading github.com/vektra/mockery/cmd/mockery
retool: fatal err: execution error on "go get -d github.com/vektra/mockery/cmd/mockery": go: missing Git command. See https://golang.org/s/gogetcmd
package github.com/vektra/mockery/cmd/mockery: exec: "git": executable file not found in $PATH
: failed to 'go get' tool: exit status 1
It would be nice if retool worked with the default GOPATH or at least warned if GOPATH isn't set.
> retool version
retool v1.0%
The text was updated successfully, but these errors were encountered:
retool really isn't prepared for the brave new world of Go modules and GOPATH-less workflows. I'm not sure we can remedy this issue, since it goes quite deep into how the tool works.
It might be time to instead start thinking about how a new retool2 (re2l?) might work, centered around modules. Or, even better, how we might use Go modules to replace any need for retool at all.
Here's a blog post I wrote up explaining how you can avoid needing retool (for many of the basic cases) in the modules world - https://npf.io/2019/05/retooling-retool/
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using the default
GOPATH
(not explicitly setting it) results in an error saying thatgit
is not inPATH
(it is):It would be nice if retool worked with the default GOPATH or at least warned if GOPATH isn't set.
The text was updated successfully, but these errors were encountered: