Re: Effects of "allow relocation" in Components tab
Re: Effects of "allow relocation" in Components tab
- Subject: Re: Effects of "allow relocation" in Components tab
- From: Stéphane Sudre <email@hidden>
- Date: Mon, 3 Mar 2008 23:42:19 +0100
On Mar 3, 2008, at 6:59 PM, Rick Hoge wrote:
So my question: when would it actually be a good idea to check
this box?
When you build the package for deployment to your customer. That
being said, this option may be re-enabled in your back with the
current version of PackageMaker.
And another question: what is the logic followed by the Installer
when it finds multiple versions of an app in deciding which
location (or locations?) to upgrade if it finds them?
As far as I know, the first location that matches will be selected.
Apparently, you can specify an additional criteria based on the
minimum and maximum version of the component to filter out some
locations. A long time ago, IIRC, you could also state that the user
would be allowed to select the best location.
is this documented somewhere?
I really appreciate your sense of humor. Considering that the
PackageMaker 3 documentation is mostly made of 4 screenshots
surrounded by text (and that you have to launch the Xcode just to
access it), that the Software Delivery Guide refers to the Tiger
version of PackageMaker, that the Distribution Definition Reference
documentation is incomplete, that the package format lacks a proper
documentation (forget about overwrite-permissions), that the
Installer Javascript Reference is missing good examples, it would be
surprising if something as esoteric as relocators would be documented.
To get information about relocators, you would need to look into old
OS releases (Panther, Jaguar) and release notes. Documentation is a
foreign word when it comes to Installation.
_______________________________________________
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