ntdll: Use environment variable "WINESERVER" first on search for wineserver to start.

[Alexandre Julliard]

Ralf Habacker <ralf.habacker at freenet.de> writes:

> Am 17.02.2017 um 15:14 schrieb Alexandre Julliard:
>> Ralf Habacker <ralf.habacker at freenet.de> writes:
>>
>>> Am 16.02.2017 um 22:10 schrieb Sebastian Lackner:
>>>> On 15.02.2017 15:27, Ralf Habacker wrote:
>>>>> This fixes the issue that WINESERVER environment variable is only
>>>>> used if @bindir@/wineserver does not exist.
>>>>>
>>>>> Fixes https://bugs.winehq.org/show_bug.cgi?id=40811
>>>> Maybe I'm missing something, but what would be the purpose of running
>>>> a different wineserver? 
>>> This is not to run a different wineserver. This is required to start
>>> wineserver with command line parameters e.g. by creating a wineserver.sh
>>> shell script with specific informations:
>>>
>>> cat ~/wineserver.sh
>>> /usr/bin/wineserver --persistent=600
>>>
>>> WINESERVER=~/wineserver.sh wine <myapp>
>> I'm not sure what your use case is for this, but I'd suggest adding a
>> different mechanism to specify the server timeout, like a registry key.
>>
> You are saying that the command line parameter -p or --persistent should
> be removed because it is useable only in very special situations and
> replaced by a related registry key according to
> https://wiki.winehq.org/UsefulRegistryKeys for example 
> HKCU/Software/Wine/WineServer Value Persistent ?

I'm not saying that it should be removed, I'm saying that if you have a
situation where using the command line parameter is inconvenient, it
would be possible to also make it configurable through a registry key.

-- 
Alexandre Julliard
julliard at winehq.org