Timeline for answer to How to install a gem or update RubyGems if it fails with a permissions error by thebiggestlebowski
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 10, 2019 at 0:49 | comment | added | thebiggestlebowski | The gem is installed by default to this location. It was unusable because it was mistakenly installed as root (sudo) instead of my normal user. The outcome of what I did was the same as if I'd installed as $USER in the first place. I don't see the harm. Most of the other answers here suggest the same outcome/solution, but different ways to achieve it. I still don't see the problem. Are you saying gems should not be installed under /Library? | |
| May 9, 2019 at 4:34 | comment | added | Raptor | The path is for system. Further updates of macOS may break. | |
| May 9, 2019 at 4:26 | comment | added | thebiggestlebowski | @Raptor I'm modifying permissions on a subfolder, not "/Library". In my case, I mistakenly installed the gems as root, so I wanted to undo that. There are no negative consequences that I can think of theoretically nor have there been any that I've observed. I'm curious - why do you think this is a bad idea? | |
| Apr 29, 2019 at 3:14 | comment | added | Raptor |
Big NO! never change the permission on /Library folder, the system may break in future updates. (sorry for late reply)
|
|
| Sep 30, 2016 at 20:15 | history | answered | thebiggestlebowski | CC BY-SA 3.0 |