As done in the Makefile in ad2f4ab. Theoretically this problem
shouldn't happen here, as RUNUSR is always 'macports', but there have
been occasional reports of strange things happening to the macports
user or other accounts getting renamed to 'macports' (with Migration
Assistant being one of the likely culprits), so it's probably best not
to mess with the user if it doesn't look right.
This brings us back to state of the art Tcl. Note that the only
adaptions done together with this commit are in vendor/Makefile.in. The
code in these directories itself is unpatched. Patches to fix various
problems will be re-applied in separate commits for better visibility.
Additionally, this commit will not build: Tcl 8.6 introduces a try
statement that's incompatible with the re-implementation is currently
shipping, and some changes in configure scripts require adaptions in our
buildsystem. Those will also be done in a separate commit.
Apple switched the default Shell on macOS Catalina to zsh, so our
installer now no longer correctly configures $PATH in the default
configuration.
Add support for zsh to fix this. Write the PATH configuration to
~/.zshenv, which seems to be the default location for this kind of
configuration data on zsh.
Use "Mac OS X" for 10.0-10.7, "OS X" for 10.8-10.11, "macOS" for 10.12+.
In the configure script check, direct the user to the Mac App Store to
update the OS on 10.8 and later, instead of Software Update.
You can't tell whether configure.cxx_stdlib was overridden by a port if
it was not recorded at install time. This creates a problem for users
upgrading from versions of MacPorts that did not record it: rev-upgrade
will think that ports that do override it are broken, because they do
not follow the global cxx_stdlib setting.
Therefore, to ease the transition, keep a list of ports that are known
to override the setting, and when upgrading base, set the flag in the
registry for those ports if it is currently null.
Closes: https://trac.macports.org/ticket/56326