- wineserver is not in PATH but in an arch specific subdirectory in
/usr/lib (works flawlessly for plain wine, but is a pita for 3rd party stuff like winetricks and PlayOnLinux).
Also a pita for people who advise typing things like 'wineserver -k'? Are they really supposed to know to look in this directory?
Why is it in an arch-specific subdirectory when wineserver is designed to be architecture independent (same interface, and potentially the same server instance, used with 32-bit and 64-bit clients)?
Er, sorry, I missed the part where you were describing the current state and not necessarily advocating for it. Never mind.
Although now this part seems a bit odd:
On Fri, Sep 18, 2015 at 2:34 PM, Jens Reyer jre.winesim@gmail.com wrote:
- Download of gecko and mono packages is disabled.
Doesn't keeping it (so that the wine package downloads a binary blob not built by Debian) violate their principles?