summaryrefslogtreecommitdiffstats
path: root/release
diff options
context:
space:
mode:
authordwhite <dwhite@FreeBSD.org>1999-08-29 19:11:11 +0000
committerdwhite <dwhite@FreeBSD.org>1999-08-29 19:11:11 +0000
commitc0fcda6e0b5309b4c6fca3c39f53535a9f2ef00d (patch)
tree0cd49dfba65c55bc73eab7f4e4a2af24f34e9697 /release
parentd9c1a7ececab55a0366188c5c1614b10e9c103a6 (diff)
downloadFreeBSD-src-c0fcda6e0b5309b4c6fca3c39f53535a9f2ef00d.zip
FreeBSD-src-c0fcda6e0b5309b4c6fca3c39f53535a9f2ef00d.tar.gz
MFS: Dialog-ify 'reuse custom directory' question.
Diffstat (limited to 'release')
-rwxr-xr-xrelease/picobsd/build/build21
1 files changed, 14 insertions, 7 deletions
diff --git a/release/picobsd/build/build b/release/picobsd/build/build
index 34cb928..b5a7ad3 100755
--- a/release/picobsd/build/build
+++ b/release/picobsd/build/build
@@ -107,19 +107,26 @@ main() {
}
# check for existing custom config directory and ask user if they want to use it
+#
+# Note that specifying an alternate directory is broken due to relative
+# path assumptions during the kernel compilation phase of the build.
+# For now just dialog-ify.
check_for_old_custom() {
KEEP_CUSTOM=no
if [ ! -d ../custom ] ; then
return
fi
- clear
- echo " Custom directory setup"
- echo ""
- echo "There is an existing custom configuration linked to"
- ls -l ../custom | awk -F\> '{ print $2 }' | awk '{ print $1 }'
- echo ""
- read -p "Do you wish to use the existing custom directory? (yes/no): " KEEP_CUSTOM
+
+ CUSTOMLINK=`ls -l ../custom | awk -F\> '{ print $2 }' | awk '{ print $1 }'`
+ if dialog --title "Custom directory setup" --yesno "A custom configuration\n ${CUSTOMLINK}\nalready exists. Would you like to use it?" 7 50 ; then
+ KEEP_CUSTOM=yes
+ else
+ KEEP_CUSTOM=no
+ fi
+
+ # If custom is just a simple directory, assume the user wants it
+
}
# Ask for, and set the custom config directory
OpenPOWER on IntegriCloud