Add Solaris regress comments

diff --git a/regress/README.ctest b/regress/README.ctest
index 97549b931024b2da8531a14aab8848558b77f691..f5374c93e0e8d3625ed6f68bd3957b33c4c36382 100644 (file)
--- a/regress/README.ctest
+++ b/regress/README.ctest
@@ -8,6 +8,7 @@ already had a working test framework in place, is the ability to have the
 results of each test submitted to a centralized dashboard system.  All of the
 test results are aggregated and summarized, where all of the developers can
 quickly see how the regression tests are running.
+====
 
 How to Use CTest
 ==================================================================
@@ -85,10 +86,10 @@ DartTestfile.txt that matches the pattern will be run.
 
 Note that you must have run ./scripts/do_sed at least once already in order to
 use Experimental mode.
+====
 
-Updating and Building Within CTest
+Updating and Building Within CTest:
 ==================================================================
-
 Before each Nightly run, ctest will automatically update the BACULA_SOURCE
 directory, and submit these updates along with the test results.  Any
 Experimental runs will not.
@@ -98,21 +99,43 @@ script scripts/update-ctest.  This script first compares the version of
 BUILD_SOURCE with that of the build/ directory.  If the two versions differ, or
 if the build/ directory does not exist, it will automatically run 'make setup'
 for you.
+====
 
-Viewing the Dashboard
+Viewing the Dashboard:
 ==================================================================
-
 You can view the dashboard at:
 
 http://regress.bacula.org/index.php?project=bacula
 
-
 Results will not be visible as soon as they are submitted to the server.
 Processing is currently done every 10 minutes, so you may have to wait up to 15
 minutes or so before your results show up.
+====
 
-=========================================================
+Getting CTest running on Solaris (thanks to Robert Hartzell):
+============================================================
+The regression is working in zone on opensolaris build 126
+
+ create a zone and install these pkg's:
+    SUNWcmake, SUNWmysql5, SUNWlibm, gcc-dev
+    SUNWgtar, SUNWgit, SUNWperl584usr,
+    and most of SUNWgnu*
 
+ In the config file I edited the "WHICHDB=" line to read:
+     WHICHDB="--with-mysql=/usr/mysql/5.0"
+
+ And then in the shell:
+ $ export LDFLAGS="-L/usr/mysql/5.0/lib/mysql -R/usr/mysql/5.0/lib/mysql"
+ $ PATH=/usr/gnu/bin:$PATH
+
+ When i first ran "make setup" it failed... couldn't create the database
+ so I had to run /usr/mysql/5.0/bin/mysql -u root mysql and do this:
+    grant all privileges on regress.* to ''@localhost;
+    grant all privileges on regress.* to ''@"%";
+====
+
+CTest script details:
+=========================================================
 Email from Frank describing the flow when running a ctest and some of the
 problems that come up.
 
@@ -194,8 +217,13 @@ create a hook to tag the version being tested, everyone as far as I can tell
 just seems to rely on the timestamp of the test.
 ======
 
+Important Note:
+======================================================================
 NOTE !!!!!!!!! ctest can actually back out changes that have been made to
-your local source repository.  As a consequence, it is probably better not to
+your local source repository (this was true for SVN, but I (Kern) am
+not sure it is true now that we have switched to git).
+
+As a consequence, it is probably better not to
 use a directory in which you are developing code for Nightly tests.  Seee the
 below explanation given by Frank Sweetser.