March 2010 - Installer-dev - lists.apple.com

Where do I start?
by Allan Marcus 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com OK, I would like to start to add some JavaScript as a requirements test to my installer. I cannot find any documentation on how to do this. I can find Installer JavaScript References on the Mac Dev web site, but nothing on how to do it. Where do I put my scripts? Are there examples? is there any documentation at all? --- Thanks, Allan Marcus 505-667-5666 _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Removing the Installer Dialogs in Packages
by Karthikeyan M 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=27xC93jj8hLuzDHzCK5d+wmauMNKG0x3P7OQDOgTo10=; b=nA7p9aIcdAs4WBMOJUfxb5EcFhLPiDE9M1N+6RnpQQZhwKLnf54OktlGTFQWWfq7G8 D99buEPVHQ4r2xIqCUAaZXWO87TcDaEyZzQJnJwImTFY3vKzbq8kOn4aqQ13mbte0dLV OUSjwro2qW8Il7nmT6J1Hdm6Uk+4BJWHYhNxE= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=Weqiw6fDN8xPRGCvtFsYbdxYBMegtyvkqMWQyoljeYM+EsaeCd3G9V+Z50CmAcxpW3 uRU47ZeJ0OOViyUbKYBGa2UhhEjlze1rYByXfsQlQpbIeF1nhSycVfTX2zk/8TQn5n7r dhHL+zBINNrySp+7yNy8vaWBEFF0cuLgCSN6E= User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 Hi, We have to create a one Click Install Package. Package needs to be as follows _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… If users clicks the package file, it should show the Welcome Screen (Installer) and the same screen should have Install Button. if the install button is clicked, it should ask for authentication then it should show the Progress and Finish/Close Window. The total installation should should only have three user intervention. 1. Double-click to launch 2. First screen (Welcome screen) should show the Install Button 3. User should get Authentication Dialog 3. The installer should finish, the window should close automatically Thanks& Regards, Karthikeyan M This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to test to see if a program is running?
by Allan Marcus 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Please let me clarify. I see that I can have a script run for system requirements. I cannot find any documentation on how to use this feature. I have a test.sh script that I put into the script path field. questions: 1) what should the script return to indicate pass or fail? exit 0 for pass exit 1 for fail ? 2) the script doesn't seem to get included in the package. In the installer log when I run the installer it appears the install is trying to run the script from the original location. --- Thanks, Allan Marcus 505-667-5666 On Mar 5, 2010, at 9:49 AM, Allan Marcus wrote: > Hi, > > I'm trying to build an installer for FireFox that I can push out with puppet. The installer will be run from the command line (silent install). > > The issue is that if FireFox is running, bad things can happen if the installer runs. Is there a way (and how) to check to see if FireFox is running and stop the install if it is? > > Some way to incorporate > ps -efc | grep -i FireFox > > --- > Thanks, > > Allan Marcus > 505-667-5666 > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/installer-dev/allan%40lanl.gov > > This email sent to allan(a)lanl.gov _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to test to see if a program is running?
by Bill Coderre 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 5, 2010, at 8:50 AM, Alexander von Below wrote: > http://developer.apple.com/mac/library/qa/qa2001/qa1123.html > > Am 05.03.2010 um 17:49 schrieb Allan Marcus: >> >> I'm trying to build an installer for FireFox that I can push out with puppet. The installer will be run from the command line (silent install). >> >> The issue is that if FireFox is running, bad things can happen if the installer runs. Is there a way (and how) to check to see if FireFox is running and stop the install if it is? >> >> Some way to incorporate >> ps -efc | grep -i FireFox If you are using distribution-based packages (and you almost certainly should be), the Installer JavaScript Reference has some good stuff for you: http://developer.apple.com/mac/library/documentation/DeveloperTools/Referen… _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Upgrade/downgrade darwin daemons with Installer
by Jakub Bednar 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hello list, I have some problems with PackageMaker and I can't find the answer. I have spent some time now going through the archives, reading Apple's delivery guide and experimenting but still nothing. I'm using PackageMaker 3.0.4 on Snow Leopard 10.6.2. My questions/problems are: 1. How can I tell from a preinstall script, whether this is a fresh install or an upgrade? I need to distinguish these two so I can stop/unload my deamons before upgrading them. I have checked the environment and parameters passed to the scripts, but there is nothing. Older versions of PackageMaker were able to specify also preupgrade and postupgrade scripts. Do I need to check for older version of the receipt again manually in preinstall/postinstall? 2. Can I somehow tell installer during an upgrade, that a system reboot is needed after the end of installation? I'm installing a KEXT, so the older version sometimes can't be unloaded as it may be referenced by the kernel. In this case a system reboot is needed to get the new version loaded. The thing is, that with clean install, or when the unload succeeds, the reboot is not needed. That is why I don't want to set it as an action for the package. 3. I have run some tests with installing simple darwin command-line tool. I made two versions of the binary and two installers. One has a package version set to 1.0 and the other to 2.0. There is no Info.plist, just one executable in every installer. Therefore there are no components displayed in PackageMaker so I can't check/uncheck the allow donwgrade checkbox. Now if I run the installer with version 2.0, it installs the package and writes the receipt with version 2.0. Then if I run the installer with version 1.0, it just replaces the binary and rewrites the receipts with version 1.0 :-( Can anyone please help me solve this problems? Thanks a lot, Jakub _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to test to see if a program is running?
by Alexander von Below 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com http://developer.apple.com/mac/library/qa/qa2001/qa1123.html Am 05.03.2010 um 17:49 schrieb Allan Marcus: > Hi, > > I'm trying to build an installer for FireFox that I can push out with puppet. The installer will be run from the command line (silent install). > > The issue is that if FireFox is running, bad things can happen if the installer runs. Is there a way (and how) to check to see if FireFox is running and stop the install if it is? > > Some way to incorporate > ps -efc | grep -i FireFox > > --- > Thanks, > > Allan Marcus > 505-667-5666 > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Installer-dev mailing list (Installer-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/installer-dev/below%40mac.com > > This email sent to below(a)mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

How to test to see if a program is running?
by Allan Marcus 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi, I'm trying to build an installer for FireFox that I can push out with puppet. The installer will be run from the command line (silent install). The issue is that if FireFox is running, bad things can happen if the installer runs. Is there a way (and how) to check to see if FireFox is running and stop the install if it is? Some way to incorporate ps -efc | grep -i FireFox --- Thanks, Allan Marcus 505-667-5666 _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Payload ownership
by Don Montalvo 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:in-reply-to :mime-version:content-type:message-id:content-transfer-encoding:cc :from:subject:date:to:x-mailer; bh=DjxreJu18cMcSYVU4WzsFYvsertwtbC6blx9kwsYvP8=; b=fih8c86tFI7zEJXH71tv+HAFyRDrsKjP1XtxRBY4nkQG30slBeuc6SZkgYeWHLhNL3 BuS3cvnCRKoCDfTpzk65Zvr5J9xxhhk2Lm/C02axv+UzB/u/TK6wfpXEtNWcjJP+A7d3 BjC7h6BMzbjEns2K3bOBLes4mXlJBHc0cFp0o= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=Ycv+3baDNN/+Znu3cXAKN3vcLXy6Gq32dwSF0f06mp0xPfPZxvzkjrWi7DGeBkkvqN w5ZVx8vqhxBmFiWJdIZBITHIJD0H/3Nb469x3M4ZL94Mtmew4YIEDTiTmE7PZcwUBUx6 2dGeRD0fe4icYreU3SPCvVwChAx1j2UCxPL/A= Hi Sakshi, We set root:wheel on all the items in Packagemaker/Iceberg project file. Unless there's a reason to have a different user and group. Or, if there is a reason to not have root:wheel we would need a consistent local account across the board that uses the same UID. I'm not sure how accurate the last sentence is, but since we had that issue in the past, we're more confident with root:wheel than with any other. :) Don On Mar 5, 2010, at 10:24 AM, sakshi wrote: > :). So do you also enforce root:wheel in the staging area or only in the pmdoc? > > Thanks! > Sakshi > > On Fri, Mar 5, 2010 at 9:51 PM, Don Montalvo <donmontalvo(a)gmail.com> wrote: > That's what happened to me. :) Since my development Mac was not bound to AD, my account had 504 as the UID. The target computer was bound to AD and the user account had a UID of something like 12312312123123 (just a guess) which is the UID assigned by AD. > > If the pkg is set to force ownership to root:wheel everything should work fine. We standardize on root:wheel to avoid these kinds of UID issues, and since there is no consistent local account we can assign as owner:group of the pkg payload. > > Don > > On Mar 5, 2010, at 9:58 AM, sakshi wrote: > > > The usernames are different on both machines. The UID on my machine is 501 whereas on the buggy machine it is 1133xxx693. > > > > I am confused by multiple things: > > 1. The PackageMaker UI works fine but the commandline does not. > > 2. The machine has two users, say, user1 and user2. The staging area contents list owner as user1 for all files and directories. The pmdoc UI shows the owner to be user1. When the pkg is built, the ownership varies from user1 to user2 to <unknown> for various files. > > 3. When I look at the contents pane in PackageMaker, the owner dropdown shows user1. While experimenting, I changed it to root. When I next viewed the dropdown, user1 was not even listed. > > > > I am not clear on how the ownership is decided at pkg creation time. Does it come from the contents.xml file lying in the pmdoc? Does it come via an actual parse of the staging area and therefore is decided at every run? To verify this I manually edited the contents.xml and changed all user1 instances to 1133xxx693. But even this did not work. > > > > Changing the payload ownership to root:admin is on my ToDo list but before that I want to get my concepts right. Would just changing the staging area and then resaving the pmdoc (to regenerate the contents.xml files) suffice? > > > > Thanks, > > Sakshi > > > > On Fri, Mar 5, 2010 at 8:46 PM, Don Montalvo <donmontalvo(a)gmail.com> wrote: > > Hi Sakshi, > > > > Just curious, is the username exactly the same on both computers? I mean the short name (not John Doe, but johndoe or jdoe). Also, what is the UID on the account (on each machine)? We deal with managed environments, so the UID is consistent across all Macs (longish AD string). Lastly, is there a reason the payload can't simply be owned by root:wheel (the standard we use)? :) > > > > Don > > > > On Mar 5, 2010, at 5:54 AM, sakshi wrote: > > > > > Hi Don, > > > > > > The user:group do exist on the machine. In fact when I see the pmdoc on my machine, files are labeled root:admin and on the buggy machine (the staging area and) the pmdoc contents get set to the user's username:admin. I was under the impression that the staging area would define what does into the pmdoc and finally the pkg. This situation seems to differ from my opinion: the pmdoc gets set from the staging area but the pkg has a mind of its own. > > > Does the fact that packagemaker is being invoked from the commandline and not the UI have any impact? > > > > > > Thanks, > > > Sakshi > > > > > > On Fri, Mar 5, 2010 at 1:40 AM, Don Montalvo <donmontalvo(a)gmail.com> wrote: > > > sakshi <heysakshi(a)gmail.com> wrote: > > > > > > > Hi, > > > > > > > > I am running into a very weird issue while building a pmdoc and need some > > > > help with my basics. I created a pmdoc using a staging folder on my machine. > > > > I shared it with the team to build and test on their machines. On one > > > > machine we are seeing weird behavior and some files end up getting created > > > > with an <unknown> owner. The pmdoc is being built through the commandline. > > > > > > > > All other files have a valid username associated with them, just these > > > > specific files are linked to <unknown>. I've verified the staging folder on > > > > that machine and it has the right permissions and owner. I opened that copy > > > > of the pmdoc in PackageMaker and it also has the expected owner. Somehow the > > > > final pkg differs. I used lsbom and verified that the pkg itself contains a > > > > 'corrupted' file. > > > > > > > > Any clues on where else I could look? > > > > > > > > Thanks! > > > > Sakshi > > > > > > Hi Sakshi, > > > > > > Sounds like the user:group defined in the pkg is not present on the target computer? For example, if you set user to "jdoe" who has UID of 504, but there is no UID 504 on the target computer, this can happen. It happened last week when I was testing a new pkg. Since it happened before, I recognized the problem. I changed the user:group to something that's on every computer. Then tested again and all went well. > > > > > > Don > > > > > > > > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Payload ownership
by sakshi 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=NZn6vx9/9fovif6h5xTFMi094mXZW2E3CHyR6FHh3DI=; b=qnhyAlMxKR5WeG50iL9U8fSYjbrG+WvxkP4OvSLDyv87fTBErpMoyuwGW5rGncff7s NCDRuu220/l8LLSLSnYQEHYsnqeFRgcToE8uTqggdl9R1zSaWvqDdAdcLXYAZ9+DdvHX iVopivTPIUTCuQouzn79efv2Y2ef18Y7y2mEg= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=rwkGhl/LPdbe8xP6FJsoU9VoP2TRJ0A02/zeaxsLiPpl0gMuGTU2mpVLv431aR7b85 4WjhJc9X6gfGNK0ggRv4EikOWOAxK0jpE8Fg2EKGzaKmxoAddb10YAN+oyoswkYdY64h wrxlPdu2FBH5XJ0wpDxijswDf6dZdBOgDWJ38= _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Payload ownership
by Don Montalvo 05 Mar '10

05 Mar '10

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:in-reply-to :mime-version:content-type:message-id:content-transfer-encoding:cc :from:subject:date:to:x-mailer; bh=aqTeJHJe9J3GRrfzaujhHX7r4O4bXCyMI87juFGc7qk=; b=AH8ZHE703h/oEsFpG5rOWaV0Y8UrSYQHcNcpqxzezC+N26zI68vNHZObcTLuBNbl0V 6He7cmqZ7rD7/aBaErC85q/blxO4Et4NuuJiOHPw5v6nzWEa1nVBlwamWe3BDgaMK+QG E1yy3eStzzwH+fnxSH7YkMBuorFC5hJOR6Vs4= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=E4WNdb2mtetxbVhB3WMuPF9sSG7UV53SpAoFDPe//em2IC2AF/ZaqrsRLyG+vSxc6n 02iF5STDAEk+PsX70haTkQO7ba0EtD8pm69eT+UObUuDlVtgMrHURPFcmJSwEuuQCoqX 8c46l5pm4d/wS4csKx5V/FtGxVwF6TznR+k9U= That's what happened to me. :) Since my development Mac was not bound to AD, my account had 504 as the UID. The target computer was bound to AD and the user account had a UID of something like 12312312123123 (just a guess) which is the UID assigned by AD. If the pkg is set to force ownership to root:wheel everything should work fine. We standardize on root:wheel to avoid these kinds of UID issues, and since there is no consistent local account we can assign as owner:group of the pkg payload. Don On Mar 5, 2010, at 9:58 AM, sakshi wrote: > The usernames are different on both machines. The UID on my machine is 501 whereas on the buggy machine it is 1133xxx693. > > I am confused by multiple things: > 1. The PackageMaker UI works fine but the commandline does not. > 2. The machine has two users, say, user1 and user2. The staging area contents list owner as user1 for all files and directories. The pmdoc UI shows the owner to be user1. When the pkg is built, the ownership varies from user1 to user2 to <unknown> for various files. > 3. When I look at the contents pane in PackageMaker, the owner dropdown shows user1. While experimenting, I changed it to root. When I next viewed the dropdown, user1 was not even listed. > > I am not clear on how the ownership is decided at pkg creation time. Does it come from the contents.xml file lying in the pmdoc? Does it come via an actual parse of the staging area and therefore is decided at every run? To verify this I manually edited the contents.xml and changed all user1 instances to 1133xxx693. But even this did not work. > > Changing the payload ownership to root:admin is on my ToDo list but before that I want to get my concepts right. Would just changing the staging area and then resaving the pmdoc (to regenerate the contents.xml files) suffice? > > Thanks, > Sakshi > > On Fri, Mar 5, 2010 at 8:46 PM, Don Montalvo <donmontalvo(a)gmail.com> wrote: > Hi Sakshi, > > Just curious, is the username exactly the same on both computers? I mean the short name (not John Doe, but johndoe or jdoe). Also, what is the UID on the account (on each machine)? We deal with managed environments, so the UID is consistent across all Macs (longish AD string). Lastly, is there a reason the payload can't simply be owned by root:wheel (the standard we use)? :) > > Don > > On Mar 5, 2010, at 5:54 AM, sakshi wrote: > > > Hi Don, > > > > The user:group do exist on the machine. In fact when I see the pmdoc on my machine, files are labeled root:admin and on the buggy machine (the staging area and) the pmdoc contents get set to the user's username:admin. I was under the impression that the staging area would define what does into the pmdoc and finally the pkg. This situation seems to differ from my opinion: the pmdoc gets set from the staging area but the pkg has a mind of its own. > > Does the fact that packagemaker is being invoked from the commandline and not the UI have any impact? > > > > Thanks, > > Sakshi > > > > On Fri, Mar 5, 2010 at 1:40 AM, Don Montalvo <donmontalvo(a)gmail.com> wrote: > > sakshi <heysakshi(a)gmail.com> wrote: > > > > > Hi, > > > > > > I am running into a very weird issue while building a pmdoc and need some > > > help with my basics. I created a pmdoc using a staging folder on my machine. > > > I shared it with the team to build and test on their machines. On one > > > machine we are seeing weird behavior and some files end up getting created > > > with an <unknown> owner. The pmdoc is being built through the commandline. > > > > > > All other files have a valid username associated with them, just these > > > specific files are linked to <unknown>. I've verified the staging folder on > > > that machine and it has the right permissions and owner. I opened that copy > > > of the pmdoc in PackageMaker and it also has the expected owner. Somehow the > > > final pkg differs. I used lsbom and verified that the pkg itself contains a > > > 'corrupted' file. > > > > > > Any clues on where else I could look? > > > > > > Thanks! > > > Sakshi > > > > Hi Sakshi, > > > > Sounds like the user:group defined in the pkg is not present on the target computer? For example, if you set user to "jdoe" who has UID of 504, but there is no UID 504 on the target computer, this can happen. It happened last week when I was testing a new pkg. Since it happened before, I recognized the problem. I changed the user:group to something that's on every computer. Then tested again and all went well. > > > > Don > > > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0