site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Thread-index: Act3BPXEfzqwMuYfTIChg69bYrW8jQFM0WUQ Thread-topic: Unable to enforce version checks in metapackage Hi, have you tried manually creating a .dist script in your .mpkg bundle? You could set a 'choice' for each of your packages, and have it call a javascript function to determine if a newer version of the package is present or not, and enable, disable, select, deselect the choice accordingly... http://developer.apple.com/library/mac/#documentation/DeveloperTools/Referen... http://developer.apple.com/library/mac/#documentation/DeveloperTools/Referen... Regards, Dave -----Original Message----- From: installer-dev-bounces+david.glover=prometheanworld.com@lists.apple.com [mailto:installer-dev-bounces+david.glover=prometheanworld.com@lists.apple.com] On Behalf Of Monte Benaresh Sent: 29 October 2010 02:02 To: Installer-Dev mailing-list Subject: Unable to enforce version checks in metapackage Hi All, Some of you may have seen that I am interested in creating a metapackage that only installs its components when they are newer than what is already installed. Thanks to Stéphane for his replies to my last post. Originally, I tried twiddling all the available version numbers in Iceberg. I found that the only instance of the version number that is checked for simple packages is "Short Version" under "Display Information." However, as other developers have seen, this mechanism is absent when installing a metapackage, and all components are installed regardless of whether they are older or newer. Today I thought of using the InstallaitonCheck script to enforce version checking. First I simply modified a working script to 'exit 113' and defined a string for it. This all works fine in the simple package, but when placed into a metapackage I get the following behavior: 1. Log error: Oct 28 17:44:22 Monte-Intel-Mac Installer[2793]: Package Authoring Error: Infinite loop between <choice> attributes and mixed state aborted. 2. No alert box. 3. The component generating the failure is grayed-out. Hovering over its entry in the "customize" list shows tip text with my error message string. I did more experimenting, and #1 happens whenever InstallaitonCheck returns a non-0 return code. Are metapackage installs really so badly broken, or are there some other rules I must abide by when dropping components into a metapackage? My goal is simply to combine multiple installs for the convenience of the user while preventing back-rev components from getting installed. Thank you, Monte Benaresh PACE Anti-Piracy _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/david.glover%40promethe... This email sent to david.glover@prometheanworld.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com