Always do 'cabal sandbox init'.

Running 'cabal sandbox init' when the sandbox is already initialized
doesn't cause problems. On the other hand, when guarded by
'[ ! -e ${sandbox_dir} ]', it's possible for the dependency sandbox
configurations to disappear.

Author: ntc2

build-sandbox.sh

@@ -85,12 +85,10 @@ for repo in ${PRIVATE_GITHUB_REPOS} ; do
   fi
 done
 
-if [ ! -e ${sandbox_dir} ] ; then
-    for pkg in ${PKGS} ; do
-        (cd deps/$pkg && ${CABAL} sandbox --sandbox="${HERE}/${sandbox_dir}" init)
-    done
-    ${CABAL} sandbox --sandbox="${HERE}/${sandbox_dir}" init
-fi
+for pkg in ${PKGS} ; do
+  (cd deps/$pkg && ${CABAL} sandbox --sandbox="${HERE}/${sandbox_dir}" init)
+done
+${CABAL} sandbox --sandbox="${HERE}/${sandbox_dir}" init
 
 if [ "${dotests}" == "true" ] ; then
   for pkg in saw-script llvm-verifier jvm-verifier cryptol-verifier saw-core ; do