From a2b1892f170857cfa28db220c64f99b7449d95a1 Mon Sep 17 00:00:00 2001
From: Jeremy Katz <katzj@redhat.com>
Date: Thu, 30 Jul 2009 10:16:40 -0400
Subject: Let's not exit from buildinstall.functions, say, ever

Exiting from a function being called could leave things in a
weird state.  The exit makes sense for mkinitrd, maybe less
so when building installer images
---
 scripts/buildinstall.functions | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

(limited to 'scripts')

diff --git a/scripts/buildinstall.functions b/scripts/buildinstall.functions
index 3b10dffde..2afb65235 100755
--- a/scripts/buildinstall.functions
+++ b/scripts/buildinstall.functions
@@ -56,11 +56,8 @@ EOF
     while [ $n -lt ${#FILES[*]} ]; do
         FILE="${FILES[$n]}"
         if [ "$FILE" == "not found" ]; then
-            cat 1>&2 <<EOF
-There are missing files on your system.  The dynamic object $bin
-requires ${NAMES[$n]} n order to properly function.  mkinitrd cannot continue.
-EOF
-            exit 1
+            echo "WARNING: The dynamic object $bin requires ${NAMES[$n]} n order to properly function."
+            continue
         fi
        case "$FILE" in
          /lib*)
-- 
cgit