"downgrade", "installed", "upgrade" behavior
"downgrade", "installed", "upgrade" behavior
- Subject: "downgrade", "installed", "upgrade" behavior
- From: Joakim Nyström <email@hidden>
- Date: Fri, 7 Dec 2007 13:51:38 +0100
Hi!
I have tried to figure out how the installer is comparing versions
but I can't get it. I tried to look in the available documentation
and also tried to do some searching on this list but I can't find the
information I want.
This is what I have tried to do:
I've created a small sample application in two versions - version 1
and version 2 and created a separate installer for each of them. When
nothing is installed I can use the Installer application to install
version 1 and it is possible to upgrade to version 2. Going back to
version 1 is prohibited after this since I don't allow downgrades. So
long, everything is fine. What puzzles me a bit is that I'm able to
install version 2 once again even though it is already installed. The
Installer GUI says it is an upgrade (which it is not) and when I
inspect the global javascript variable
"choices.*.packageUpgradeAction" it even says "downgrade". (I
expected "installed" - see file:///Developer/ADC Reference%
20Library/releasenotes/DeveloperTools/Installer.html#choices-
packageUpgradeAction )
To summarize, what I'm trying to accomplish is an installer that is
able to upgrade old versions but will recognized there is no need to
install anything if the same version or a newer version is already
installed.
I guess there is something I've missed or misunderstood. Please, can
anyone give me some advice or point to some relevant documentation.
It would also be interesting to know if there are any differences
between Tiger and Leopard regarding this issue.
Thanks!
/ Joakim Nyström
_______________________________________________
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