November 2007 - Installer-dev

Re: PackageMaker home directrory installers for pre 10.5 systems
by Stéphane Sudre 25 Nov '07

25 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On dimanche, novembre 25, 2007, at 04:38 PM, patrick machielse wrote: Op 25 nov 2007, om 10:24 heeft Stéphane Sudre het volgende geschreven: On dimanche, novembre 25, 2007, at 01:28 AM, patrick machielse wrote: If you need to support 10.4 or earlier, yes. preinstall.sh ------------- #!/usr/bin/env sh # install location for iPhoto exporters PluginDir="$HOME/Library/Application Support/iPhoto/Plugins" # create the plugin folder if needed mkdir -p "$PluginDir" # create a soft link in /var/tmp/ ln -shf "$PluginDir" /var/tmp/com.mycompany.myproduct postinstall.sh -------------- #!/usr/bin/env sh # clean up the install symlink (OS X won't) rm -f /var/tmp/com.mycompany.myproduct Otherwise, check the usual suspects: - permissions - file name (no extensions) - line endings (Unix vs Mac vs Windows) (should be Unix). My € 0.02 (***) -- Stephane (***) The $ is so much depreciated these days. _______________________________________________ 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 developing a plugin (exporter) for iPhoto 08 that should be installed in ~/Library/Application Support/iPhoto/Plugins. Since installers are encouraged now, and I certainly don't want the user to have to dig around in ~/Libarary/ (using the Finder, on paths that Spotlight won't search) I thought I'd turn to PackageMaker. For deployments on 10.5 I can specify that the product only be installed into the user's Home Directory domain, and all is well. However, this PackageMaker domain is not supported on 10.4 and the (very light) documentation of PackageMaker doesn't explain how to achieve the same result on earlier versions of the OS. I've searched for a solution on the internet and it was suggested some years ago that you could install the product in a temporary directory and then have a post-install script move the installed component to its final destination. Alternatively, a symlink to a location in the home directory could be created in /tmp/ using a pre-flight script, and the installer would install through that. Is this still the way to do it in 2007? The flat package format which includes the new domain feature is 10.5 or later only. Apple _could_ have supplied a more intelligent installer as part of 10.4.11 :-( I'm afraid that while we think Apple can or should do a lot of things, they still are limited by resources and schedules. I personally think it's a good point that this domain features has been added in 10.5 (though I have some questions on the level of implementation of this feature that I need to eliminate through tests. Such as: since it's at the distribution script level, does this mean you can't have a specific domain for a package inside a distribution? ). I'm trying to install into the plugin folder by using the following scripts: The problm I'm having now (only tested on 10.5.1) is that the Installer doesn't run my scripts. I can see that they are included in the package, they just never seem to be executed. The same seems to be true for the distribution action (get iPhoto and quit it); it never seems to run. What am I missing? It could be the usual mistakes with preinstall and postinstall scripts. They are only executed when the package is installed for the first time on the system (*). If you want this to be run for every installation, use preflight and postflight (**). (*) Removing the receipt used to be a workaround. I'm not sure anymore with the new installation data base. (**) A smart move in the 10.5 package format was to rename postflight and preflight scripts to preinstall and postinstall. It can be confusing if you know the old formats but in the end, it will be easier. This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker home directrory installers for pre 10.5 systems
by patrick machielse 25 Nov '07

25 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Op 25 nov 2007, om 10:24 heeft Stéphane Sudre het volgende geschreven: On dimanche, novembre 25, 2007, at 01:28 AM, patrick machielse wrote: If you need to support 10.4 or earlier, yes. preinstall.sh ------------- #!/usr/bin/env sh # install location for iPhoto exporters PluginDir="$HOME/Library/Application Support/iPhoto/Plugins" # create the plugin folder if needed mkdir -p "$PluginDir" # create a soft link in /var/tmp/ ln -shf "$PluginDir" /var/tmp/com.mycompany.myproduct postinstall.sh -------------- #!/usr/bin/env sh # clean up the install symlink (OS X won't) rm -f /var/tmp/com.mycompany.myproduct What am I missing? patrick _______________________________________________ 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 developing a plugin (exporter) for iPhoto 08 that should be installed in ~/Library/Application Support/iPhoto/Plugins. Since installers are encouraged now, and I certainly don't want the user to have to dig around in ~/Libarary/ (using the Finder, on paths that Spotlight won't search) I thought I'd turn to PackageMaker. For deployments on 10.5 I can specify that the product only be installed into the user's Home Directory domain, and all is well. However, this PackageMaker domain is not supported on 10.4 and the (very light) documentation of PackageMaker doesn't explain how to achieve the same result on earlier versions of the OS. I've searched for a solution on the internet and it was suggested some years ago that you could install the product in a temporary directory and then have a post-install script move the installed component to its final destination. Alternatively, a symlink to a location in the home directory could be created in /tmp/ using a pre-flight script, and the installer would install through that. Is this still the way to do it in 2007? The flat package format which includes the new domain feature is 10.5 or later only. Apple _could_ have supplied a more intelligent installer as part of 10.4.11 :-( I'm trying to install into the plugin folder by using the following scripts: The problm I'm having now (only tested on 10.5.1) is that the Installer doesn't run my scripts. I can see that they are included in the package, they just never seem to be executed. The same seems to be true for the distribution action (get iPhoto and quit it); it never seems to run. This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker home directrory installers for pre 10.5 systems
by Stéphane Sudre 25 Nov '07

25 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On dimanche, novembre 25, 2007, at 01:28 AM, patrick machielse wrote: If you need to support 10.4 or earlier, yes. _______________________________________________ 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 developing a plugin (exporter) for iPhoto 08 that should be installed in ~/Library/Application Support/iPhoto/Plugins. Since installers are encouraged now, and I certainly don't want the user to have to dig around in ~/Libarary/ (using the Finder, on paths that Spotlight won't search) I thought I'd turn to PackageMaker. For deployments on 10.5 I can specify that the product only be installed into the user's Home Directory domain, and all is well. However, this PackageMaker domain is not supported on 10.4 and the (very light) documentation of PackageMaker doesn't explain how to achieve the same result on earlier versions of the OS. I've searched for a solution on the internet and it was suggested some years ago that you could install the product in a temporary directory and then have a post-install script move the installed component to its final destination. Alternatively, a symlink to a location in the home directory could be created in /tmp/ using a pre-flight script, and the installer would install through that. Is this still the way to do it in 2007? The flat package format which includes the new domain feature is 10.5 or later only. This email sent to site_archiver(a)lists.apple.com

1 0

PackageMaker home directrory installers for pre 10.5 systems
by patrick machielse 25 Nov '07

25 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com thanks, patrick -- Hieper Software _______________________________________________ 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 developing a plugin (exporter) for iPhoto 08 that should be installed in ~/Library/Application Support/iPhoto/Plugins. Since installers are encouraged now, and I certainly don't want the user to have to dig around in ~/Libarary/ (using the Finder, on paths that Spotlight won't search) I thought I'd turn to PackageMaker. For deployments on 10.5 I can specify that the product only be installed into the user's Home Directory domain, and all is well. However, this PackageMaker domain is not supported on 10.4 and the (very light) documentation of PackageMaker doesn't explain how to achieve the same result on earlier versions of the OS. I've searched for a solution on the internet and it was suggested some years ago that you could install the product in a temporary directory and then have a post-install script move the installed component to its final destination. Alternatively, a symlink to a location in the home directory could be created in /tmp/ using a pre-flight script, and the installer would install through that. Is this still the way to do it in 2007? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Installer is not showing Upgrade button in Leopard
by Stéphane Sudre 23 Nov '07

23 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On vendredi, novembre 23, 2007, at 03:42 PM, JanakiRam wrote: Hi All, _______________________________________________ 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 maintaing Mac application(developed on Tiger ) which has an installer , created using Package Maker. When i install my app first time on Tiger, it used to show Install button and each subsequent time it shows Upgrade button. Now i've tried to install my package on Leopard , it shows Install every time. Am i missing any thing ? Do i need to add any thing to make it work on Leopard. Is this a known issue on Leopard ? Please help me to analyze this behavior. Thanks in Advance. Considering the pre/post install/upgrade scripts are gone in the new Leopard flat package format (the preinstall and postinstall scripts now refer to the old preflight and postflight scripts), you can somehow bet that this is a feature and not an issue. This email sent to site_archiver(a)lists.apple.com

1 0

Installer is not showing Upgrade button in Leopard
by JanakiRam 23 Nov '07

23 Nov '07

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=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=EOzs6isVnEt2lG+Uecm9QT97XEIV6MiaPNYg7IxgAbw=; b=Z0gcE4RDxD2qI+wENzyZX58C47PuUo3uii5tmMAhyZ7cfxgcffKgh62g2an+ffW6h4CgCjaIoxi3JooeR96YmCqTarv+PiK5xE0+GkHtYtGeknPK4wNno/98lsXpLSfMtcxOhfKVbZywxZDusuHOWX4YzPmq0vLwpkxlSeGGNQU= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=evqJLS9br0DEt5w2wcwMSmeU+QjbADOLowNDJxUTQgTzkVNwk96G3IB0EUwukltHs3iV7SyGnEVnS2WOKuUv5wDRrNQ9K1sWForEIin1Wl0jDSpKmIaYSqa0JOOUNIijgZb45elL1wdzSyLskBqEW5nRc68QsXTdaqO0dXf/hvs= _______________________________________________ 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

Another localization issue with the License Step in Leopard Installer
by Stéphane Sudre 21 Nov '07

21 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Your package may look something like this: MonPaquetage.pkg Contents Resources French.lproj License.txt Let's imagine you're running Leopard in English. What happens when you reach the License Step is this: * BUT the buttons are in English. Not OK. * The License is displayed in French, the popup button says Français. * The buttons are now correctly (1) displayed in French. _______________________________________________ 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.… While the issue regarding fr.lproj vs French.lproj still exists in Mac OS X 10.5.1, there is another issue involving localization support. Let's say you have a package (10.2 format) that includes a License Agreement in French only. * The License is displayed in French, the popup button says Français. OK. Let's imagine you click on the popup button to select Français (which is not pointless in this case), what you see is this: So Installer.app can display the buttons in French but not without manually selecting the language. A bug report will be filed as soon as Bug Reporter lets people submit Bug Report anew. (1) Actually, they are not displayed correctly as the Enregistrer… label is cut off since the button is not wide enough. But that's another bug report. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard Installer sometimes skips the "Destination Select" pane?
by Stéphane Sudre 19 Nov '07

19 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On mercredi, novembre 14, 2007, at 08:15 PM, Peter Bierman 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.… At 11:21 AM -0600 11/14/07, Mark Krenek wrote: We have experienced a few times where the Leopard Installer will skip the "Destination Select" pane. It will go straight from the License pane to the "Installation Type" screen. If you then press "Change Location" (I think that's the name of the button), it will go back to the "Destination Select" pane. Has anyone else seen this? It is not 100% reproducible - I can't figure out what triggers this behavior. The particular package is a distribution metapackage, but I've also seen it in a standard .pkg. This is a feature of Leopard. If there's only one possible destination and the volume has been checked by the time the user would get to that panel, the panel is skipped. Is it also a feature that when you have a Root Volume Only flag, the Choose Location… button is visible (package, metapackage)? IIRC, there is no way to change the Startup Disk without restarting the Mac. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Groups, resources, installer stuff
by Bill Coderre 17 Nov '07

17 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Wow, that was a BIG mistake. Excuse me. On Nov 16, 2007, at 3:52 PM, Bill Coderre 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/bc%40apple.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.… installer-dev(a)group.apple.com -- internal Apple installer app developers and installer script developers installer-dev(a)lists.apple.com -- EXTERNAL list. It is now safe to talk about Leopard on it, but not what Apple does internally. (I sometimes post something like "this is how Apple checks for 64-bit" but I get yelled at if not careful.) External School and Corporate developers often have to take N installers and bundle them together into One Big Installer. You can check the group archives for hints and tricks. Jack Matthew, head of Installer.app, PackageMaker, and MacBuddy and Migration Assistant and maybe other stuff Scott Amory, my boss, head of Installer Script Engineering, which writes pretty much all the installer scripts at Apple. Wayne Kilthau and Kaz Shinohara make the disk images that get blasted onto new Macs, and also the Restore Discs that come with Macs. They have some tools to combine scripts together, but they might not have enough tools. This email sent to bc(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Groups, resources, installer stuff
by Bill Coderre 16 Nov '07

16 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.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.… installer-dev(a)group.apple.com -- internal Apple installer app developers and installer script developers installer-dev(a)lists.apple.com -- EXTERNAL list. It is now safe to talk about Leopard on it, but not what Apple does internally. (I sometimes post something like "this is how Apple checks for 64-bit" but I get yelled at if not careful.) External School and Corporate developers often have to take N installers and bundle them together into One Big Installer. You can check the group archives for hints and tricks. Jack Matthew, head of Installer.app, PackageMaker, and MacBuddy and Migration Assistant and maybe other stuff Scott Amory, my boss, head of Installer Script Engineering, which writes pretty much all the installer scripts at Apple. Wayne Kilthau and Kaz Shinohara make the disk images that get blasted onto new Macs, and also the Restore Discs that come with Macs. They have some tools to combine scripts together, but they might not have enough tools. This email sent to site_archiver(a)lists.apple.com

1 0