Help with conditions AND installer Packages

Question

Hello everyone,
I need help still learning.
My shell is SHELL=/bin/sh based on env command
I am trying to write a package with Iceberg to push Office 2004 to 250 Macs. I need a preflight script with a condition that will stop my script if /Applications/Microsoft Office 2004 exists OR if OFFICE 2004 exists. Don't know if searching on the folder name is the best or if there is better way
If it doesn't exist I want it to continue with with placing Office 2004 in the /Applications folder.
I don't know how to do conditions (If, then, end)
PREFLIGHT SCRIPT
IF /Applications/Microsoft Office 2004 folder exist = STOP
IF /Applications/Microsoft Office 2004 folder doesn't exist continue with laying down files/folder in the package.
LAYDOWN FILES
LAY DOWN FILES IN ICEBERG FILE SECTION OF THE PACKAGE
POSTFLIGHT SCRIPT
#!/bin/sh
#Change to root directory
cd /
# Move Microsoft Office X folder to Messages Received folder
mv /Applications/Microsoft\ Office\ X /Messages\ Received
#Open Office 2004 Installer
open /Applications/Utilities/Installers/Office2004Installer
G4 1.42   Mac OS X (10.3.5)  

Answer 1

Hi Dmcrory,
   The answer to your question about ORing tests in a shell conditional statement could be something along the lines of:
if [ -d /Applications/Microsoft\ Office\ 2004 -o -d "/Applications/OFFICE 2004" ]
then
   exit 1
fi
I've included two different styles of quoting so you can choose which you prefer.
   That said, you appear to be asking us how to write shell scripts, starting from scratch. Time that you spend studying benefits you forever and sometimes benefits us, while time we spend doing your work is at best a trivial review for us. The above "-o" option, and many others, are documented at the compound comparison section of the Advanced Bash-Scripting Guide. Don't let the name fool you; the Guide actually assumes very little. The "Advanced" adjective refers to the completeness of work. In fact there are many good references.
   I used to have a long post of links to what I think are some of the better beginning UNIX tutorials and books. However, as others posted great links and I stole them, my post became too long so I put it in a web page. Bill Scott did the same thing so here is Bill's and here is mine.
   This is being written after reading your exchange with Roger. When you execute code that doesn't work, we certainly have no chance of knowing why without seeing the code. It generally helps a lot to see the output as well.
Gary
~~~~
   University politics are vicious precisely because the
   stakes are so small.
         -- C. P. Snow