Re: Does a flat package allow a relocatable installation?
Re: Does a flat package allow a relocatable installation?
- Subject: Re: Does a flat package allow a relocatable installation?
- From: Stephane Sudre <email@hidden>
- Date: Thu, 25 Apr 2013 11:06:04 +0200
On Thu, Apr 25, 2013 at 1:03 AM, Andrew Keller <email@hidden> wrote:
> On Apr 24, 2013, at 1:13 PM, Jim Dodd wrote:
>
>> We have finally switched from using PackageMaker and creating a bundled package installer to using Stephane Sudre's Package program to create a flat package installer. I have chosen Relocatable in the Settings for the package but when we get to the list of volumes, I can only choose the volume. Previously, with bundled package installers created with PackageMaker, I could select the volume and a Choose Folder button would appear to allow us to change where our application is installed (from the /Applications default).
>>
>> Is there something else I must select in Packages or is choosing a different folder on a volume no longer allowed with a flat package installer?
>
> I do not have experience with Packages (we create our installer manually), however I do know modern flat packages can install onto other volumes, and you can activate the "relocate" feature, which allows files (bundles, technically) to be installed during an upgrade install to follow to where a user may have previously moved them. So, you could install an app, move the app manually, and when you reinstall, the new copy would overwrite the copy you moved, rather than putting the new one in the original location.
>
> I have not seen any documentation for the ability to install apps to a specific folder, although I may have just missed it.
The relocation feature of the original post refers to the ability to
install the entire payload in a specific folder.
By default, the payload of a package can be installed on any volume at
the relative default location described in the PackageInfo file (the
install-location key). it's usually / (but it can be set to
/Applications).
With flat packages and distributions, you can only restrict the
installation to the startup volume when the package is integrated into
a distribution (I personally find this limitative but that's how it
is).
Then you have the relocatable option in the PackageInfo file of a raw
package which indicates that the entire payload can be installed at a
relative custom location on the selected target volume.
This works fine for flat package. But with distribution packages, this
won't let you see the popup menu on the right of the choice/package in
the "Installation Type" pane. For that, it requires to set the
customLocation attribute of the corresponding choice. And it's not
supported by Packages at this time.
And finally, with distributions, you have the ability define the
domains where the entire payload can be installed.
_______________________________________________
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