admin/brew
1
0
Fork 0
Code Issues Packages Projects Releases 6 Wiki Activity

Revise docs/FAQ.md

Browse Source 
Co-authored-by: Mike McQuaid <mike@mikemcquaid.com>
This commit is contained in:
Shaun Jackman 2020-11-26 10:17:14 -08:00 committed by GitHub
parent 85a7947956
commit 8846779d83
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/FAQ.md
View File

@ -104,7 +104,7 @@ It is not always straightforward to tell `gem` to look in non-standard directori
## Why does Homebrew on Linux recommend that I install to `/home/linuxbrew/.linuxbrew`?
Homebrew's pre-built binary packages, called bottles, of most software can only be used if you install in `/home/linuxbrew/.linuxbrew`, otherwise they have to be built from source. Building from source takes a long time, is prone to fail, and is not supported. Install Homebrew on Linux in `/home/linuxbrew/.linuxbrew/` if possible so that you can use our pre-built binary packages. If you do not yourself have admin privileges, consider asking your admin staff to create a `linuxbrew` role account for you with home directory `/home/linuxbrew`. The prefix `/home/linuxbrew/.linuxbrew` was chosen so that users without admin access can ask an admin to create a `linuxbrew` role account and still benefit from precompiled binaries.
The prefix `/home/linuxbrew/.linuxbrew` was chosen so that users without admin access can ask an admin to create a `linuxbrew` role account and still benefit from precompiled binaries. If you do not yourself have admin privileges, consider asking your admin staff to create a `linuxbrew` role account for you with home directory `/home/linuxbrew`.
+ https://docs.brew.sh/FAQ.html#why-do-you-compile-everything
+ https://docs.brew.sh/Installation.html#alternative-installs