Re: silent sub-launch of dependent package during install?
Re: silent sub-launch of dependent package during install?
- Subject: Re: silent sub-launch of dependent package during install?
- From: "Bryan S. Lee" <email@hidden>
- Date: Tue, 01 Jul 2008 22:22:02 -0400
- Thread-topic: silent sub-launch of dependent package during install?
Title: Re: silent sub-launch of dependent package during install?
Running an installer from within a postscript should work fine. I’m currently doing it with MS Office (among other products) without repacking MS’s package.
Have the main installer putting the secondary installer in a /tmp location and then engage the second installer using the following command in the postscript.
installer -pkg /private/tmp/office/office2008/Office\ Installer.mpkg -target LocalSystem
Agree with Bill, that it won’t give any feedback in the installer (and that is VERY sub-wonderful), but it should function fine.
--
Bryan S. Lee
Information Resource Consultant II
Computer Support Services
Clemson Computing and Information Technology
Clemson University
email@hidden
ACHDS 10.4, MCP NTS/NTW
From: Bill Coderre <email@hidden>
Date: Tue, 1 Jul 2008 15:50:26 -0400
To: Ryan McGann <email@hidden>
Cc: <email@hidden>
Subject: Re: silent sub-launch of dependent package during install?
On Jul 1, 2008, at 9:57 AM, Ryan McGann wrote:
>> What I want to do is just launch a silent install of this package
>> (using
>> "installer") in my postinstall/postupgrade scripts. I'll embed the
>> dependent package in my primary package Resources, and just launch it
>> from the script.
> I'll let somebody else confirm, but I don't believe running two
> instances of "installer" at the same time is supported (or more
> appropriately, two instances of the underlying install package
> mechanism, "runner" or whatever it is in 10.5, is not supported).
> That is why if you double click 2 .pkg's in the Finder,
> Installer.app waits until one package is finished installing before
> going on to the next. It might work, but I wouldn't count on it.
I won't swear it won't work, but I am pretty sure it won't. Also, the
lack of progress bar is sub-wonderful.
> Why don't you want to create a metapackage? It's not that hard
> really--unless you need to support 10.3 through 10.5.
10.5 is very happy to run 10.3 mpkgs.
You can set up the entire thing as a 10.3 style mpkg, where all the
packages have InstallationChecks and VolumeChecks, and each mpkg has a
listing of its subpackages, marked "required" or "optional" etc.
OR you can have the 10.3 stuff AND a 10.4 distribution. That's what
iLife did in 06. (Distributions have extra powers and launch faster.)
_______________________________________________
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
_______________________________________________
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