cmd/go: module 0400 permissions are annoying #28137
Labels
FrozenDueToAge
modules
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
I use
go build
as part of larger build systems, such as gradle, xcodeproj, and cmake. In these cases, I'm generally putting various artifacts into a predefined build directory that I don't control. I'm only allowed to write files there, and so that's where they go. So, for example, downloaded go modules go into this intermediate/temporary build structure.When it's time for the parent build system to clean up its various temporary or intermediate directories, it of course chokes when hitting the 0400 directories. It's not very pleasant or clean (in error paths) to have to unconditionally run
chmod -fR +w .../pkg/mod
everytime that eithergo build
orgo get
is called.Rather, would you consider adding an option to these tools or perhaps even an environment variable that doesn't chmod anything and just uses the ordinary boring file permissions?
The text was updated successfully, but these errors were encountered: