[winetest] Updated the README to reflect a bit of research into using Winetest to report Wine (on Linux/Mac) results, not only Windows results.

[Jeremy White]

---
 programs/winetest/README |   52 ++++++++++++++++++++++++++++++++++++++++++++-
 1 files changed, 50 insertions(+), 2 deletions(-)

diff --git a/programs/winetest/README b/programs/winetest/README
index 90e8acc..b50efac 100644
--- a/programs/winetest/README
+++ b/programs/winetest/README
@@ -3,20 +3,68 @@

 Winetest is a single-executable version of all the DLL conformance
 test programs suitable for unattended testing and report submission.
-People assigned to build winetest must take care of the following
-files, which are only used by 'make dist':
+
+There are two ways that you can use Winetest.  First, a team of
+volunteers uses Winetest to build date specific versions of winetest.exe
+which other testers can download and run on their Windows computers.
+
+Second, you can invoke winetest directly from the winetest build
+directory on your native system.
+
+Winetest requires three files which are only used by 'make dist':

 * build.id

 Contains a single (either CR or CR-LF) terminated line providing the
 build identification.  The accepted characters are [-.0-9a-zA-Z].

+The current convention is that this is set to the date and time that
+a given Winetest.exe was built, e.g., 200802050743.
+
+However, whatever you use will be used as the primary index when
+it is reported to test.winehq.org, so it will be visible and will
+affect the organizational structure of the reports on that site, so please
+choose your build.id with care.
+
 * tests.url

 Also contains a single terminated line providing the archive URL of
 the testing suite being built.

+The current convention is that this points to a location that someone
+can use to download the winetest.exe that is being built.
+
 * build.nfo

 Contains a block of terminated lines providing miscellaneous
 information about the build, like eg. the tools being used.
+
+
+Running Winetest from the Wine source tree:
+  Running Winetest is essentially identical to running 'make -k test'
+  with the added benefit that the results are reported to a central
+  server.
+
+  To do this, you must first populate the three files given above.
+  Only the build.id is truly critical, as that will control where
+  the result is cataloged.
+
+  Then, invoke
+    make dist
+    make
+  Followed by:
+    ./winetest-dist [-h]
+
+  Without arguments, winetest will run interactively; a -h will
+  show you a list of other choices, including a non interactive mode.
+
+  Most useful is:
+    ./winetest-dist -c -t "your-tag-here"
+  which will run in an unattended mode.
+
+Determining a Tag ID:
+  Winetest will require a tag id when run.  There is no hard and fast
+  convention for this.  Ideally you would include your name or some
+  identifier that would allow someone to trace the report back to you,
+  along with enough information for you to distinguish amongst your
+  test systems, presuming you have multiple.
-- 
1.5.3.6