3 ms·
> a package management system that will literally yell at you if you try to do something about "huh, maybe it's not great my executables are writeable by my acc
by ricardobeat 4y ago
> a package management system that will literally yell at you if you try to do something about "huh, maybe it's not great my executables are writeable by my account without requiring authorization first"
I assume “asking for authorization” means sudo. That’s a lot more dangerous, since installers can then modify anything on your system, this is the reason homebrew is set up to avoid it.
- DavideNL 4y agoNote that you could just setup/run brew as another Admin useraccount (without using sudo.) So from your main non-Admin account you can then do `su - myadminuser` to then run `brew install vim`, etc.
- ricardobeat 4y agoWon't this alternative admin account also have access to the entire filesystem during installs?
- DavideNL 4y agoThe point is; First of all, the standard (non-admin) user can't directly write to/change brew files. So neither can all the apps you run. You'd first have to change to the admin user with `su - myadminuser`. An admin user does not equal the 'root' user, which has even more permissions. You still have to first `sudo -i` as the admin user, to become root (which is not needed for brew.)