Re: previous version clobbering newer version?
Re: previous version clobbering newer version?
- Subject: Re: previous version clobbering newer version?
- From: Pradeep Kumar Udupi <email@hidden>
- Date: Thu, 18 Sep 2008 14:59:48 -0700
- Thread-topic: previous version clobbering newer version?
I had encountered a very similar problem recently. The receipt based version
check of pkgs does not happen when the pkgs are installed from a
metapackage. It just installs all the pkgs that are listed in default
install unless blocked by the pkg's check tools.
The man page for 'installer' tool states,
"The installer command is used to install Mac OS X installer packages to a
specified domain or volume. The installer command installs a single package
per invocation, which is specified with the -package parameter ( -pkg is
accepted as a synonym). It may be either a single package or a metapackage.
In the case of the metapackage, the packages which are part of the default
install will be installed unless disqualified by a package's check tool(s)."
One way to solve this issue is to use InstallationCheck scripts to control
the installation. In the InstallationCheck script you can check if a
previous version of that pkg is installed or not and if installed do a
version check of the receipt pkg and the one that's installed.
- pradeep
> Hi all,
> Has anyone ever seen this behaviour, if so how did you fix it?
>
> Product 1 contains
> Package A.pkg version 1.0.2.0 is installed on the system
> Package product 1.pkg
>
> Product 2 contains
> Package A.pkg version 1.0.1.0
> Package product 2.pkg
>
> Product 1 is installed on the system. I then install Product 2 after
> product 1 has been installed. Note that product two has an older version
> of package A.pkg.
>
> My problem is that the installer when installing package A.pkg version
> 1.0.1.0 will remove 'obsolete' files that are actually the newer files
> of Package A version 1.0.2.0. (mostly language and support documents)
> while refusing to install the older version of the app (which has a
> versions.plist). The end result is you have a new app with missing
> support files that have been removed.
>
> The odd thing is if I remove package A completely from the metapackage,
> and install them stand alone, the correct thing happens: The install
> halts and says a newer version exists on the system.
>
> Is there some magic .plist file that controls this behaviour? Why does
> it only happen when the package is in the metapackage?
>
> Any thoughts?
>
> Thanks,
> Lisa
>
>
> Lisa Weimer
> Build/Install
> SMART Technologies
>
> _______________________________________________
> 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
>
-----------------------------------------------
Robosoft Technologies - Come home to Technology
Disclaimer: This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. Emails to and from our network may be logged and monitored. This email and its attachments are scanned for virus by our scanners and are believed to be safe. However, no warranty is given that this email is free of malicious content or virus.
_______________________________________________
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