September 2009 - Installer-dev

Setting permissions in packagemaker
by Brant Sears 04 Sep '09

04 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com My project is set to build in MacOS 10.5. PackageMaker version 3.0.3. How should I be changing this? _______________________________________________ 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.… I cannot figure out how to get this program to set the permissions of a file to what I want them to be. The file is a signature file in my app bundle. It needs to be set to 444 (read for everyone). When it gets checked out of Subversion, it is 644. When PackageMaker creates a package and I install it, it is always set to 664. Everytime I make any change in PackageMaker, it seems to change the permissions on this file to 644. If I change the permissions for the file - PackageMaker doesn't seem to care. This email sent to site_archiver(a)lists.apple.com

1 0

SL checking bundle versions incorrectly?
by Kevin Brock 04 Sep '09

04 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812) Here's what's happening. 1) Install initial package -- bundle version 1.0.2 2) Run installer of new package, with bundle version 1.0.3 Any help would be appreciated. Kevin _______________________________________________ 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.… I've seen a strange error with SL upgrade of a package. result: 'PackageKit: skipping component "com.thecompany.theapp" (*-1.0.0-*-*) because the version *-1.0.2-*-* is already installed.' I figured something was wrong with the 1.0.3 package, so I uninstalled 1.0.2, installed 1.0.3 fresh. Worked. Now I tried to upgrade to 1.0.4, result: 'PackageKit: skipping component "com.mycompany.theapp" (*-1.0.0-*-*) because the version *-1.0.3-*-* is already installed.' so clearly is is able to see that 1.0.3 *is* 1.0.3. So, why didn't it see this during the upgrade from 1.0.2? Is it looking at a different plist entry in each case? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Authorization in an Installer plugin
by Erik Larsson 04 Sep '09

04 Sep '09

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 :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=TWnUA8a5djpW+MHhmy6g4BowuOfWkdHgX0csGXvhBHs=; b=KDGK5yhbBBrLQKQ4I2vosGJoUQ/a/ibq7wEeJ3b4Y4AGviA6pbtWwA4dLsbge9rxOX +T7d84x9sRWjxoWr6gH7iJZ9IpMT8ZR6SDSF1REdjymXytNxdZTTC1TJ9fpDugH95Gp1 YeBiVjz447Ixb8yVly0QNZWn+vo5ctwdLM/9U= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=cAYzvqi8qVfKAuMLhnDu6BrdBGOorga0UXQrmW2s0mf+8h8tM55XIxCpgjb6Cd74jK C42pC6HWZVDk+Ets6k4EyV+Cwxj/n4sUnHJwxZGwa6m9RIZ9MUNTPPL9+yS3VkNerT+l Fyswz5t0Dq8lvQWqyjGRKoVrnfGWwmiHNhG2c= User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812) Hi Greg, - Erik -Greg On Sep 4, 2009, at 7:17 AM, Erik Larsson wrote: Hi, Currently, I create a new Authorization reference and have the user authenticate, which means the user will have to type its password in a new authentication dialog, before calling a helper tool with AuthorizationExecuteWithPrivileges to carry out the actual operation. I would really like to avoid having the user type its credentials in two dialogs in a row (first for copying files, second for writing to the preference file). Any hints would be welcome... Regards, - Erik _______________________________________________ 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.… That's a possible solution, yes. Thanks for the suggestion... I didn't think about that. However, I have been so naughty as to peek into the object code of those installer plugins that magically seem to get authorized and found references to AuthorizationCreateFromExternalForm, and I thought that maybe there's something poorly documented about the Install procedure that they are making use of. Like a lingering AuthorizationRef from the first time the user authorized that you could somehow get hold of... Greg Neagle wrote: Since postflight/upgrade/install scripts run with privileges (assuming the package requires RootAuthorization), couldn't you just have your plugin write the data some place world-writable (like /tmp) and then have the postflight script read that and write to the system-wide prefs file? I'm writing an Installer plugin which needs to perform a privileged operation (writing to a system-wide preference file), and I'm wondering how I can reuse the authorization already made when installing the files. I have witnessed many installer plugins that execute after the file copy stage that make changes to otherwise protected files without requiring the user to re-authenticate, but I cannot understand how they do it. P.S. I sent the previous email from the wrong address. Blame Thunderbird. _______________________________________________ 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/greg.neagle%40disneyan… This email sent to greg.neagle(a)disneyanimation.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Authorization in an Installer plugin
by Greg Neagle 04 Sep '09

04 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com -Greg On Sep 4, 2009, at 7:17 AM, Erik Larsson wrote: Hi, Any hints would be welcome... Regards, - Erik _______________________________________________ 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/greg.neagle%40disneyan… _______________________________________________ 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.… Since postflight/upgrade/install scripts run with privileges (assuming the package requires RootAuthorization), couldn't you just have your plugin write the data some place world-writable (like /tmp) and then have the postflight script read that and write to the system-wide prefs file? I'm writing an Installer plugin which needs to perform a privileged operation (writing to a system-wide preference file), and I'm wondering how I can reuse the authorization already made when installing the files. I have witnessed many installer plugins that execute after the file copy stage that make changes to otherwise protected files without requiring the user to re-authenticate, but I cannot understand how they do it. Currently, I create a new Authorization reference and have the user authenticate, which means the user will have to type its password in a new authentication dialog, before calling a helper tool with AuthorizationExecuteWithPrivileges to carry out the actual operation. I would really like to avoid having the user type its credentials in two dialogs in a row (first for copying files, second for writing to the preference file). P.S. I sent the previous email from the wrong address. Blame Thunderbird. This email sent to greg.neagle(a)disneyanimation.com This email sent to site_archiver(a)lists.apple.com

1 0

Authorization in an Installer plugin
by Erik Larsson 04 Sep '09

04 Sep '09

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 :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=DJT2WCpyAExSNPFGx6FUyDqMaaxWoYx6zDiq5zC1ds0=; b=COqZtS6Aeg0BNEpJVgK49QcV+wStHByb0azTcnRzcSjRrBsqduyHsxLhulS3RF21Lq 0tt2mQqSuwIYQxwuxvY4BDkBNjna1WA6Ri0k11Hj6bCIW8Pn43jVfPhOc7iBeb1c/Yj1 le6ZOFdVr6bHQP/DwZnvjEUJaAbCacADLvvPg= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=rFjA9Qig8wApX2xeMBFN+Uv/vTtcr0mTYTwS8NIYFXFadxcEMopLHhBqT509UXWJUj qzsXWBxqzH09jsPEJovzWptlwO2anOqIk984HylmH7jl211g10QujP5FvljlYdK74c1G vXrDY8YgRSdlrljMJCKek2Rvv+XlJnRBbTGzk= User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; sv-SE; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 Hi, I'm writing an Installer plugin which needs to perform a privileged operation (writing to a system-wide preference file), and I'm wondering how I can reuse the authorization already made when installing the files. I have witnessed many installer plugins that execute after the file copy stage that make changes to otherwise protected files without requiring the user to re-authenticate, but I cannot understand how they do it. Currently, I create a new Authorization reference and have the user authenticate, which means the user will have to type its password in a new authentication dialog, before calling a helper tool with AuthorizationExecuteWithPrivileges to carry out the actual operation. I would really like to avoid having the user type its credentials in two dialogs in a row (first for copying files, second for writing to the preference file). Any hints would be welcome... Regards, - Erik P.S. I sent the previous email from the wrong address. Blame Thunderbird. _______________________________________________ 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 include a distribution script flat package in another distribution script project?
by Iceberg-Dev 03 Sep '09

03 Sep '09

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:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=nOjaic/3d6m6NBtYRa7yPxthSKaEuoeeDWrbOJ9ZZuM=; b=ON95lAWUvPkDeLNcE0p/AV8cCeEOe3NqoiqbbJqs/mCLbnDiS3Suso1B2ICrR5PilN pWMSeSP16tHW3ez/cBmIVBGIMZALdIh4zY1Y+ChlKwUCvQAuZhI70JHgB5nwqBnEi6tB fbMaaPri4L0SF4bZtC7YKcGWdVbJBGkjCjqm8= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=bb6kwyIhh7k5k0CvKxZX2tFUMKW6+SwLsYWz36xR4vxPKQkeQrKyT3GhawN7NXB0a3 gn9G9Z/UJveNJQZSc99UAJC2VyB1bDCogO6CHzB6S5Vh0XzK4f56toRMT0LKfXd61Stm ut/3rc2anB/7Im6W38QelJSzryV2qNloa/CMg= On Sep 2, 2009, at 3:32 PM, Iceberg-Dev wrote: On Sep 2, 2009, at 7:25 PM, Kennedy, Smith (Macintosh Software - IPG MCT) wrote: Hello, [...] my E.pmdoc, even though add C and D to the project, D comes up as a question mark. When I build E.pkg, it includes C but not D. Is there something I am doing wrong or is this just outside the capability of distribution scripts? If the latter, then it seems that distribution scripts are less capable than metapackages to create installers where a large number of software components need to be gathered together. You can not have a distribution script as a component of another distribution script. I was hoping I just didn't know what I was doing, rather than it being a limitation of the distribution script technology. This is really disappointing (I'm sure I am not even remotely the first person to voice this, given the age of distribution scripts). I hope this is a foolish oversight rather than a "feature" (conscious decision made by the designers) intended to prevent the re-distribution of other packages. If so, it is a lousy way to implement this. Deciding whether a package should be re-distributable or not is a policy decision best decided by the developers using PackageMaker to deploy their software. Packages are mainly payload containers. How does one go about doing that? Does that mean I need to merge D.pmdoc and E.pmdoc? If so, and I don't have access to D.pmdoc because it comes from someone else (third party who isn't sharing), what are my options aside from doing a "pkgutil --expand" etc.? _______________________________________________ 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.… On Sep 3, 2009, at 5:18 PM, Kennedy, Smith (Macintosh Software - IPG MCT) wrote: With the distribution script "format", a distribution script is just a XML file describing the hierarchy of packages, their requirements and the potential dependencies between each other. So as long as you have access to the Packages and the distribution scripts, merging them is not impossible. It's a bit like having access to 2 source code (the scripts) and libraries (the packages). You need to merge the 2 distribution scripts into one. You don't need to. Just extract the built packages and add them to the project (it's possible though I tend to remember it's not obvious). Then you need to analyse the distribution script and see what you need to add to your project. This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to get Choice Requirements to work when there is subchoices.
by Andrew Peckover 03 Sep '09

03 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Andrew I'm trying to work around what is likely a bug. I don't want the user having to choose the same folder for each of the 10 packages, otherwise I wouldn't have a problem, since the requirements work if there aren't subchoices. If anyone can make sense of this, let me know if you can think of a different way to accomplish what I am trying to do. Thanks, Andrew -------------------------------------------------------------------------------- _______________________________________________ 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/apeckover%40pgmusic.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.… Just in case anyone's interested, I was able to work around this by simply adding the functions to the script in the *built* package. ----- Original Message ----- From: "Andrew Peckover" <apeckover(a)pgmusic.com> To: "Installer-Dev mailing-list" <installer-dev(a)lists.apple.com> Sent: Wednesday, August 12, 2009 10:04 AM Subject: How to get Choice Requirements to work when there is subchoices. It appears that choice requirements don't work when there are subchoices. Maybe I'm not using the correct term "subchoices" - have attached a picture of what I mean - this is setup using raw editing mode, since it can't be done in the user interface (as far as I know). By examining the distribution script in raw editing mode, I can see what is happening... when there are subchoices, the requirement's function goes missing, even when added in raw editing mode. The function call is still there in the choice line (i.e. start selected="pm_choice1_selected()", the Function pm_choice1...." is gone. -- Anyways.... perhaps there is another way to do what I am trying to do: I have 10 packages, each of which need to be installed only if a certain file exists. The file is different for each of the 10 packages. In addition, the user can choose a custom folder to install to, but each package should be installed to the same custom folder. This is why I use subchoices, so in the Custom Install dialog, the user only has to choose the custom location once, and all of the sub-items will then install to that location. This email sent to apeckover(a)pgmusic.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to include a distribution script flat package in another distribution script project?
by Kennedy, Smith (Macintosh Software - IPG MCT) 03 Sep '09

03 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcosqciSidjJkji3Q9Op7NoP2cy+9A== Thread-topic: How to include a distribution script flat package in another distribution script project? On Sep 2, 2009, at 3:32 PM, Iceberg-Dev wrote: > > On Sep 2, 2009, at 7:25 PM, Kennedy, Smith (Macintosh Software - IPG > MCT) wrote: > >> Hello, >> >> [...] my E.pmdoc, even though add C and D to the project, D comes >> up as a >> question mark. When I build E.pkg, it includes C but not D. >> >> Is there something I am doing wrong or is this just outside the >> capability of distribution scripts? If the latter, then it seems >> that >> distribution scripts are less capable than metapackages to create >> installers where a large number of software components need to be >> gathered together. > > You can not have a distribution script as a component of another > distribution script. I was hoping I just didn't know what I was doing, rather than it being a limitation of the distribution script technology. This is really disappointing (I'm sure I am not even remotely the first person to voice this, given the age of distribution scripts). I hope this is a foolish oversight rather than a "feature" (conscious decision made by the designers) intended to prevent the re-distribution of other packages. If so, it is a lousy way to implement this. Deciding whether a package should be re-distributable or not is a policy decision best decided by the developers using PackageMaker to deploy their software. > > You need to merge the 2 distribution scripts into one. How does one go about doing that? Does that mean I need to merge D.pmdoc and E.pmdoc? If so, and I don't have access to D.pmdoc because it comes from someone else (third party who isn't sharing), what are my options aside from doing a "pkgutil --expand" etc.? _______________________________________________ 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 specify name of my receipts?
by Andrew Peckover 02 Sep '09

02 Sep '09

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Andrew On Sep 2, 2009, at 10:28 PM, Brant Sears wrote: _______________________________________________ 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/apeckover%40pgmusic.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.… As far as I've been able to tell, the receipt name is only determined by the name of the folder that your source files are in. As far as I've been able to figure out, there is no way to change the receipt name (including edits in raw mode), except by changing the name of your folder - but I could be wrong. ----- Original Message ----- From: "Iceberg-Dev" <dev.iceberg(a)gmail.com> To: "Brant Sears" <brant(a)mac.com> Cc: <installer-dev(a)lists.apple.com> Sent: Wednesday, September 02, 2009 2:33 PM Subject: Re: How to specify name of my receipts? I'm installing some things to various directories under /Library such as a LaunchAgent. The installer creates a receipt called "library.pkg". I'm trying to figure out where in PackageMaker I should specify the name of the receipt. Any ideas? I've tried changing the choice name. IIRC, PackageMaker creates the name from the name of the files included. You can not change it without editing the project in raw mode or the project XML file with a text editor. This email sent to apeckover(a)pgmusic.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to specify name of my receipts?
by Iceberg-Dev 02 Sep '09

02 Sep '09

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:in-reply-to:references :mime-version:content-type:message-id:cc:content-transfer-encoding :from:subject:date:to:x-mailer; bh=xiKEbXIsJUf0sIOMUpegb48bYB3xEMgNgUNwnaipUnI=; b=qkVVwycpr9mHO+Xu1kDDjDpNqwR7iYoL0SXd9Hei5jqfB+rPb9Q3nCo/0ipPcVf6PR lXYkz5Nox8HbEP879VcTFQUEgoFq9c1Q8ZT+ckl74yT2FYW1uL8POldGzhQ+Gux0PFKE dlZhAeUSKqpRMe6oalVDYDdJuk+UNhBnDcDiY= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=in-reply-to:references:mime-version:content-type:message-id:cc :content-transfer-encoding:from:subject:date:to:x-mailer; b=W5K5oR4q2HgSoE5sJ09hL8+hYZjfDVAGkMi54uK7EOPUgDTWn8Xxj8hI/4PdFgJ+sH W5cbHisjnc/zIasVIYmIeRmT5DIRi2+55xeRlx5O2r7fItRLlB+0E3BJlRBkBE2ETG6j ADcjpHiiTxGKDDL/neNPnyAPEsNgKknixYjWo= On Sep 2, 2009, at 10:28 PM, Brant Sears wrote: _______________________________________________ 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.… I'm installing some things to various directories under /Library such as a LaunchAgent. The installer creates a receipt called "library.pkg". I'm trying to figure out where in PackageMaker I should specify the name of the receipt. Any ideas? I've tried changing the choice name. IIRC, PackageMaker creates the name from the name of the files included. You can not change it without editing the project in raw mode or the project XML file with a text editor. This email sent to site_archiver(a)lists.apple.com

1 0