diff --git a/bin/all-run.sh b/bin/all-run.sh index 6116e47b8..a4f5f8299 100755 --- a/bin/all-run.sh +++ b/bin/all-run.sh @@ -64,8 +64,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -73,16 +73,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -90,12 +92,13 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi + # setup bash file matching # # We must declare arrays with -ag or -Ag, and we need loops to "export" modified variables. diff --git a/bin/all-years.sh b/bin/all-years.sh index c6b89ba98..824ec9f2e 100755 --- a/bin/all-years.sh +++ b/bin/all-years.sh @@ -63,8 +63,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -72,16 +72,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -89,9 +91,9 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/chk-entry.sh b/bin/chk-entry.sh index 8224b5fc1..65e25c3e4 100755 --- a/bin/chk-entry.sh +++ b/bin/chk-entry.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,16 +44,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -61,9 +63,9 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/gen-authors.sh b/bin/gen-authors.sh index 8a092b893..3b311f04c 100755 --- a/bin/gen-authors.sh +++ b/bin/gen-authors.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,16 +44,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -61,9 +63,9 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/gen-location.sh b/bin/gen-location.sh index 88c10b54e..f9123fdd9 100755 --- a/bin/gen-location.sh +++ b/bin/gen-location.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,16 +44,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -61,12 +63,13 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi + # setup bash file matching # # We must declare arrays with -ag or -Ag, and we need loops to "export" modified variables. diff --git a/bin/gen-other-html.sh b/bin/gen-other-html.sh index 98e619aa5..a75fc96c2 100755 --- a/bin/gen-other-html.sh +++ b/bin/gen-other-html.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,16 +44,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -61,12 +63,13 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi + # setup bash file matching # # We must declare arrays with -ag or -Ag, and we need loops to "export" modified variables. diff --git a/bin/gen-sitemap.sh b/bin/gen-sitemap.sh index fc3a52295..3894daa7f 100755 --- a/bin/gen-sitemap.sh +++ b/bin/gen-sitemap.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,16 +44,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -61,12 +63,13 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi + # setup bash file matching # # We must declare arrays with -ag or -Ag, and we need loops to "export" modified variables. diff --git a/bin/gen-status.sh b/bin/gen-status.sh index 3ec016d69..d26fb2461 100755 --- a/bin/gen-status.sh +++ b/bin/gen-status.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,16 +44,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -61,12 +63,13 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi + # setup bash file matching # # We must declare arrays with -ag or -Ag, and we need loops to "export" modified variables. diff --git a/bin/gen-top-html.sh b/bin/gen-top-html.sh index 7c94f7eab..6e557a7bb 100755 --- a/bin/gen-top-html.sh +++ b/bin/gen-top-html.sh @@ -39,8 +39,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -48,16 +48,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -65,9 +67,9 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/gen-year-index.sh b/bin/gen-year-index.sh index 102228751..0821c0b0f 100755 --- a/bin/gen-year-index.sh +++ b/bin/gen-year-index.sh @@ -37,8 +37,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -46,16 +46,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -63,9 +65,9 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/gen-years.sh b/bin/gen-years.sh index eefce8470..ab7a5880e 100755 --- a/bin/gen-years.sh +++ b/bin/gen-years.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,16 +44,18 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || @@ -61,9 +63,9 @@ if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/md2html.sh b/bin/md2html.sh index cd4dbb502..b82026cff 100755 --- a/bin/md2html.sh +++ b/bin/md2html.sh @@ -87,8 +87,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -96,27 +96,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/output-index-author.sh b/bin/output-index-author.sh index 2a02e3a13..15d689ab6 100755 --- a/bin/output-index-author.sh +++ b/bin/output-index-author.sh @@ -41,8 +41,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -50,27 +50,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/output-index-inventory.sh b/bin/output-index-inventory.sh index 0d1b22591..2a31506d9 100755 --- a/bin/output-index-inventory.sh +++ b/bin/output-index-inventory.sh @@ -41,8 +41,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -50,27 +50,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/output-year-index.sh b/bin/output-year-index.sh index edf873071..4e5143dfc 100755 --- a/bin/output-year-index.sh +++ b/bin/output-year-index.sh @@ -7,7 +7,7 @@ # # It is usually invoked by: # -# -a bin/output-year-index.sh +# bin/output-year-index.sh # # Copyright (c) 2024 by Landon Curt Noll. All Rights Reserved. # @@ -42,8 +42,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -51,27 +51,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/pandoc-wrapper.sh b/bin/pandoc-wrapper.sh index a82e40da9..131fa4159 100755 --- a/bin/pandoc-wrapper.sh +++ b/bin/pandoc-wrapper.sh @@ -42,8 +42,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -51,27 +51,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/quick-readme2index.sh b/bin/quick-readme2index.sh index bc239f99b..17a8dd533 100755 --- a/bin/quick-readme2index.sh +++ b/bin/quick-readme2index.sh @@ -44,8 +44,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -53,27 +53,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/readme2index.sh b/bin/readme2index.sh index ed3cb31c6..ef078db77 100755 --- a/bin/readme2index.sh +++ b/bin/readme2index.sh @@ -38,8 +38,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -47,27 +47,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/sort.gitignore.sh b/bin/sort.gitignore.sh index ad05a2254..028010545 100755 --- a/bin/sort.gitignore.sh +++ b/bin/sort.gitignore.sh @@ -50,8 +50,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -59,30 +59,32 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi + # setup bash file matching # # We must declare arrays with -ag or -Ag, and we need loops to "export" modified variables. diff --git a/bin/status2html.sh b/bin/status2html.sh index 03ef26bd4..ba546e6a1 100755 --- a/bin/status2html.sh +++ b/bin/status2html.sh @@ -39,8 +39,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -48,27 +48,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/subst.default.sh b/bin/subst.default.sh index cc5a1cc37..64a8ca5c7 100755 --- a/bin/subst.default.sh +++ b/bin/subst.default.sh @@ -44,8 +44,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -53,27 +53,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/subst.entry-index.sh b/bin/subst.entry-index.sh index 9c3d0fa40..94856647a 100755 --- a/bin/subst.entry-index.sh +++ b/bin/subst.entry-index.sh @@ -44,8 +44,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -53,27 +53,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/subst.year-index.sh b/bin/subst.year-index.sh index 2118a9ee3..01382a5bb 100755 --- a/bin/subst.year-index.sh +++ b/bin/subst.year-index.sh @@ -44,8 +44,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -53,27 +53,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/tar-all.sh b/bin/tar-all.sh index cecab4768..85058d356 100755 --- a/bin/tar-all.sh +++ b/bin/tar-all.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,27 +44,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/tar-entry.sh b/bin/tar-entry.sh index 8a1a03c0f..11b85aa36 100755 --- a/bin/tar-entry.sh +++ b/bin/tar-entry.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,27 +44,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi diff --git a/bin/tar-year.sh b/bin/tar-year.sh index 8bf580507..dbbf3968c 100755 --- a/bin/tar-year.sh +++ b/bin/tar-year.sh @@ -35,8 +35,8 @@ # of bash between 4.2 and 5.1.7 might work. However, to be safe, we will require # bash version 5.1.8 or later. # -# WHY 5.1.8 and not 4.2? This safely is done because macOS homebrew bash we -# often use it "version 5.2.26(1)-release" or later, and the RHEL Linux bash we +# WHY 5.1.8 and not 4.2? This safely is done because macOS Homebrew bash we +# often use is "version 5.2.26(1)-release" or later, and the RHEL Linux bash we # use often use is "version 5.1.8(1)-release" or later. These versions are what # we initially tested. We recommend you either upgrade bash or install a newer # version of bash and adjust your $PATH so that "/usr/bin/env bash" finds a bash @@ -44,27 +44,28 @@ # # NOTE: The macOS shipped, as of 2024 March 15, a version of bash is something like # bash "version 3.2.57(1)-release". That macOS shipped version of bash -# will NOT work. For users of macOS we recommend you install homebrew, -# (see https://brew.sh), and then install homebrew bash (/opt/homebrew/bin/bash), -# and then arrange your $PATH so that "/opt/homebrew/bin" is ahead of "/bin". +# will NOT work. For users of macOS we recommend you install Homebrew, +# (see https://brew.sh), and then run "brew install bash" which will +# typically install it into /opt/homebrew/bin/bash, and then arrange your $PATH +# so that "/usr/bin/env bash" finds "/opt/homebrew/bin" (or whatever the +# Homebrew bash is). # # NOTE: And while MacPorts might work, we noticed a number of subtle differences # with some of their ported tools to suggest you might be better off -# with installing homebrew (see https://brew.sh). No disrespect is intended +# with installing Homebrew (see https://brew.sh). No disrespect is intended # to the MacPorts team as they do a commendable job. Nevertheless we ran # into enough differences with MacPorts environments to suggest you -# might find a better experience with this tool under homebrew instead. +# might find a better experience with this tool under Homebrew instead. # if [[ -z ${BASH_VERSINFO[0]} || ${BASH_VERSINFO[0]} -lt 5 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -lt 1 || ${BASH_VERSINFO[0]} -eq 5 && ${BASH_VERSINFO[1]} -eq 1 && ${BASH_VERSINFO[2]} -lt 8 ]]; then - echo "$0: ERROR: bash version needs to be >= 5.1.8: $BASH_VERSION" 1>&2 echo "$0: Warning: bash version >= 4.2 might work but 5.1.8 was the minimum we tested" 1>&2 - echo "$0: Notice: For macOS users: install homebrew (see https://brew.sh)," \ - "then install homebrew bash (brew install bash), and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ - "finds the homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 + echo "$0: Notice: For macOS users: install Homebrew (see https://brew.sh), then run" \ + ""brew install bash" and then modify your \$PATH so that \"#!/usr/bin/env bash\"" \ + "finds the Homebrew installed (usually /opt/homebrew/bin/bash) version of bash" 1>&2 exit 4 fi