diff options
| author | Dave Reisner <d@falconindy.com> | 2011-12-04 18:09:16 +0100 |
|---|---|---|
| committer | Pierre Schmitz <pierre@archlinux.de> | 2011-12-04 18:13:13 +0100 |
| commit | 0e32334ccaf345430d5c2465cf8f9dc572e704f8 (patch) | |
| tree | 8f508a85ef9df28f333810958aefe283dad992c4 | |
| parent | 58d0ccc4f85c428e90f416a80359f6c0a3f91e47 (diff) | |
| download | devtools-0e32334ccaf345430d5c2465cf8f9dc572e704f8.tar.gz devtools-0e32334ccaf345430d5c2465cf8f9dc572e704f8.tar.xz | |
archbuild: exec makechrootpkg to preserve exit value
This fixes a compound command such as the one below from continuing even
if the first fails.
extra-x86_64-build && extra-i686-build
The problem is that 'cleanup 0' is triggered in archbuild even after an
unsucessful call to makechrootpkg. Since both archbuild and
makechrootpkg share the exact same cleanup function (from lib/common),
we simply force the shell to exit with the true return value by exec'ing
the call to makechrootpkg.
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
Signed-off-by: Pierre Schmitz <pierre@archlinux.de>
| -rw-r--r-- | archbuild.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/archbuild.in b/archbuild.in index 502654c..4e16d1f 100644 --- a/archbuild.in +++ b/archbuild.in @@ -83,4 +83,4 @@ else fi msg "Building in chroot for [${repo}] (${arch})..." -setarch "${arch}" makechrootpkg -c -n -r "${chroots}/${repo}-${arch}" +exec setarch "${arch}" makechrootpkg -c -n -r "${chroots}/${repo}-${arch}" |