http://bugs.winehq.org/show_bug.cgi?id=21773 --- Comment #11 from Ian Goddard <iang(a)austonley.org.uk> 2010-02-27 06:06:19 --- (In reply to comment #10)
You've been given number of ways how you can run tests within newly compiled environment: 1. ./wine /path/to/winetest-latest.exe 2. ./wine winetest 3. make test
All of the above _guarantees_ to use wine from the current source tree and not system installed one. Of course in all cases you have to start with clean wineprefix and make sure wine_gecko is available.
Just read your last sentence again: "Of course in all cases you have to start with clean wineprefix and make sure wine_gecko is available." If you simply tell people to take any of the above 3 you do not assure that the proviso in that sentence will be met. That means that you cannot trust any of the regression-testing results you get back from the community. Simply using the wine from the current source tree isn't enough. Good testing practice just isn't that simple. Ian -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.