-
Notifications
You must be signed in to change notification settings - Fork 17.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd/go: do not report cached libraries as stale in module mode #46911
Labels
Milestone
Comments
bcmills
added
modules
NeedsFix
The path to resolution is known, but the work has not been done.
labels
Jun 24, 2021
This appears to have been fixed incidentally by (or in association with) #47257.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
In module mode, non-
main
packages have no install path: built packages are stored only in the build cache. In module mode,go install
for a non-main package only ensures that the build cache is up to date; it does not install the library elsewhere.According to https://tip.golang.org/cmd/go/#hdr-List_packages_or_modules, the
Stale
field means:According to that interpretation, we should not report a library as
Stale
in module mode if it is already up to date in the build cache. Today, we always report libraries as stale:This came to my attention via https://stackoverflow.com/q/64462190.
CC @jayconrod @matloob
The text was updated successfully, but these errors were encountered: