What happens…
I install a go utility… for example, go install github.com/boyter/scc/v3@latest and it installs fine and scc works fine.
Later, I want to see what go utilities I’ve installed… I know I could do ls $GOPATH/bin but that just lists executable filenames. What about the original full path, version, etc?
Hmm, maybe go list, go list all, go list -m all, … nope! These all seem to intend listing the packages used by the module in the current directory. If I’m in any other directory that isn’t a go project, it says go: go.mod file not found in current directory or any parent directory; see 'go help modules'.
Tell me… why would I need a go list command to list packages used in the current project when cat go.mod tells me everything?
What I think should happen…
Shouldn’t there be some local file that remembers all my prior go installs including the full package name/path and the actual version? And past that, basic commands like go uninstall scc, go update scc, etc to help manage them?
Unsure whether relevant… but I’ve lately been using Go on Windows in Git Bash… but would love to use it across Linux, Windows, macOS, FreeBSD, …
Appreciate any insight wiser Go devs can provide!