On Wed, Apr 4, 2012 at 12:00, Andrey Rahmatullin <[email protected]> wrote: > On Wed, Apr 04, 2012 at 11:47:06AM -0700, Austin English wrote: >> >> Yes, the current upstream winetricks doesn't have this bug and properly >> >> dies on my system. I needed to hardcode >> >> /usr/lib32/wine-unstable/wineserver there to make it work but that's >> >> another question and I don't know whether it applies to official Debian >> >> wine packages. >> > Ouch. Upstream would like to have a patch that adds all the needed >> > search locations, e.g. /usr/lib32/wine-unstable/wineserver, I think. >> A user reported this in #winehq yesterday (first I'd heard of it). I'd >> argue it's a debian packaging bug, wineserver is a binary, not a >> library, and belongs in $PATH. > If a binary is not intended to be launched by users directly (see postfix, > dovecot or git), it doesn't belong in $PATH: > > """ > It is recommended that supporting files and run-time support programs that > do not need to be invoked manually by users, but are nevertheless required > for the package to function, be placed (if they are binary) in a > subdirectory of /usr/lib, preferably under /usr/lib/package-name. > """ > [Debian Policy 8.2] > > I don't know whether this applies to wineserver but its manpage probably > suggests that it does. > > -- > WBR, wRAR
wineserver -k is often used to stop runaway wine processes, by a user. wineserver -p/wineserver -w can also be useful, though not as common. -- -Austin -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
