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

Re: productbuild(1) distribution definition
by Dave Barker-Plummer 30 Apr '13

30 Apr '13

Yes. Indeed I was looking for that flag. Many thanks. -- Dave On Apr 29, 2013, at 11:07 PM, John Gee <john.lists(a)adi.co.nz> wrote: > On 26/04/2013, at 10:09, Dave Barker-Plummer wrote: > >> The productbuild(1) command line tool for building installers allows one to specify files to be included in the installer (readme, license and the like) within the distribution.xml file. >> >> I can get this to work by specifying an absolute path name for these keys, but all my attempts to use a relative path name have been unsuccessful. Has anyone been able to use a relative path here, and to work out how the path is interpreted (relative to what)? >> >> -- Dave >> >> Documentation for the xml format here: >> https://developer.apple.com/library/mac/#documentation/DeveloperTools/Refer… > > > You are probably looking for: productbuild --resources rsrc-dir > > I stick a welcome, readme, license, and background file directly into a folder I called Resources. I use just the filename in the xml, and invoke the build with: > productbuild --distribution distribution.xml --resources Resources ... > > -- > John Gee, ADInstruments > Programmers live in interesting times... > _______________________________________________ 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: productbuild(1) distribution definition
by John Gee 30 Apr '13

30 Apr '13

On 26/04/2013, at 10:09, Dave Barker-Plummer wrote: > The productbuild(1) command line tool for building installers allows one to specify files to be included in the installer (readme, license and the like) within the distribution.xml file. > > I can get this to work by specifying an absolute path name for these keys, but all my attempts to use a relative path name have been unsuccessful. Has anyone been able to use a relative path here, and to work out how the path is interpreted (relative to what)? > > -- Dave > > Documentation for the xml format here: > https://developer.apple.com/library/mac/#documentation/DeveloperTools/Refer… You are probably looking for: productbuild --resources rsrc-dir I stick a welcome, readme, license, and background file directly into a folder I called Resources. I use just the filename in the xml, and invoke the build with: productbuild --distribution distribution.xml --resources Resources ... -- John Gee, ADInstruments Programmers live in interesting times... _______________________________________________ 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: productbuild(1) distribution definition
by Bill Coderre 29 Apr '13

29 Apr '13

Feel free to file a bug. Can't promise instant satisfaction, but gratitude for your time, yes. On Apr 26, 2013, at 5:57 PM, Dave Barker-Plummer <dbp(a)stanford.edu> wrote: > In case anyone is playing along at home. I solved my problem by creating a distribution file template with dummy markers in it, and preprocess this file using sed(1) to replace the markers by actual absolute paths, to produce the real distribution file used by productbuild(1). This assuages productbuild's requirement for absolute paths, and allows me to automate the build using ant, assuming nothing about the true absolute path to the requisite files. > > Its ugly, but it works. > > -- Dave > > On Apr 26, 2013, at 6:52 AM, Greg Neagle <Greg.Neagle(a)disneyanimation.com> wrote: > >> I have no information on how productbuild creates its packages. I can only point to actual existing packages and their Distribution files. I suspect that productbuild does not support the full range of what is possible to do in a package or a Distribution file, but rather, implements a generally useful subset. >> >> So I guess I have no useful information for you. Sorry! >> >> -Greg >> >> On Apr 26, 2013, at 6:34 AM, Dave Barker-Plummer <dbp(a)stanford.edu> wrote: >> >>> I am not sure why I should be able to infer the required layout of the files on disk from the layout of the files in the resulting package. The whole point of productbuild is to collect together files on disk and then put them in the right place within the package. What I am asking is how to specify the original location of the files. >>> >>> If I interpret your suggestion correctly, you're saying that if I create a Resources directory on the package search path, and place a file "readme" in that directory, then I can reference the file as Resources/readme (or possibly readme) in the distribution,xml file. Regrettably, neither of these work. The resulting package does not contain the readme file. >>> >>> -- Dave >>> >>> On Apr 25, 2013, at 7:27 PM, Greg Neagle <greg.neagle(a)disneyanimation.com> wrote: >>> >>>> Oh -- you mean relative file references inside the XML distribution file. I misunderstood your original question. >>>> >>>> You can peek inside an Apple package for clues. >>>> >>>> For example, I expand the iPhoto 9.4.3 update pkg: >>>> >>>> % pkgutil --expand /Volumes/iPhoto\ 9.4.3/iPhoto9.4.3Update.pkg iPhoto_update >>>> % cd iPhoto_update/ >>>> gneagle@foo:iPhoto_update % ls >>>> Distribution Resources iPhoto9.4.3ContentUpdate.pkg iPhoto9.4.3Update.pkg >>>> >>>> There are two pkgs in the same directory as the Distribution file. The corresponding bits in the Distribution file: >>>> >>>> <pkg-ref id="iPhotoUpdate" auth="Root" active="LogicalAnd3(my.target.mountpoint)">#iPhoto9.4.3Update.pkg</pkg-ref> >>>> <pkg-ref id="iPhotoContentUpdate" auth="Root" active="LogicalAnd3(my.target.mountpoint)">#iPhoto9.4.3ContentUpdate.pkg</pkg-ref> >>>> >>>> Those are relative paths. I've seen distribution-style packages refer to component pkgs _outside_ of the distribution pkg; this is typically on DVD media or on a disk image, and looks something like this: >>>> >>>> <pkg-ref id="foo" auth="Root">../Packages/foo.pkg</pkg-ref> >>>> >>>> This probably doesn't really help you, though. What is it you are trying to accomplish? For self-contained flat packages (especially if they are signed) you just want to use the default behavior described in the document you linked to: >>>> >>>> "Content >>>> Required. A URL specifying the location of the installation package to which this element refers. Typically, you specify a simple filename and productbuild adjusts the URL as needed when the product archive is created." >>>> >>>> -Greg >>>> >>>> >>>> On Apr 25, 2013, at 5:13 PM, Dave Barker-Plummer <dbp(a)stanford.edu> wrote: >>>> >>>>> I should probably have mentioned the places that do not work: >>>>> >>>>> - the working directory when productbuild is run >>>>> - the directory containing the distribution file >>>>> - the directories on the package-path >>>>> >>>>> -- Dave >>>>> >>>>> On Apr 25, 2013, at 3:17 PM, Greg Neagle <Greg.Neagle(a)disneyanimation.com> wrote: >>>>> >>>>>> Most UNIX tools interpret relative paths as relative to the current working directory. >>>>>> >>>>>> I'd be surprised if productbuild doesn't do the same. If it doesn't, it's a bug and should be reported. >>>>>> >>>>>> A big exception is /usr/bin/defaults, which does not "do" relative paths. But that is because `default` really operates on preference domains, and not files. >>>>>> >>>>>> -Greg >>>>>> >>>>>> On Apr 25, 2013, at 3:09 PM, Dave Barker-Plummer <dbp(a)stanford.edu> wrote: >>>>>> >>>>>>> The productbuild(1) command line tool for building installers allows one to specify files to be included in the installer (readme, license and the like) within the distribution.xml file. >>>>>>> >>>>>>> I can get this to work by specifying an absolute path name for these keys, but all my attempts to use a relative path name have been unsuccessful. Has anyone been able to use a relative path here, and to work out how the path is interpreted (relative to what)? >>>>>>> >>>>>>> -- Dave >>>>>>> >>>>>>> Documentation for the xml format here: >>>>>>> https://developer.apple.com/library/mac/#documentation/DeveloperTools/Refer… >>>>>>> _______________________________________________ >>>>>>> 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/greg.neagle%40disneya… >>>>>>> >>>>>>> This email sent to greg.neagle(a)disneyanimation.com >>>>>> >>>>> >>>> >>> >> > > > _______________________________________________ > 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/bc%40apple.com > > This email sent to bc(a)apple.com _______________________________________________ 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: Using plugins with PackageMaker
by Don Montalvo 29 Apr '13

29 Apr '13

Or perhaps look at it's successor...Packages. :) http://s.sudre.free.fr/Software/Packages/about.html Don Sanjay Rao <email@hidden> wrote: > Hi, > > Similar requirement we had in past for our project. We choose to use "Iceberg" over packagemaker. Its very easy to understand and use. > http://s.sudre.free.fr/Software/Iceberg.html > > Regards, > Sanjay Rao _______________________________________________ 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: Using plugins with PackageMaker
by Sanjay Rao 29 Apr '13

29 Apr '13

Hi, http://s.sudre.free.fr/Software/Iceberg.html Regards, Sanjay Rao On 4/29/2013 1:54 AM, Stephane Sudre wrote: On Sat, Apr 27, 2013 at 11:22 PM, Scott Grosch <scott.grosch(a)gmail.com> wrote: Have a few questions about the proper way to use a plugin with PackageMaker. I have the plugin displaying correctly at this point where I want it. - After asking the user for the answers to questions, how do I pass those answers to the post install script that is run? You can either write them on disk or spawn a process from the plugin to answer the requests from the script. - Is there a way to get notified if the user cancels the install? For example, if I take some actions right in the pane, how do I know to undo them? There's no way to do this AFAIK. So it's good idea to only modify the file system or the settings of an application with the payload and with the pre/post installation scripts. - What is the proper way to cancel an install? For example, if a required action my pane takes fails, how do I stop the install properly with a message to the user? If it fails during an action launched when you move to the next pane, what you could do is launch the action from: - (BOOL)shouldExitPane:(InstallerSectionDirection)dir; So that you can display a standard alert and prevent the user from moving to the next pas. Docs on PackageMaker seem pretty hard to come by. Especially since hitting Help inside of PackageMaker itself doesn't do anything :( -- Sanjay Rao Digital Media Group, Interra Systems srao(a)interrasystems.com http://www.interrasystems.com _______________________________________________ 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 Similar requirement we had in past for our project. We choose to use "Iceberg" over packagemaker. Its very easy to understand and use.

1 0

Re: Using plugins with PackageMaker
by Stephane Sudre 28 Apr '13

28 Apr '13

On Sat, Apr 27, 2013 at 11:22 PM, Scott Grosch <scott.grosch(a)gmail.com> wrote: > Have a few questions about the proper way to use a plugin with PackageMaker. I have the plugin displaying correctly at this point where I want it. > > - After asking the user for the answers to questions, how do I pass those answers to the post install script that is run? You can either write them on disk or spawn a process from the plugin to answer the requests from the script. > - Is there a way to get notified if the user cancels the install? For example, if I take some actions right in the pane, how do I know to undo them? There's no way to do this AFAIK. So it's good idea to only modify the file system or the settings of an application with the payload and with the pre/post installation scripts. > - What is the proper way to cancel an install? For example, if a required action my pane takes fails, how do I stop the install properly with a message to the user? If it fails during an action launched when you move to the next pane, what you could do is launch the action from: - (BOOL)shouldExitPane:(InstallerSectionDirection)dir; So that you can display a standard alert and prevent the user from moving to the next pas. > Docs on PackageMaker seem pretty hard to come by. Especially since hitting Help inside of PackageMaker itself doesn't do anything :( -- Packaging Resources - http://s.sudre.free.fr/Packaging.html _______________________________________________ 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

Using plugins with PackageMaker
by Scott Grosch 27 Apr '13

27 Apr '13

Have a few questions about the proper way to use a plugin with PackageMaker. I have the plugin displaying correctly at this point where I want it. - After asking the user for the answers to questions, how do I pass those answers to the post install script that is run? - Is there a way to get notified if the user cancels the install? For example, if I take some actions right in the pane, how do I know to undo them? - What is the proper way to cancel an install? For example, if a required action my pane takes fails, how do I stop the install properly with a message to the user? Docs on PackageMaker seem pretty hard to come by. Especially since hitting Help inside of PackageMaker itself doesn't do anything :( _______________________________________________ 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: Distribution of library via Mac App Store
by Natalia Antonova 27 Apr '13

27 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

Re: productbuild(1) distribution definition
by Dave Barker-Plummer 27 Apr '13

27 Apr '13

In case anyone is playing along at home. I solved my problem by creating a distribution file template with dummy markers in it, and preprocess this file using sed(1) to replace the markers by actual absolute paths, to produce the real distribution file used by productbuild(1). This assuages productbuild's requirement for absolute paths, and allows me to automate the build using ant, assuming nothing about the true absolute path to the requisite files. Its ugly, but it works. -- Dave On Apr 26, 2013, at 6:52 AM, Greg Neagle <Greg.Neagle(a)disneyanimation.com> wrote: > I have no information on how productbuild creates its packages. I can only point to actual existing packages and their Distribution files. I suspect that productbuild does not support the full range of what is possible to do in a package or a Distribution file, but rather, implements a generally useful subset. > > So I guess I have no useful information for you. Sorry! > > -Greg > > On Apr 26, 2013, at 6:34 AM, Dave Barker-Plummer <dbp(a)stanford.edu> wrote: > >> I am not sure why I should be able to infer the required layout of the files on disk from the layout of the files in the resulting package. The whole point of productbuild is to collect together files on disk and then put them in the right place within the package. What I am asking is how to specify the original location of the files. >> >> If I interpret your suggestion correctly, you're saying that if I create a Resources directory on the package search path, and place a file "readme" in that directory, then I can reference the file as Resources/readme (or possibly readme) in the distribution,xml file. Regrettably, neither of these work. The resulting package does not contain the readme file. >> >> -- Dave >> >> On Apr 25, 2013, at 7:27 PM, Greg Neagle <greg.neagle(a)disneyanimation.com> wrote: >> >>> Oh -- you mean relative file references inside the XML distribution file. I misunderstood your original question. >>> >>> You can peek inside an Apple package for clues. >>> >>> For example, I expand the iPhoto 9.4.3 update pkg: >>> >>> % pkgutil --expand /Volumes/iPhoto\ 9.4.3/iPhoto9.4.3Update.pkg iPhoto_update >>> % cd iPhoto_update/ >>> gneagle@foo:iPhoto_update % ls >>> Distribution Resources iPhoto9.4.3ContentUpdate.pkg iPhoto9.4.3Update.pkg >>> >>> There are two pkgs in the same directory as the Distribution file. The corresponding bits in the Distribution file: >>> >>> <pkg-ref id="iPhotoUpdate" auth="Root" active="LogicalAnd3(my.target.mountpoint)">#iPhoto9.4.3Update.pkg</pkg-ref> >>> <pkg-ref id="iPhotoContentUpdate" auth="Root" active="LogicalAnd3(my.target.mountpoint)">#iPhoto9.4.3ContentUpdate.pkg</pkg-ref> >>> >>> Those are relative paths. I've seen distribution-style packages refer to component pkgs _outside_ of the distribution pkg; this is typically on DVD media or on a disk image, and looks something like this: >>> >>> <pkg-ref id="foo" auth="Root">../Packages/foo.pkg</pkg-ref> >>> >>> This probably doesn't really help you, though. What is it you are trying to accomplish? For self-contained flat packages (especially if they are signed) you just want to use the default behavior described in the document you linked to: >>> >>> "Content >>> Required. A URL specifying the location of the installation package to which this element refers. Typically, you specify a simple filename and productbuild adjusts the URL as needed when the product archive is created." >>> >>> -Greg >>> >>> >>> On Apr 25, 2013, at 5:13 PM, Dave Barker-Plummer <dbp(a)stanford.edu> wrote: >>> >>>> I should probably have mentioned the places that do not work: >>>> >>>> - the working directory when productbuild is run >>>> - the directory containing the distribution file >>>> - the directories on the package-path >>>> >>>> -- Dave >>>> >>>> On Apr 25, 2013, at 3:17 PM, Greg Neagle <Greg.Neagle(a)disneyanimation.com> wrote: >>>> >>>>> Most UNIX tools interpret relative paths as relative to the current working directory. >>>>> >>>>> I'd be surprised if productbuild doesn't do the same. If it doesn't, it's a bug and should be reported. >>>>> >>>>> A big exception is /usr/bin/defaults, which does not "do" relative paths. But that is because `default` really operates on preference domains, and not files. >>>>> >>>>> -Greg >>>>> >>>>> On Apr 25, 2013, at 3:09 PM, Dave Barker-Plummer <dbp(a)stanford.edu> wrote: >>>>> >>>>>> The productbuild(1) command line tool for building installers allows one to specify files to be included in the installer (readme, license and the like) within the distribution.xml file. >>>>>> >>>>>> I can get this to work by specifying an absolute path name for these keys, but all my attempts to use a relative path name have been unsuccessful. Has anyone been able to use a relative path here, and to work out how the path is interpreted (relative to what)? >>>>>> >>>>>> -- Dave >>>>>> >>>>>> Documentation for the xml format here: >>>>>> https://developer.apple.com/library/mac/#documentation/DeveloperTools/Refer… >>>>>> _______________________________________________ >>>>>> 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/greg.neagle%40disneya… >>>>>> >>>>>> This email sent to greg.neagle(a)disneyanimation.com >>>>> >>>> >>> >> > _______________________________________________ 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: Distribution of library via Mac App Store
by Andrew Keller 26 Apr '13

26 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