New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eval "$(/usr/bin/env brew shellenv)"
causes duplicate path
, man path
, info path
#17142
Comments
This is not going to happen. It will break the setup for everyone who relies on this.
We intentionally are willing to accept duplication here (it does no harm) to ensure that the sequencing is correct (so that |
I think good design should be able to separate private and public parts. brew_env() {
set_brew_private_env
set_public_env
} Equal: set_brew_private_env && set_public_env This makes it easier to combine other programs. And can be called multiple times safely. set_brew_private_env && set_brew_public_env
set_brew_public_env && more_process_a
set_brew_private_env && more_process_b
We got a clean path handling. PATH = user_path:brew_path:sys_path OR clean_path_handle() {
addToPath user_path
addToPath brew_path
addToPath sys_path
} |
I think the design is good already. Regardless: we cannot make backwards incompatible changes, like you're proposing. |
I don't think there is a way to make the changes you propose without either a) breaking For your use case, I suggest sticking with the code you've already written to add Homebrew to However, if in fact there is a simple way to update |
brew doctor
outputVerification
brew doctor
output" above saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
twice and am still able to reproduce my issue.brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.brew config
outputWhat were you trying to do (and why)?
What happened (include all command output)?
at the end, found the
What did you expect to happen?
suggestion
Delete
PATH
,MANPATH
, andINFOPATH
in the defaultshellenv.sh
.brew
should only handle its own private variables, such asHOMEBREW_PREFIX
,This way we can use external functions to handle these environment variables.
For example, avoid duplication or sequencing.
Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: