Re: Never upgrade. Always install
Re: Never upgrade. Always install
- Subject: Re: Never upgrade. Always install
- From: Jim Dodd <email@hidden>
- Date: Wed, 2 Sep 2009 12:10:43 -0700 (PDT)
Also, if you are not creating a flat package but have a PKG file that you can look inside, look for a TokenDefinitions.plist in YourApp.pkg/Contents/Resources and open the TokenDefinitions.plist and drill down through pkmk-token-xx/Item x/searchPlugin to see what the Installer will be using as a search algorithm. You can set that to just look for your application in a specific place as we have done.
Regards,
Jim Dodd
Onset Computer Corporation
----- Original Message ----
> From: Andrew Peckover <email@hidden>
> To: Justin Williams <email@hidden>
> Cc: email@hidden
> Sent: Wednesday, September 2, 2009 2:51:02 PM
> Subject: Re: Never upgrade. Always install
>
> If Allow Relocation is enabled, then it looks for the .app on your computer, and
> will put it elsewhere (not where you might expect) if it finds it. For example,
> if you're testing your install on a computer that you use for development and
> you've got the app in a few different places. A typical user wouldn't
> experience this, since they would only have the .app in one place.
>
> But - note: If you uncheck the Allow Relocation box, you can't just forget
> about this setting.... Because it often becomes automatically checked when you
> modify your package..
>
> Andrew
>
> ----- Original Message ----- From: "Justin Williams"
>
> To: "Andrew Peckover"
> Cc:
> Sent: Wednesday, September 02, 2009 11:07 AM
> Subject: Re: Never upgrade. Always install
>
>
> > Hi,
> >
> > The Allow Relocation checkbox is enabled, but in my testing, I'm not channging
> the default setting of installing to /Applications. Would disabling the Allow
> Relocation checkbox make a difference?
> >
> > - j
> >
> >
> > On Sep 2, 2009, at 11:28 AM, Andrew Peckover wrote:
> >
> >> Hello Justin,
> >>
> >>
> >> 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"
>
> >> >
> >> To:
> >> 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
> >>>> Williamswrote:
> >>>>> 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
> >>>>>
> >>>>> -
> >>>>> _______________________________________________
> >>>>> 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
_______________________________________________
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