On 03.06.2013 23:48, Alan W. Irwin wrote: > 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? >
You could download the recent gecko and mono files and place them in the appropriate places as described in http://wiki.winehq.org/Gecko Or you create a wineprefix after you removed it, but without a valid display set: DISPLAY=none wine wineboot