On 09/23/2014 10:34 PM, Joseph Bisch wrote: > I think it might actually be better to direct the user to set the WINE > and WINESERVER variable before running winetricks. That way if both > wine and wine-development are installed, the user can choose which to > use. It looks like your patch prioritizes the wine wineserver and > prioritizes the wine-development wine binary, which might lead to > issues if wine and wine-development are both installed.
No, I (hope to have) took care of that: wineserver from wine-development is the last in the list that is tried. If another wineserver is found, WINE stays untouched. Only if no other wineserver is found, the wine-development wineserver is taken and paired with WINE=/usr/bin/wine-development. So if you have wine stable installed, its wine and wineserver are taken. Regardless if you have co-installed wine-development or not. So the only problem is, if you have both wine (stable) and wine-development installed AND are using wine-development (then wine and wineserver from stable would be taken). In this case indeed setting WINE and WINESERVER would be better. But I think forcing everyone to set those variables just to have a clean solution for this special case would do more harm than good. So asking the user for WINE and WINESERVER should only happen if both wine and wine-development are installed (or even better the running processes could be checked to figure out which wineserver is currently running). But seriously, I think it is enough to just document this fact and just fix the currently non-working situation (better do the good thing, instead of trying the perfect thing without implementing it). Greets jre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
