Clarifying permissions needed for symlinks
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 3.3k
- Forks
- 446
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 1
Description
It's not about "running as administrator" in the same way that not being a member of a unix group isn't about "running as root".
Windows has a specific local security policy about creating symlinks.
Instead of deploying nuclear weapons to kill a flea, run the local security policy applet and add your account name to the access control list for the creating symlinks policy, e.g. LOCALMACHINE\user. Then things like git and other programs that try to make symlinks will work correctly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the relevant MSYS2 homepage guidance about symlink creation and compare it with the linked Windows local security policy documentation. Clarify that administrator privileges differ from the Create symbolic links policy, include the account-ACL guidance described here, and consider the work done when the instructions no longer conflate these permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation, operating-systems
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100