Related Issues and Documentation

• cmd/go: clean cache periodically #22642 (closed)
• cmd/go: make cache keys for libraries in GOROOT insensitive to `-trimpath` #57346

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

CC @matloob

I don't know if this justifies its own environment variable (that would show up in go env, etc.) but maybe we can make it an undocumented # godebug setting?

@matloob If you mean something we can set via the GODEBUG environment variable, that would also be acceptable. We just need something we can easily configure globally in the base image.

Yes. That is what I mean.

I think a possible workaround for this would be to update trim.txt with a time value far in the future so any go command that looks at it will not bother trying to trim.

Something like that could be done at container image build time.

Is that sufficient?

I don't think trim.txt and its usage by the go command are documented / promised but it's something.

I don't think the trim.txt workaround works, because the go command will ignore trim.txt if the timestamp is more than one hour in the future.

Maybe the trim.txt mtime in more than one hour in the future could be removed.

Or changed to if it is more than a year in the future then it is intentionally in the future, if that isn't too implicit.

trim.txt is supposed to be an internal implementation detail of the go command. I don't think we'd want to change its behavior to support a workaround.