RE: PackageMaker & a Script
RE: PackageMaker & a Script
- Subject: RE: PackageMaker & a Script
- From: George Spiese <email@hidden>
- Date: Wed, 20 Jun 2012 16:43:22 -0400
Apparently it's OK to place the script
in the third party package itself... interesting, and thank you for solving
that one, shew. Now my final issue, is where in Composer do I tell it the
destination for the file I want to place? It's the mms.cfg file you mention,
and I've edited it as you suggested but also edited the second item in
the .cfg file as well to:
SilentAutoUpdateEnable=0
Do I simply edit the "Files For
Package" to reflect where I want it placed? I thought this was the
path to my original, not the destination. I'm used to seeing a destination
field, but there is none that I can find, or am I missing it?
Thanks,
George Spiese
Macintosh Technician
CSC
500 Gulfstream Road, Savannah, GA 31408
Global Outsourcing Services | p:912.395.9718 | email@hidden | www.csc.com
*************************************************************************************
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
From:
Herrington_Hasaan <email@hidden>
To:
George Spiese/USA/SC/CSC@CSC,
Date:
06/20/2012 04:25 PM
Subject:
RE: PackageMaker
& a Script
Basically I did this for my use:
1. Install the Flash player normall and make the change to the /Library/Application\
Support/Macromedia/mms.cfg to read AutoUpdateDisable=1
2. Mount the install_flash_player_osx.dmg
3. Right click install Adobe Flash Player and select show package contents
4. Navigate to the Contents/Resources and drag Adobe Flash Player.pkg in
to the sources pane of Composer and convert to source.
5. Drag the /Library/Application\ Support/Macromedia/mms.cfg in to the
source you just created in Composer
6. Under the Abobe Flash source in Composer , Right clickthe scripts
folder and add Shell script, Pre-flight script, then add the contents of
the script you want to execute.
7. Build it as a newly created (non-flat package) in Composer
Hasaan Herrington
Technical Support III
Anchorage School District
email@hidden<mailto:email@hidden>
________________________________
From: George Spiese [email@hidden]
Sent: Wednesday, June 20, 2012 12:14 PM
To: Herrington_Hasaan
Cc: email@hidden
Subject: Re: PackageMaker & a Script
I had reviewed the Casper Admin Guide previously, and posted to their Discussions.
There it was suggested that Casper Composer "might" not be the
best tool to do what I want. Now, going back to it, the only place I see
to place the preflight script is in the Adobe Flash Player .pkg, something
that doesn't seem right- I wonder if placing it in the third party package
IS the correct place to put it. To test it, I did place it there. But now
I want to place a file on the source Mac so I drag the file I want to place
into the left pane of Composer. But now, I don't see a place to add the
destination for that file. PackageMaker has a field for the destination,
but I can't see it in Composer. Where do I indicate the destination? Please
note that I am not building this pkg from a build Mac. I don't want to
use a snapshot in this case.
Thanks,
George Spiese
From: Herrington_Hasaan <email@hidden>
To: George Spiese/USA/SC/CSC@CSC,
Date: 06/20/2012 02:22 PM
Subject: Re: PackageMaker & a Script
________________________________
See page 70 in in the Casper Administrators Guide, to set a preflight script
in your Composer package.
Hasaan Herrington
Technical Support III
Information Technology
Sent from my mobile device
-----Original message-----
From: George Spiese <email@hidden>
To: Herrington_Hasaan <email@hidden>
Sent: Wed, Jun 20, 2012 17:49:01 GMT+00:00
Subject: Re: PackageMaker & a Script
I first tried it in Casper Composer, but had no success with placing a
script that fired when delivered. Their Discussions folk suggested PackageMaker
which is where I am now with this little project. I'd much rather continue
using Composer as the tool for making Packages. I am glad yours worked
flawlessly, can you tell me where you placed the script and any other step-by-step
instruction for me to get mine to also run flawlessly?
Thanks,
George Spiese
From: Herrington_Hasaan <email@hidden>
To: George Spiese/USA/SC/CSC@CSC,
Date: 06/20/2012 10:55 AM
Subject: Re: PackageMaker & a Script
________________________________
Hey George,
I just did the same process you outlined yesterday using Composer from
the Casper Suite, used a preflight script to remove existing files, installed
the adobe flash. Pkg and my edited .cfg file. The process worked flawlessly.
Hasaan Herrington
Technical Support III
Information Technology
Sent from my mobile device
-----Original message-----
From: George Spiese <email@hidden>
To: "email@hidden" <email@hidden>
Sent: Wed, Jun 20, 2012 14:05:03 GMT+00:00
Subject: PackageMaker & a Script
I am using Apple's PackageMaker v3.0.5 to create a mpkg file that contains
three items:
•A shell script
•An Adobe Flash Player .pkg file
•A .cfg file
Everything works except the script. How do I get this script to fire when
sending to a remote Mac?
Each item works when tested individually. The test was using Casper Suite's
Casper Remote to send each to a remote Mac. The shell script sent, unpackaged
fires and deletes three files on the remote Mac, just fine. The adobe Flash
.pkg sent the same way installs the Flash Plugin and daemon as expected.
The file is the mms.cfg. File that the Adobe Software Update Daemon reads.
I've changed the settings of this file to what I want it to be. This file
gets placed where I've indicated in the destination field of PackageMaker.
I have changed the permissions on the script to Owner=root and Group=admin
which had no affect. The script isn't running. I need to know where in
PackageMaker to place the script and how I ensure it runs when sent to
a remote Mac.
Thanks,
George Spiese
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden