Orkuncakilkaya
bfa763a55b
~/.bashrc was only appended to when it already existed, so on an account without one — a fresh container, a minimal image — `bash -i`, which is what most Linux terminal emulators start, did not see the toolchain even though every other shell did. .bashrc is now created when missing. Unlike .bash_profile, whose existence stops bash reading ~/.profile, a .bashrc that only sources the env file changes nothing else about how bash starts. Verified across zsh -i, zsh -c, bash -l, bash -i, sh -l and dash -l on a staged HOME: all six resolve ludic, a second run writes nothing, and .bash_profile is still never created. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
7 lines
399 B
Markdown
7 lines
399 B
Markdown
bump: patch
|
|
type: fix
|
|
The installer also covers a non-login interactive `bash` — the shell most Linux
|
|
terminal emulators start, which reads only `~/.bashrc`. That file is now created
|
|
when it is missing (its presence changes nothing else about how bash starts),
|
|
while `~/.bash_profile` is still only appended to when it already exists, since
|
|
creating that one would stop bash reading `~/.profile`.
|