Hi Tomáš,
Thank you for reopening the bug. This was my first package in the
archive. I'll do a better job of testing packages in the future.
I think the problem is bigger than it initially appears. The patch
Andrey provides seems to only work for i386, not amd64. The
wine-development package only provides wine-development[0], whereas
wine provides wine[1]. Winetricks searches for a wine executable, not
the wine-development executable. The wine32-development package
provides a wine executable, which isn't provided by
wine64-development, which is why this only affects amd64, not i386. I
have attached a patch that appears to fix the wine-development issue
by searching for wine-development if wine can't be found.
If I got anything wrong let me know. I think I choose too difficult of
a package for my first package. Maybe I should re-orphan it to allow
someone more qualified to adopt it.
In the meantime, I will release a new version with Andrey's patch and
my patch if you agree with my assessment of the problem.
[0] - https://packages.debian.org/sid/amd64/wine-development/filelist
[1] - https://packages.debian.org/sid/amd64/wine/filelist
Thanks,
Joseph
Index: winetricks/src/winetricks
===================================================================
--- winetricks.orig/src/winetricks
+++ winetricks/src/winetricks
@@ -3718,6 +3718,11 @@ winetricks_init()
;;
*)
WINE="${WINE:-wine}"
+ _abswine="`which "$WINE" 2>/dev/null`"
+ if ! test -x "$_abswine" || ! test -f "$_abswine"
+ then
+ WINE="wine-development"
+ fi
# Find wineserver. Some distros (Debian) don't have it on the path,
# on the mistaken understanding that user scripts never need it :-(
# FIXME: get packagers to put wineserver on the path.
