I just finished a git bisect to establish the cause of the git regression given by http://bugs.winehq.org/show_bug.cgi?id=33715. My detailed report concerning the result of the bisect appears there, but I have an additional question concerning the git bisect process itself.
I pretty much follow the recommendations in http://wiki.winehq.org/RegressionTesting, but I like to completely remove my WINEPREFIX directory as the first step in my bisect test script to eliminate the possibility that some unclean cached result there is causing issues. But after a particular version of wine is built, that test script goes on to test it using wineconsole which has to populate WINEPREFIX itself (which is fine) since I removed it for a reason, but that step is accompanied by some popups concerning what I want to do about downloading mono (not available on Debian testing) and gecko (available on Debian testing, but I haven't figured out how to make the ./configure step of the wine build recognize that). I don't mind the popups, but I do mind having to answer the questions posed by them (say through the night) as the automated git bisect proceeds.
For the case where wineconsole populates the WINEPREFIX directory for the first time, is there a way to configure wine or run wineconsole so those popups that require me answering a question can be eliminated?
Alan __________________________ Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________
Linux-powered Science __________________________