Re: Option to execute a command?
Re: Option to execute a command?
- Subject: Re: Option to execute a command?
- From: Allister Banks <email@hidden>
- Date: Thu, 31 Mar 2011 12:03:21 -0400
| Not that this needs repeating in such esteemed company, but:
Allister On Mar 31, 2011, at 11:06 AM, Karl Kuehn wrote: On Mar 31, 2011, at 1:03 AM, Stephane Sudre wrote: On Wed, Mar 30, 2011 at 9:11 PM, Karl Kuehn <email@hidden> wrote:
One thing that is missing in this conversation is that you could be running this installer targeted at a volume other than the boot volume. It is really simple to catch this case, so we should always be pushing people to do this when they write installer scripts. More inline:
Another solution is to only allow the package to be installed on the startup disk.
That restriction only takes effect for GUI installs. Command line installs blow right past it without even a warning in a log. So this would not help you on InstaDMG, System Image Utility, or weird cases with ARD. And given the number of installs out there done with InstaDMG or SIU, and the usually trivial nature of making installer scripts work in those environments, it is bad form to ignore them.
|
_______________________________________________
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