Re: installer scripts launch the wrong browser!?
Re: installer scripts launch the wrong browser!?
- Subject: Re: installer scripts launch the wrong browser!?
- From: Greg Neagle <email@hidden>
- Date: Wed, 16 Nov 2011 08:42:31 -0800
I hope you are joking, Stephane!
The most common usage of command-line installs is an install via an automation tool: ARD, Munki, Casper, Absolute Manage, InstaDMG, System Image Utility, DeployStudio, etc...
In all of these cases, NO user interaction is welcome.
Going back to the original problem:
The right approach in most cases is to NOT put this sort of thing in the install package at all, but rather have the installed software itself open the browser when it is first used. This solves several problems:
1) The software is running in the user's context, so it will open the user's preferred browser.
2) If there is more than one user for the machine, each user will see the "getting started info" when they first use the software.
3) If the software is installed in an automated fashion, whoever uses it after it is installed will see the "getting started info" when they first use the software.
-Greg
On Nov 16, 2011, at 2:30 AM, Stephane Sudre wrote:
> Maybe checking if lynx is installed and using it when
> COMMAND_LINE_INSTALL is set would be nice.
>
> On Wed, Nov 16, 2011 at 1:06 AM, Greg Neagle
> <email@hidden> wrote:
>> If there _is_ a "sitting at the screen" user. Make sure your script fails gracefully if no-one is logged in.
>>
>> Better yet, if COMMAND_LINE_INSTALL is set, skip this entirely.
>>
>> -Greg
>>
>> On Nov 15, 2011, at 3:57 PM, Bill Coderre wrote:
>>
>>> Preflight and Postflight scripts run as root.
>>>
>>> Investigate this:
>>> su $USER -c "open http://foo.com";
>>>
>>> ($USER is the sitting-at-the-screen user.)
>>>
>>> On Nov 15, 2011, at 3:41 PM, Andy O'Meara wrote:
>>>> After enough years I thought this issue would fix itself, but it's time to see if someone knows what's going on. In our package postflight installer script, we use the open command to launch our web page which contains some getting started info. However, calling 'open http://foo.com' from the installer script opens Safari rather than the user's preferred browser. Yet the same line in my user terminal causes the correct browser to open, so clearly the installer env is missing something to invoke the correct browser. Anyone know the best way to address this?
>>>
>>> _______________________________________________
>>> 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
>>
_______________________________________________
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