`eval "$(/usr/bin/env brew shellenv)"` causes duplicate `path`, `man path`, `info path` about brew HOT 4 CLOSED

brew shellenv is designed to work for 95% of our users. In its current form, it does that.

I don't think there is a way to make the changes you propose without either a) breaking shellenv for a significant proportion of the 95%, or b) making the code significantly more complex than it's worth making shellenv more useful to another 2-3% of users.

For your use case, I suggest sticking with the code you've already written to add Homebrew to PATH, MANPATH, etc instead of using shellenv.

However, if in fact there is a simple way to update shellenv without breaking it for any existing users, please open a pull request instead.

from brew.

Delete PATH, MANPATH, and INFOPATH in the default shellenv.sh.

brew should only handle its own private variables, such as HOMEBREW_PREFIX,

This is not going to happen. It will break the setup for everyone who relies on this.

For example, avoid duplication or sequencing.

We intentionally are willing to accept duplication here (it does no harm) to ensure that the sequencing is correct (so that bin/brew and brew installed bins and sbins are at the front of the various *PATH.

from brew.

This is not going to happen. It will break the setup for everyone who relies on this.

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 intentionally are willing to accept duplication here (it does no harm) to ensure that the sequencing is correct (so that bin/brew and brew installed bins and sbins are at the front of the various *PATH.

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
}

from brew.

I think good design should be able to separate private and public parts.

I think the design is good already. Regardless: we cannot make backwards incompatible changes, like you're proposing.

from brew.