The end result should be a Homebrew installation that does not need the use of sudo ever again. IMPORTANT: do not use sudo unless absolutely necessary as described below. NOTE: This answer assumes that the macOS user is setup as an administrator. lower security risk if Homebrew itself or Homebrew packages do not compel the user to run some things as root.easier to manage existing Homebrew packages.Motivation for avoiding the need for the user to use sudo after installation: Installation into subdirectory of my home directory is not ideal since Homebrew manages a combination of locally built packages and system-wide packages.Manual installation gives me the best control over the process of installation and management of Homebrew.Motivation for manual installation info /usr/local subdirectory: How should I manually install Homebrew into a /usr/local subdirectory? (Standard Homebrew install scripts seem to use sudo but only when absolutely necessary, while the standard result is that there is no need to use sudo to install new packages, update, etc.) I understand that I may need to use sudo to install Homebrew itself but hope I do not need to continue using sudo to install new packages, update, etc. Directions in this question along with its accepted answer are a little better but also do not work without using sudo. Manual installation directions in are very brief and unsatisfactory, resulting in some errors if I try it in a subdirectory of /usr/local without using sudo.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |