Re: Never upgrade. Always install
Re: Never upgrade. Always install
- Subject: Re: Never upgrade. Always install
- From: "Andrew Peckover" <email@hidden>
- Date: Wed, 2 Sep 2009 09:28:56 -0700
Hello Justin,
<When this happens, files that are missing (usually
the application bundle that should go to /Applications) is not
installed.>
Are you sure that this isn't being caused by that allow relocation checkbox
in the Components section? Just making sure.
--
I haven't found a way around the 'upgrade' issue either, other than to
always make sure when I change the contents of my package I use a different
folder name for my source files. Then at least customers' files don't get
deleted (which I still can't believe is allowed)
Andrew
----- Original Message -----
From: "Justin Williams" <email@hidden>
To: <email@hidden>
Sent: Wednesday, September 02, 2009 8:56 AM
Subject: Re: Never upgrade. Always install
It's a metapackage that contains an application file and another
subpackage that installs some config files and certificates into the
Library folder. We build each package on the fly using a set of
scripts, because the subpackage's contents is unique to each user.
Before I got around this issue by just trashing the receipts files in /
Library/Receipts/ but with the transition away from those, I haven't
found a reliable way to accomplish it in Leopard & Snow Leopard.
- j
On Sep 2, 2009, at 10:53 AM, Nick Peelman wrote:
Howard brings up an interesting question...what else are you
installing that makes an installer necessary? I assume you're dumping
files into /Library or a Kext or something?
-nick
On Wed, Sep 2, 2009 at 10:33 AM, Justin
Williams<email@hidden> wrote:
Hi,
I am running into an issue with my Installer where many times it will
determine that the user should be upgrading their package rather than
installing fresh. When this happens, files that are missing (usually
the
application bundle that should go to /Applications) is not installed.
I'd prefer to set my package to never have the option to upgrade and to
just
always install/overwrite the existing file on the user's Mac. I
thought I
could do this by adding the "pkgutil --forget net.secondgear.mybinary"
command to my postinstall script to remove it from the receipts
database,
but it doesn't seem to make a difference.
What's the preferred method to handle something like this? I was
hoping
there would be a magic button I could click in PackageMaker, but sadly,
it
didn't seem to exist.
Any help would be appreciated.
-
Justin Williams
http://secondgearsoftware.com/
-
Check out Today: snapshot view of your daily iCal agenda
<http://secondgearsoftware.com/today/>
-
_______________________________________________
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
--
Nick Peelman
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