contrib: "set -e" behaves weird in subshells followed by OR. don't use.
This exits as expected:
```
$ cat s1.sh
#!/bin/bash
set -e
(
echo "a"
false
echo "b"
)
$ ./s1.sh
a
```
This does NOT exit, seemingly because of the outer context?!
```
$ cat s2.sh
#!/bin/bash
set -e
(
echo "a"
false
echo "b"
) || echo "c"
$ ./s2.sh
a
b
```
ref https://unix.stackexchange.com/questions/65532/why-does-set-e-not-work-inside-subshells-with-parenthesis-followed-by-an-or
This commit is contained in:
@@ -50,7 +50,7 @@ else
|
||||
info "not doing fresh clone."
|
||||
fi
|
||||
|
||||
# build the type2-runtime binary, this build step uses a separate docker container
|
||||
# build the type2-runtime binary, this build step uses a separate docker container
|
||||
# defined in the type2-runtime repo (patched with type2-runtime-reproducible-build.patch)
|
||||
TYPE2_RUNTIME_REPO_DIR="$PROJECT_ROOT_OR_FRESHCLONE_ROOT/contrib/build-linux/appimage/.cache/appimage/type2-runtime"
|
||||
(
|
||||
@@ -74,7 +74,7 @@ TYPE2_RUNTIME_REPO_DIR="$PROJECT_ROOT_OR_FRESHCLONE_ROOT/contrib/build-linux/app
|
||||
rm -rf "$TYPE2_RUNTIME_REPO_DIR/out"
|
||||
|
||||
info "runtime build successful: $(sha256sum "$TYPE2_RUNTIME_REPO_DIR/runtime-x86_64")"
|
||||
) || fail "Failed to build type2-runtime"
|
||||
)
|
||||
|
||||
info "building binary..."
|
||||
# check uid and maybe chown. see #8261
|
||||
|
||||
@@ -181,7 +181,7 @@ info "finalizing AppDir."
|
||||
mv usr/include usr/include.tmp
|
||||
delete_blacklisted
|
||||
mv usr/include.tmp usr/include
|
||||
) || fail "Could not finalize AppDir"
|
||||
)
|
||||
|
||||
info "Copying additional libraries"
|
||||
(
|
||||
|
||||
Reference in New Issue
Block a user