Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Subject: [OT?] make bash script wait for called program to finish?
From: Thomas L Roche <tlroche AT us DOT ibm DOT com>
Message-ID: <OF8360AB8D.AF64EFE2-ON85256E7A.007A0B3E-85256E7A.007AB9B2@us.ibm.com>
Date: Sun, 18 Apr 2004 18:20:29 -0400
Content-Type: text/plain; charset="US-ASCII"

How to make a bash script wait for a program that it calls to finish?
Why I ask:

Don't ask me why this process is structured this way, but, in order to
install some code that I need in order to test my code, I hafta

a wget an (executable) extractor and some (non-executable) binaries

b run the extractor on the binaries. This runs some InstallShield UI
  that no one I know seems to know how to script. This creates an
  installer and a set of disk images.

c run the installer on the images. Fortunately this part I know how to
  script.

What I'd really like to do is script the whole thing, because each
step takes about 30 min, but step b eludes me. So what I'd like my
script to do is

0 wget

1 launch the extractor UI, which I will briefly twiddle

2 wait for the extractor to finish

3 check that the installer and images were created

4 run the installer on the images

I know how to script everything but 2: how can I do that?

Apologies if this is a FAQ: if so, please pass a pointer. If possible
please post to me as well as the list, and TIA.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/