Re: Upgrading and not replacing in a distribution package on Tiger or Leopard
Re: Upgrading and not replacing in a distribution package on Tiger or Leopard
- Subject: Re: Upgrading and not replacing in a distribution package on Tiger or Leopard
- From: Iceberg-Dev <email@hidden>
- Date: Sat, 28 Mar 2009 01:40:37 +0100
On Mar 27, 2009, at 5:21 AM, Dymyr Winicki wrote:
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"/>
</choice>
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.
If there is an easier way of doing this I would like to know.
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.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden