First, I appologize for the title... it's not dripping! I meant DROPPING
With the help of so many Nationer's I can't thank everyone, but thanks everyone! I did ake this Q of lis tot he apple-installer-dev list and after discussions there moed from PackageMaker back to Casper Composer. I just want to try to use the tool-set that Casper provides if at all posible. Creating the pkg that did all that I wanted:
•Deleted unneeded files from a previously poorly designed dmg installer;
•Installing Flash Player "Plugin" that incuded the first SUS Daemon fpsaud
•Revised the fpsaud fonfig file mms.cfg to turn off the automatic and silent updates of future FP
Just learning to do those theree exposed me to most of the basic tools used to make pkg file sfor Casper Deployment. I've written an internal How do Doc that's too lenghty (and ha screen shots) to post here. But I did want to give a quick start wuide for any newbies that might find this a helpfuld post for helping grasp to tool and how it likes things presented so it does what you want. Here is te qick start, and please correct me or add to this as you see it fitting:
1) Double-Click the Flash Player .dmg file
2) Right-Click the Installer Icon and select “Show Package Contents”
3) Expand the Contents folder then the Resources folder and drag the Adobe Flash Player.pkg file to where you want it.
4) Launch Casper Composer and drag the Adobe Flash Player.pkg (from step #3 above) into the left pane of Composer. It will appear under the heading “PACKAGES”
5) Click on the Adobe Flash Player.pkg in the left pane and on the right will be an option in the right pane to Convert to Source. Click the Convert to Source button.
6) The Package is converted to Source and appears under the SOURCES heading in the left pane.
7) Next, we want to place one file onto the Macs that the package runs to. That file is the mms.cfg file that we changed to the settings we want instead of the default settings. To tell Composer where you want the file to be placed, click on the name of the SOURCES file in the left pane. You will now see a folder named Library in the right pane. We want to add a new directory path to where we want the file placed then place it there in Composer.
8) Click the triangle to the left of the Library folder to expand it. Since we want to place our mms.cfg file into Library/Application Support/Macromedia and there is already a Library folder with an Application Support folder in it we only need to create the missing Macromedia folder inside the Application Support folder then place the mms.cfg file in that folder.
To create the Macromedia folder exand the Application Support folder and right-click on the name “Application Support” and select Create New Directory. A new Untitled Folder appears, just type the name you want it to be. In this case “Macromedia”, then hit Enter on your keyboard. Find the file mms.cfg on your computer and drag it on top of the Macromedia folder and Composer places it there.
9) Finally, we want to place our script into the package we are creating in Composer. The script deletes files that were incorrectly placed when the previous version of the Flash Player Installer ran. We want the files to be deleted before the new Flash Player plugin gets installed. We then want to run the script as a PREFLIGHT Script. To Create a place to put our preflight script, in Composer ‘s left pane, expand the triangle to the left of our Source file. Doing so reveals three folders: Scripts; Settings; Snapshots. Expand the Scripts folder and you’ll see a postflight script already there. To create a preflight script, right-click (or Command-click) the Scripts folder and select Add Shell Script then select preflight.
10) Click on the preflight script in the left pane. Look at the script that was automatically created in the right pane. Since we want to use our own script, select the text as shown in figure X and delete it. Now using a text editor open the script you created and copy the script and paste it into the area where you deleted the text in the preflight script of Composer.
11) Figure X shows the preflight script with our script in it. To save your script you must fo to Composer’s Main Menu and select File/save (Command-S). If you click anywhere else before saving, then your script will not be saved and you’ll need to repeat step #10, then remember to SAVE before clicking on anything else.
12) We have all our elements in the Source file of Composer and are ready to Build the Package that will be sent to each computer that needs the update. Click the triangle to the left of the Source file in Composer to collapse all the folders under it, and click the source file. With the source file selected, click the Build as PKG icon in the upper part of the Composer window.
13) You will be presented with a dialog box asking where you want to save the PKG file that’s about to be created. Navigate to where you want it save and click Save.
14) When the Unsupported scripts for flat packages warning appears, click the Build as Non-flat PKG button. Your PKG file is saved in the location you indicated.
15) Your PKG file is now ready for testing and eventual deployment.
