just a minor issue, but if the script could please use $wine consistently, then it allows users, who use "wine-development" and "wine64-development" (i.e. on Debian) to change the script with a simple change of the binary names at the top of the script.
Debian-based distributions offer two types of WINE packages, where the newer version of WINE is found in the *-development packages. These packages can be installed along with the default WINE packages and do not conflict with one another, because the binaries have *-development appended to their names. Hence the need for a manual change of the script.
Right now does one have to change it everywhere it uses $wine or "wine".
As a feature request: ideal would be if the script could actually detect the presence of the *-development binaries and use them over the standard binaries.
Should be fixed as of 2dae99e748441a96dd737ac81d2772a359ba63c9. Please keep in mind that you have to specify your wine64 binary for the 64-bit setup and the wine binary for the 32-bit one.
Hello,
just a minor issue, but if the script could please use $wine consistently, then it allows users, who use "wine-development" and "wine64-development" (i.e. on Debian) to change the script with a simple change of the binary names at the top of the script.
Debian-based distributions offer two types of WINE packages, where the newer version of WINE is found in the *-development packages. These packages can be installed along with the default WINE packages and do not conflict with one another, because the binaries have *-development appended to their names. Hence the need for a manual change of the script.
Right now does one have to change it everywhere it uses $wine or "wine".
As a feature request: ideal would be if the script could actually detect the presence of the *-development binaries and use them over the standard binaries.