Re: How to make update package with Package Maker?
Re: How to make update package with Package Maker?
- Subject: Re: How to make update package with Package Maker?
- From: email@hidden
- Date: Mon, 18 May 2009 19:09:42 -0400
Namaste!
My apologies for hijacking this thread...
I think I have a related issue.
I have implemented Sparkle in my applications. To the best of my
knowledge it is doing its job. It connects, senses an update,
downloads it, and either extracts the zip (which is what I temporarily
have in place at the moment) or runs the .pkg that is there. The .pkg
fails though, so I've implemented the application-only zip for now.
The reason I need to use a package for updates is there are other
files in addition to my app that need to be changed as well and they
are not in the same folder as the app.
The package appears to execute, but does not overwrite the application
file. There are no errors nor an install.log file.
I am wondering if the reason this happens is the name & identifier
have not changed from the old version?
Karl states to "bump the version number." What does he mean by that
more specifically?
Thanks!
Peace, Love, and Light,
/s/ Jon C. Munson II
Quoting Greg Neagle <email@hidden>:
Or alternately, your updater package must have a different name and
identifier and contain pre-install logic that makes sure the earlier
version of the software is installed before it can run.
I prefer Karl's recommendation, however.
-Greg
On May 18, 2009, at 10:36 AM, Karl Kuehn wrote:
On May 18, 2009, at 1:00 AM, Chris Gardner wrote:
I have a pragram of alpha version and want to update this version
to add new files. After making a update package with Package
Maker tool, and setuping the update package, the same name of
original file will be instead, but the others will disappear. Why?
Apple's installer system is being helpful, it is just not working
the way you think. When it installs a package it writes out a
receipt (or into the reciepts.db) the list of files that it
installed. When you then install something with the same
name/identifier it compares the list of files to what is already
installed, and figures that if a file that was in the old version
is not in the new version it should remove it (cleaning up after
itself).
The problem in this case is that you are trying to out-think the
installer, and so it is removing files that you still want in the
later version.
How can I update the old specified files ,meanwhile do not delete
the others with update package made by Package Maker.
Don't try and create packages that are just updaters. Create a new
full installer of the latest version (and bump the version
number), and Apple's installer will take care of "updating" for you.
--
Karl Kuehn
email@hidden
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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