No Ryan, I didn't switch from zsh to bash as any user - after migration
of users and apps, and my moving from a temporary user to my usual one,
Terminal came up in bash with the usual zsh entreaty, and I left things
that way. This was all a few hours before starting a "clean" install of
MacPorts (from my usual user, using bash).
So the Macports install was from bash, and that session had picked up a
.bash_profile dated 3 years ago which had no less than 3
Macports-generated exports of PATH inserting the /opt/local/... stuff.
And there were three .bash_profile.macports-saved files.
I've looked at the backups of those days and the day following my
install of Macports there was no sign that anything had modified
.bash_profile recently, nor was there a telltale
.bash_profile.macports-saved... for any recent date. So I guess the
MacPort installer post-flite did not detect the need to add the export
of a modified PATH. (But then, maybe that part of the installer has been
modified since I last used it, and won't attempt to add an unnecessary
export PATH if there are suitable ones already there....)
I can't see that it is relevant, but I did have a problem with my second
port install, ImageMagick, which failed at Python311 because I had
forgotten to remove /Applications/Macports - see #68494. I fixed that
and completed the install of ImageMagick before starting on installing
ruby31 (which installed without problems).
Chris F
On 22/10/23 7:12 am, Ryan Schmidt wrote:
On Oct 20, 2023, at 19:44, Chris F wrote:
I have created an appropriate .bash_profile (as described in the Guide) and
everything appears normal now.
You are using bash on Sonoma? The default shell is zsh. The MacPorts installer
is supposed to detect which shell you use and configure the appropriate shell
startup file but maybe it's not identifying your shell properly. Of course, if
you changed your shell from zsh to bash after installing MacPorts that would
explain it.
