All these scripts have the same expectation, of failing on anything unexpected.
So setting the same options the same way everywhere leads to more consistency
and predictability.
#!/usr/bin/env bash
-set -x
set -e
-set -u
set -o pipefail
+set -u
+set -x
if [ -f /etc/os-release ]; then
cat /etc/os-release
#!/usr/bin/env bash
-set -eux
+set -e
+set -o pipefail
+set -u
+set -x
/cygwinsetup.exe --quiet-mode --wait --packages autoconf2.5
/cygwinsetup.exe --quiet-mode --wait --packages automake
#!/usr/bin/env bash
set -e
+set -o pipefail
+set -u
set -x
if [ "$( uname -s )" = "Darwin" ]; then
#!/usr/bin/env bash
-set -eux
+set -e
+set -o pipefail
+set -u
+set -x
ci/mingw-install.sh
#!/usr/bin/env bash
-set -eux
+set -e
+set -o pipefail
+set -u
+set -x
ci/mingw-install.sh
#!/usr/bin/env bash
-set -eux
+set -e
+set -o pipefail
+set -u
+set -x
pacman -S --noconfirm --needed \
autoconf \
#!/usr/bin/env bash
-set -eux
+set -e
+set -o pipefail
+set -u
+set -x
ci/mingw-install.sh
# this script does something close to the work flow end users may follow when
# building Graphviz
-set -x
set -e
set -o pipefail
+set -u
+set -x
# output some info for debugging
uname -rms
# this script does something close to the work flow end users may follow when
# building Graphviz
-set -x
-set -u
set -e
set -o pipefail
+set -u
+set -x
# output some info for debugging
uname -rms
# this script does something close to the work flow end users may follow when
# building Graphviz
-set -x
set -e
set -o pipefail
+set -u
+set -x
# output some info for debugging
uname -rms