-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: support reusing GOMODCACHE system wide #40895
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
Comments
I'm not sure, what's problem here -- you can create common directory like |
Sorry i should give an example:
The directories are created without writing permission to group and others and the owner is the first user who go get something. |
You need to set |
Yes for the group, but there is still no write permission on the group. |
Try to set acl for this directory and add group to it: |
No, i believe go get explicitly set group without write. |
That's strange, that works for me. |
Here's how i tried to reproduce your problem, feel free to update my steps if i do something wrong: Create group:
Create user and add him to group:
Create common directory and assign needed permissions:
Login as new user and download module:
And that works just fine. |
The first user who |
Ah, i see. Indeed, i get this error from first user. |
I'm not sure if this is meant to be supported and whether it's already possible (if done in a certain way). |
What is your The |
Also /cc @katiehockman FYI since this topic may be relevant to fuzzing work. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
What version of Go are you using (
go version
)?Given the new possibility to set
GOMODCACHE
i would like to make it system wide as i have only trusted users on my server it would let me gain disk space and download speed if the directory could be the same for all users.But the perms prevent it, for security reason i believe.
Is there a workaround ? Or could it be a proposal for a such a feature ?
I'm aware of running a local proxy but it's overkill for me and will duplicate again the cache.
The text was updated successfully, but these errors were encountered: