site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:reply-to:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:from; b=QN5FM9UX/LJF4TiZUrcXEH6zEF2UyMjWv8lqfQvy5fVuWq/rinHzv/blQXn137B6Qv31prI9MDCNLvzh/GDySYipyyve0ruWuqku7vV7sq7KX1oZynuFuF0IAl2uPsWdSZKWmINqCACkjjE3zAldPgIxVYdf7/vWflPYszoHf+8= User-agent: Thunderbird 1.5.0.5 (Windows/20060719) Hello Stéphane, I agree that my description matches your doc, except that I am using the Requirements, which according to my reading of the docs will supercede the InstallationCheck script in 10.4 and 10.3. When using the InstallationCheck script, which should only happen on earlier systems, I am returning 112 (bits 5 and 6 both set), so that I could display an error string (#16). I have read in the Legacy docs that there may be bugs in some implementations. http://developer.apple.com/documentation/DeveloperTools/Conceptual/SoftwareD... The new Software Delivery docs don't even seem to mention the use of bits 5 & 6. Are you suggesting that I should use only InstallationCheck scripts, and clear bit 6? Thanks for your help! - Rick On jeudi, septembre 7, 2006, at 04:12 PM, cohen.rick@gmail.com wrote: Hi folks, _______________________________________________ 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... Stéphane Sudre wrote: I am creating a product installer metapackage, using the wonderful Iceberg. The product runs on 10.2 and above. However, some components are different in Tiger and in Panther/Jaguar. Also, some other components are different between Intel and PPC Macs. I am using separate packages for these different components, and I'm trying to use the installer to decide which components are right for each possible Mac. All of the components have the Selected attribute set. None of them have the "Required" flag set. Iceberg allows the creation of requirements, which are supported in 10.4 and 10.3, and ignored in 10.2. According to documentation, in 10.3 and 10.4 if requirements are found, the InstallationCheck script is ignored. So what I've done is to create both requirements and InstallationCheck scripts for each component. If I install my product on 10.4 (which uses the requirements and ignores the script), everything seems to work perfectly. If I look at the components during the Install by pressing the Customize button, I can see that the components that do not match the requirements are greyed out. If I run my installer on a 10.3 system, the error message that is associated with my first 10.4-only component is displayed, and the user's only option is to close the installer. If I run my installer on a 10.2 system, a screen immediately appears that says the software cannot be installed on this computer. Is it possible to achieve the same results that I see on my 10.4 system while installing on earlier versions of OS X? What value are you returning in the InstallationCheck script when it shall be greyed out? Your description looks to match the "How can I install different versions of an application depending on the Mac OS X version?" case of the document available here: http://s.sudre.free.fr/Software/documentation/Iceberg/English.lproj/document... This email sent to site_archiver@lists.apple.com