previous version clobbering newer version?
previous version clobbering newer version?
- Subject: previous version clobbering newer version?
- From: Lisa Weimer <email@hidden>
- Date: Thu, 18 Sep 2008 15:40:35 -0600
- Thread-topic: previous version clobbering newer version?
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