odd upgrade behaviour on 10.5
odd upgrade behaviour on 10.5
- Subject: odd upgrade behaviour on 10.5
- From: "Lisa Weimer" <email@hidden>
- Date: Mon, 26 May 2008 16:18:04 -0600
- Thread-topic: odd upgrade behaviour on 10.5
Hi everyone!
I have two packages that are displaying odd behaviour when determining
if to upgrade. It seems to work fine in tiger (10.4) but not in leopard
(10.5). (I don't want any downgrading, and have made sure that option is
set to No). My problem in a nutshell: When the older version of my
software installed over top of the newer version of my software, the
older version overwrites the newer version.
Here is my situation:
Metapackage-A (10.0.58.0)
Package-Z: version 10.0.58.0 (older version)
Package-Y: version 1.0.1.0
Metapackage-B (1.2.111.0)
Package-Z: version 10.0.60.0 (newer version)
Package-X: version 1.2.111.0
The packages were built on 10.4 (10.4.11). Metapackage A was created
with iceberg, Metapackage B was created with package maker except for
the Package-Z component, which was created with iceberg.
On 10.5, no matter which order I install the metapackages, Package-Z
always overwrites itself. It fails to see if there is a newer version
and do nothing. However if I install just package-Z-10.0.58.0 over
Package-Z-10.0.60.0, then the installer correctly identifies that there
is a newer on package on the system and doesn't try to upgrade
package-Z.
Everything works correctly in 10.4. (no old packages clobbering newer
ones.)
The version is 4 digits and is set in the CFBundleShortVersionString in
the info.plist for all packages and metapackages. The packages are not
using the versions.plist (or bundleVersions.plist )
Questions:
1) Has anyone else seen this behaviour before?
2) Does anyone have ideas why this could be happening?
3) Should I be using versions.plist?
4) I started trying to create the packages on 10.5, but from the
documentation and from my first experiments packagemaker doesn't seem to
be using versions.plist or bundleVersions.plist anymore. Is it really
only determining upgrade behaviour from the package short version number
as well as the identifier? Has the 10.4 way, the 5-tuple consisting of
cfbundleshortversion, buildversion, and sourceversion been dropped?
5) Should I be using versions.plist in leopard installs?
If anyone has ideas I would appreciate hearing them, I am very stuck
atm.
Thanks,
Lisa
_______________________________________________
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