site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Hi I have looked into the packageUpgradeAction properties Kind Regards ...dymyr On 28/03/2009, at 11:40 AM, Iceberg-Dev wrote: On Mar 27, 2009, at 5:21 AM, Dymyr Winicki wrote: [...] </choice> If there is an easier way of doing this I would like to know. _______________________________________________ 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... and on Leopard if the receipt exists for the same package id it always says upgrade even though it may be a downgrade so the property seems to have a bug with Leopard as far as I can gather. Theoretically Packages and Distributions can be made to upgrade and not just replace files however using PackageMaker from the gui I haven't yet been able to do this. With Packages I have using Iceberg. I have had trouble using Iceberg with metapackages with large number of files in the – With a simple mockup it upgrades and doesn't downgrade except with Leopard where it just replaces the files anyway. I have not seen any answer on the forum (either to my questions or to others) that have broached this – so I will post my answer in the hope it will help others. <choice id="choice1" title="btcc" Location="/Applications" selected="pm_choice1_selected()" enabled="false" start_enabled="false" > <pkg-ref id="com.edalive.btcc.pkg"/> This will select if the same or an upgrade but in all cases will not enable to be changed. I also changed customLocation to the keyword Location which means you cannot change the location of the install. With distribution scripts, you can tune more finely the behavior between upgrade, downgrade and so on of a choice. Have a look at the packageUgradeAction properties of the choice class. This email sent to site_archiver@lists.apple.com