April 2013 - Installer-dev - lists.apple.com

Re: Does a flat package allow a relocatable installation?
by Andrew Keller 25 Apr '13

25 Apr '13

On Apr 25, 2013, at 5:06 AM, Stephane Sudre wrote: > On Thu, Apr 25, 2013 at 1:03 AM, Andrew Keller <andrew(a)kellerfarm.com> 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. Yes, of course. I attempted to imply that, but looking at my words again, I see the confusion... Thanks keeping it clear. > 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. Well, hey - look at that. That's awesome. Thanks, Andrew Keller _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Does a flat package allow a relocatable installation?
by Stephane Sudre 25 Apr '13

25 Apr '13

On Thu, Apr 25, 2013 at 1:03 AM, Andrew Keller <andrew(a)kellerfarm.com> 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 (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Does a flat package allow a relocatable installation?
by Andrew Keller 24 Apr '13

24 Apr '13

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. - Andrew Keller _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Does a flat package allow a relocatable installation?
by Jim Dodd 24 Apr '13

24 Apr '13

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? Thank you, Jim Dodd Onset Computer Corporation _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Install Location
by koko 23 Apr '13

23 Apr '13

In today's Mac environment am I allowed to install to: / Users / Home / Library / Containers / bundle id / Data / Library / Application Support / < my paths > -koko _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Version string patterns
by Andrew Keller 15 Apr '13

15 Apr '13

Hello all, I would like to fully understand the patterns and best practices used by version strings in OS X apps. I've been having trouble finding any hard documentation on exactly what patterns to follow, so I would like to bounce what I think I've learned off the list and see how much I got right. BuildVersion: The build number on your CI server? Does anything in OS X use this? Are there any restrictions? CFBundleShortVersionString: Human readable. Used when displaying versions. Typically something like 1.2.3d5. Integers are unlimited, stage code is usually 'd', 'a', 'b', or 'f' (or 'fc'?). Drop the stage code and the build number when on a real release. CFBundleVersion: Machine comparable. Used by Installer.app when determining if copy X is newer than copy Y of an app. For KEXTs, use the same pattern as CFBundleShortVersionString, except that the bug version cannot be greater than 255. No specific pattern to follow for other types of products? SourceVersion: The commit ID in the source repository? Does anything in OS X use this? Are there any restrictions? Also, what's the difference between Info.plist and version.plist? Thanks, Andrew Keller _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Selected option check
by Stephane Sudre 05 Apr '13

05 Apr '13

I'm not sure to understand the description. • If no choices are selected in the customize screen and if no invisible choices are selected, the "Install" button should be disabled. • If you want the installations not to be possible if any of the choices (*) is unselected by the user, this looks like you don't need a customize mode and should only display the standard mode. • If you want the installations not to be selected if any of the choices is unselected because of a JavaScript requirements, you may be able to achieve this by checking for this JavaScript requirement for all the choices (depending on the relative state of other choices may be more complex to implement). But you could be describing another case. * This assumes that there are no selected invisible choices. On Fri, Apr 5, 2013 at 1:29 PM, Philip Petev <madmax2000(a)gmail.com> wrote: > Hi there, > I want to implement a check in one of my packages, which should prevent the > installation to continue, when any of the options in the customize screen > has been selected or not, but I don't know what scripting should be used in > this case. Can you help me? _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Selected option check
by Philip Petev 05 Apr '13

05 Apr '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0