From bb76e408239489e28f71b60d753853bd0a5c7bf1 Mon Sep 17 00:00:00 2001 From: Haneul Choi Date: Tue, 26 Nov 2024 14:31:04 +0900 Subject: [PATCH] Fixed typo --- doc/README_macOS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/README_macOS.md b/doc/README_macOS.md index 1249a8a3ee..01cb59b127 100644 --- a/doc/README_macOS.md +++ b/doc/README_macOS.md @@ -86,7 +86,7 @@ A short summary of the dispute: It is a dangerous thing to make `/usr/local/bin` writable to the current user, but the alternative - running `sudo make install` for 100 software packages - is also not free of danger. Also installing opam and putting `~/.opam//bin` at the begin of the PATH opens the door to sneaking in adversarial programs in a similar way - with the big difference that opam by default doesn't do this in a fresh shell but only after you called `eval $(opam env)`. -The bottom line is: there is no entirely safe way to install 100s of open source packages. If you trust the community reviews of open source software, you might be better off with MacPorts. If you more trust Murphy's law you might be better of with following Homebrew's path to limit potential damage to `/user/local`. +The bottom line is: there is no entirely safe way to install 100s of open source packages. If you trust the community reviews of open source software, you might be better off with MacPorts. If you more trust Murphy's law you might be better of with following Homebrew's path to limit potential damage to `/usr/local`. ## Homebrew issues and workarounds