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
Alias tip: gog github.com/evcc-io/evcc@master
go: downloading github.com/evcc-io/evcc v0.0.0-20211008101320-ad0211e9c660
go: downloading github.com/pascaldekloe/name v1.0.1
go get: installing executables with 'go get' in module mode is deprecated.
To adjust and download dependencies of the current module, use 'go get -d'.
To install using requirements of the current module, use 'go install'.
To install ignoring the current module, use 'go install' with a version,
like 'go install example.com/cmd@latest'.
For more information, see https://golang.org/doc/go-get-install-deprecation
or run 'go help get' or 'go help install'.
go get: added github.com/evcc-io/evcc v0.0.0-20211008101320-ad0211e9c660
go get: upgraded github.com/magiconair/properties v1.8.4 => v1.8.5
go get: upgraded github.com/pelletier/go-toml v1.8.1 => v1.9.3
go get: upgraded github.com/spf13/afero v1.4.1 => v1.6.0
go get: upgraded github.com/spf13/cobra v1.1.1 => v1.2.1
go get: upgraded github.com/spf13/viper v1.7.1 => v1.8.1
go get: upgraded github.com/thoas/go-funk v0.7.0 => v0.9.0
go get: upgraded golang.org/x/net v0.0.0-20201010224723-4f7140c49acb => v0.0.0-20210805182204-aaa1db679c0d
go get: upgraded golang.org/x/text v0.3.3 => v0.3.6
As modules user this is highly confusing for me as I did not intent to install executables, much less as part of a dependency.
As module author I would wonder what to do to make my consumers not subject to this hint?
The text was updated successfully, but these errors were encountered:
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
@seankhliao I feel this is the right place. The issue here is that updating a module for go.mod triggers an (invalid) install warning. This happens for modules that provide both packages and binaries apparently.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Require a module:
What did you expect to see?
No error
What did you see instead?
As modules user this is highly confusing for me as I did not intent to install executables, much less as part of a dependency.
As module author I would wonder what to do to make my consumers not subject to this hint?
The text was updated successfully, but these errors were encountered: