Skip to content

Persist PATH to bash_profile when a bash login already has it #7

Description

@VladimirBrejcha

Why this is real

The CLI-only installer persists PATH with one guarded login-profile snippet when it cannot write Homebrew prefix bin. On zsh that file is ~/.zprofile. On bash it currently writes ~/.profile.

A bash login shell that already has ~/.bash_profile will not read ~/.profile. After install, a new bash login may still not resolve simbroker. Independent review of PR #4 recorded this as a residual, not a merge blocker.

This project is Alpha, macOS-only, and needs Xcode. This ticket is only the bash profile choice.

Expected

If the operator uses bash and ~/.bash_profile already exists, the installer writes the guarded snippet there (or documents that --profile is required). zsh behavior stays on ~/.zprofile. --profile still overrides the path so tests never edit a live login rc.

Likely files

  • scripts/install_local.sh / the distribution installer PATH helper
  • installer tests under client/test/ that already isolate --profile

Out of scope

  • Homebrew formula, notarized app, or npm
  • Changing default install prefix

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions