February 2013 - Installer-dev

Re: Gatekeeper and downloading packages
by Stephane Sudre 20 Feb '13

20 Feb '13

On Wed, Feb 20, 2013 at 8:00 AM, Natalia Antonova <natalya.a.antonova(a)gmail.com> wrote: > Hello > > My Distribution refers to component packages that are downloaded by a plugin > later in the installation. Though both distribution (mpkg) and component > packages are correctly signed, Gatekeeper assessment fails. I suspect > Gatekeeper evaluates all the pieces right after user double clicks on the > package, and if some part is not signed or is not there yet (my case) - the > assessment fails.I am 95% sure this is a limitation we have to leave with, > but perhaps someone knows a workaround (except creating an own installer)? Yes, this is a limitation. Even when the certificates are the same for the distribution and remote packages, it fails. I haven't found a way to make it work either. > Another question is what is the best place to store component packages > downloaded by my plugin? > I noticed that if Distribution contains http URL to packages, Installer > keeps them in /tmp folder. But wouldn't it better to store them in > "~/Downloads"? But I am not sure how to set this in Distribution file (and > if it's really possible). Not possible as far as I know. You can only provide the remote URL not a local download folder. I assume the package is downloaded in the same kind of /tmp "sandboxed" location used to expand the flat packages. _______________________________________________ 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: How to quit running app before installer replaces it?
by Stephane Sudre 20 Feb '13

20 Feb '13

On Wed, Feb 20, 2013 at 1:12 AM, Sean McBride <sean(a)rogue-research.com> wrote: > On Tue, 19 Feb 2013 15:53:34 -0800, Stephane Sudre said: > >>One of the possible best practices is probably to use the 'must-close' >>options of a distribution script. >> >>https://developer.apple.com/library/mac/#documentation/DeveloperTools/ >>Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.html >> >>Caveat: it's not supported by all OS versions that support >>distributions. I haven't checked which versions are supported yet. This option/requirement is not supported at this time by the Packages application. So this would require to edit the distribution script (file) once you have built it (if it's a bundle distribution, you just need to edit the file, if it's a flat distribution, you would need to expand it and then flatten it) As mentioned, this option/requirement has been added somehow recently to the distribution script features so it probably requires Mac OS X 10.6.6 or later. I thought the minimum OS version was listed in the official documentation but the "Availability" info is missing. _______________________________________________ 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

Gatekeeper and downloading packages
by Natalia Antonova 20 Feb '13

20 Feb '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: How to quit running app before installer replaces it?
by Sean McBride 20 Feb '13

20 Feb '13

On Tue, 19 Feb 2013 15:53:34 -0800, Stephane Sudre said: >One of the possible best practices is probably to use the 'must-close' >options of a distribution script. > >https://developer.apple.com/library/mac/#documentation/DeveloperTools/ >Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.html > >Caveat: it's not supported by all OS versions that support >distributions. I haven't checked which versions are supported yet. Stéphane, That looks most promising, thanks! Now, I just need to figure out what a 'distribution script' is. :) Actually, I am using your Packages.app, does it have some facility for this 'must-close' thing? Thanks, -- ____________________________________________________________ Sean McBride, B. Eng sean(a)rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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: How to quit running app before installer replaces it?
by Stephane Sudre 19 Feb '13

19 Feb '13

On Tue, Feb 19, 2013 at 9:16 AM, Sean McBride <sean(a)rogue-research.com> wrote: > Hi all, > > Just joined this list, please be gentle... :) > > We recently got a customer crash report that we figured out was due to version x of our app being run while the user ran the installer to install version y. Since the process was still running, it eventually tried to open one of its nib files (which changed from x to y) and crashed due to the mismatch. > > So: how can/should I check if my app is already running, and warn the user before installing? > > I've found this asked in the archives: > <http://lists.apple.com/archives/installer-dev/2008/Nov/msg00054.html> > <http://lists.apple.com/archives/installer-dev/2006/Jan/msg00036.html> > > But they are years old... what is current best practice? One of the possible best practices is probably to use the 'must-close' options of a distribution script. https://developer.apple.com/library/mac/#documentation/DeveloperTools/Refer… Caveat: it's not supported by all OS versions that support distributions. I haven't checked which versions are supported yet. _______________________________________________ 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: InstallerSections.plist - Place an installer plugin behind thesummary
by Stephane Sudre 19 Feb '13

19 Feb '13

On Tue, Feb 19, 2013 at 8:30 AM, Paul Grathwohl <p.grathwohl(a)steinberg.de> wrote: > Hello Stephane, > > thanks for giving the reason, why it's not possible. > The idea was to display some information to the user, after the installation > was done (like where he could look for updates when he installed from a > potentially old dvd-medium). Showing that information before the > installation seems too early, and showing it before the user got the message > that the medium-installation succeeded also seems not optimal (but might be > ok...). You can use a custom (and localized) Summary text. So this may fit your needs. RTF(d), TXT or HTML. > Another thing I maybe need in the future is to have an "always up to date" > installer and I was thinking how to do it with the standard installer. A > "self-made" approach could be to have an installer plugin that downloads and > installs the latest patch directly after the installation of the version > from the medium. But maybe that's a bad idea (starting an installation at > the end of another installation is probably hard to make intuitive for the > user). With distributions, it's possible to have a package be hosted on a http server and just have a reference to it in the distribution script. _______________________________________________ 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: How to quit running app before installer replaces it?
by Beatrix Willius 19 Feb '13

19 Feb '13

Hi Sean, I'm a newbie myself in regard to installers. But I've had a similar issue like yours. You need to add a preflight script. Here is the script that I use #!/bin/sh thepid=`ps ux | awk '/Mail Archiver Scheduler/ && !/awk/ {print $2}'` if [ $thepid ]; then kill $thepid; else echo 'no schedule set'; fi This is a very simple script. However, for me it works. You can't warn the user AFAIK. On 19.02.2013, at 18:16, Sean McBride <sean(a)rogue-research.com> wrote: > Just joined this list, please be gentle... :) > > We recently got a customer crash report that we figured out was due to version x of our app being run while the user ran the installer to install version y. Since the process was still running, it eventually tried to open one of its nib files (which changed from x to y) and crashed due to the mismatch. > > So: how can/should I check if my app is already running, and warn the user before installing? > > I've found this asked in the archives: > <http://lists.apple.com/archives/installer-dev/2008/Nov/msg00054.html> > <http://lists.apple.com/archives/installer-dev/2006/Jan/msg00036.html> Mit freundlichen Grüßen/Regards Trixi Willius http://www.mothsoftware.com Mail Archiver X: The email archiving solution for professionals _______________________________________________ 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

How to quit running app before installer replaces it?
by Sean McBride 19 Feb '13

19 Feb '13

Hi all, Just joined this list, please be gentle... :) We recently got a customer crash report that we figured out was due to version x of our app being run while the user ran the installer to install version y. Since the process was still running, it eventually tried to open one of its nib files (which changed from x to y) and crashed due to the mismatch. So: how can/should I check if my app is already running, and warn the user before installing? I've found this asked in the archives: <http://lists.apple.com/archives/installer-dev/2008/Nov/msg00054.html> <http://lists.apple.com/archives/installer-dev/2006/Jan/msg00036.html> But they are years old... what is current best practice? Thanks, -- ____________________________________________________________ Sean McBride, B. Eng sean(a)rogue-research.com Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ 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: InstallerSections.plist - Place an installer plugin behind thesummary
by Paul Grathwohl 19 Feb '13

19 Feb '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 From: Stephane Sudre <dev.iceberg(a)gmail.com>

1 0

Re: InstallerSections.plist - Place an installer plugin behind the summary
by Stephane Sudre 19 Feb '13

19 Feb '13

On Tue, Feb 19, 2013 at 3:55 PM, Paul Grathwohl <p.grathwohl(a)steinberg.de> wrote: > Hello, > > is it possible to place an installer plugin behind the "Summary" section of > the installer (i.e. at the very end)? > If I try to do that in the InstallerSections.plist, my plugin will > nevertheless appear directly after the installation step and _before_ the > summary. > > I tried with this InstallerSections.plist: > > <key>SectionOrder</key> > <array> > <string>Introduction</string> > <string>ReadMe</string> > <string>License</string> > <string>Target</string> > <string>PackageSelection</string> > <string>Install</string> > <string>FinishUp</string> > <string>MyPlugin.bundle</string> > </array> > > The behaviour I saw is the same for Flat and Bundle Packages. I tested with > 10.7.5. Since the Summary step can invite the user to logout, shutdown or restart the computer, it could make no sense to have a button with such an action and then not perform this action. Maybe there's another solution for what you are trying to achieve. So what are you trying to do? _______________________________________________ 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