aboutsummaryrefslogtreecommitdiffstats
path: root/docs/Building-Against-Non-Homebrew-Dependencies.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/Building-Against-Non-Homebrew-Dependencies.md')
-rw-r--r--docs/Building-Against-Non-Homebrew-Dependencies.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Building-Against-Non-Homebrew-Dependencies.md b/docs/Building-Against-Non-Homebrew-Dependencies.md
index 0c8ad9802..4e85757a1 100644
--- a/docs/Building-Against-Non-Homebrew-Dependencies.md
+++ b/docs/Building-Against-Non-Homebrew-Dependencies.md
@@ -8,4 +8,4 @@ As Homebrew became primarily a binary package manager, most users were fulfillin
## Today
-If you wish to build against custom non-Homebrew dependencies that are provided by Homebrew (e.g. a non-Homebrew, non-macOS `ruby`) then you must [create and maintain your own tap](How-to-Create-and-Maintain-a-Tap) as these formulae will not be accepted in Homebrew/homebrew-core. Once you have done that you can specify `env :std` in the formula which will allow a e.g. `which ruby` to access your existing `PATH` variable and allow compilation to link against this Ruby.
+If you wish to build against custom non-Homebrew dependencies that are provided by Homebrew (e.g. a non-Homebrew, non-macOS `ruby`) then you must [create and maintain your own tap](How-to-Create-and-Maintain-a-Tap.md) as these formulae will not be accepted in Homebrew/homebrew-core. Once you have done that you can specify `env :std` in the formula which will allow a e.g. `which ruby` to access your existing `PATH` variable and allow compilation to link against this Ruby.