- #Install homebrew install#
- #Install homebrew update#
- #Install homebrew manual#
- #Install homebrew password#
Outdated solution from 2018 no longer tested or updated:įirst make a temporary directory within /usr/local using sudo (enter password if requested): sudo mkdir /usr/local/brewtmp1Ĭheck the results of ls -l /usr/local: total 0ĭrwxr-xr-x 2 root wheel 64 Jul 2 16:16 brewtmp1įix the user and group ownership of the temporary directory: sudo chown $USER:admin brewtmp1Ĭheck the results of ls -l /usr/local again: total 0ĭrwxr-xr-x 2 brodybits admin 64 Jul 2 16:16 brewtmp1 See further below for some optional followup steps.
#Install homebrew install#
Try installing a simple formula such as autoconf: brew install autoconfĪutoconf -version should now show that it is installed. Homebrew/homebrew-core (git revision 61cc59c956 last commit ) It will likely output some warning messages about the non-standard Homebrew prefix but this should be an issue for most packages.īrew -version after brew doctor should show homebrew-core included, for example: Homebrew 3.1.7-36-g7c68b17
#Install homebrew update#
Then run brew update to include homebrew-core and run brew doctor to verify proper installation. It is recommended to check that which brew shows it in the right place, /usr/local/opt/brew/bin/brew.Īt this point, brew -version should show some information (with no homebrew-core installed at this point), for example: Homebrew 3.1.7-36-g7c68b17 Restart the shell, start a new shell, or source the profile file. Here is an example: export PATH=/usr/local/opt/brew/bin:$PATH Update the desired profile file ( $HOME/.zprofile or $HOME/.zshenv in case of zsh, for example) to add the new Homebrew bin subdirectory to the PATH environment variable. It is also optional to move the new brew subdirectory up to the /usr/local level ( sudo may be needed just once more for this). Optional: It is possible to rename the newly installed brew subdirectory, if so desired. Now use Git to clone Homebrew/brew from GitHub into the new subdirectory, for example: cd /usr/local/opt ĭrwxr-xr-x 4 root wheel 128 May 13 17:13 bakĭrwxr-xr-x 2 brodybits staff 64 May 13 17:03 opt Ls -al /usr/local should now show the new subdirectory, for example: total 0ĭrwxr-xr-x 5 root wheel 160 May 13 17:13 11 root wheel 352. Use sudo to make a subdirectory such as opt that Homebrew can be installed under, and use your own login password if needed: sudo mkdir /usr/local/optĪnd sudo sudo only once more to take ownership of the subdirectory under the staff group, for example: sudo chown brodybits:staff /usr/local/optĪt this point sudo should no longer be needed for installing or using Homebrew. 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.
#Install homebrew manual#
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 kommentar(er)
