On 02/27/2016 08:30 PM, Michael Gilbert wrote: > On Sat, Feb 27, 2016 at 10:28 AM, Jens Reyer wrote: >> This is an automated email from the git hooks/post-receive script. >> >> jreyer-guest pushed a commit to branch master >> in repository wine. >> >> commit 03505ed825818db5ee0940a1e24ab7b6e38b42c0 >> Author: Jens Reyer <[email protected]> >> Date: Sat Feb 27 01:35:06 2016 +0100 >> >> Create winepath link and manpage. > > winepath belongs in the tools, that is why I stripped it from wine > proper a few uploads back.
My logic was to see winepath as a utility useful while "using" Wine, while I see the tools as something to "work" with Wine. But I see you're reasoning, so reverted. I had also accidentally added the winepath manpage to wine/stretch, reverted. I'm now looking into how to get winepath in tools the best way. Speaking of the tools: Do we give up on 32-/64bit co-installability of the tools permanently? I saw nobody complaining, neither after their dependencies made them not-coinstallable, nor since they officially conflict now. If yes, I propose to provide symlinks in path for all the tools now in /usr/lib/wineVERSION/ (wmc, wrc, winedump, winebuild and winemaker). 5 additional links in /usr/bin seem fair to me for an optional package that needs to be installed on purpose. We may also merge the wine[32|64]VERSION-tools. Opinions? Greets jre _______________________________________________ pkg-wine-party mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-wine-party
