Updates to Installation Instructions #549
Conversation
| @@ -68,6 +68,7 @@ install_via_binary_download() { | |||
| # Function to install via Homebrew | |||
| install_via_brew() { | |||
| export HOMEBREW_NO_INSTALL_CLEANUP=1 | |||
| export HOMEBREW_NO_ENV_HINTS=1 | |||
There was a problem hiding this comment.
Why are we suggesting the overall homebrew config (HOMEBREW_NO_INSTALL_CLEANUP and HOMEBREW_NO_ENV_HINTS)?
There was a problem hiding this comment.
In our bash install script, we explicitly set the HOMEBREW_NO_INSTALL_CLEANUP and HOMEBREW_NO_ENV_HINTS flags to minimize distractions during the installation process. Although our installer utilizes brew under the hood, the end user is not directly interacting with Homebrew. Therefore, any default hints or messages from Homebrew could be misconstrued as feedback from our installer, which could be misleading. By setting these flags, we streamline the installation experience, ensuring that only pertinent information is displayed. This approach also prevents the Homebrew cleanup messages, which could imply that files are being deleted by our installer, vs brew, which can appear scary. Keep in mind that someone using the installer is probably a novice to begin with, or they would already be using brew natively. Our objective is to keep the installation output as relevant and uncluttered as possible, avoiding any potential confusion for the users.
| For example, in `~/.config/nixpkgs/config.nix` add the following line to the file: | ||
|
|
||
| ```console | ||
| nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable"; |
There was a problem hiding this comment.
I would say that you may need to update your nix config to support the unstable packages channel. I wouldn't make it prescriptive how...that suggestion above means that every package will now be loaded from unstable, which may cause undesired behavior. Some people may prefer stable, then only missing packages from stable are loaded from unstable. And the way you do this is based on how you configure nix (standard, flakes, etc.)
Co-authored-by: Andriy Knysh <aknysh@users.noreply.github.com>
what
why