[rkward-cvs] SF.net SVN: rkward:[4198] trunk/rkward

[tfry at users.sourceforge.net]

Revision: 4198
          http://rkward.svn.sourceforge.net/rkward/?rev=4198&view=rev
Author:   tfry
Date:     2012-03-22 19:03:43 +0000 (Thu, 22 Mar 2012)
Log Message:
-----------
Do not recommend running plugintests to regular end users.

Modified Paths:
--------------
    trunk/rkward/INSTALL
    trunk/rkward/tests/CMakeLists.txt

Modified: trunk/rkward/INSTALL
===================================================================
--- trunk/rkward/INSTALL	2012-03-20 11:51:24 UTC (rev 4197)
+++ trunk/rkward/INSTALL	2012-03-22 19:03:43 UTC (rev 4198)
@@ -19,10 +19,7 @@
 > make
 > sudo make install
 
-Then, optionally:
-> make plugintests	# see section "Automated tests" below
 
-
 CMake options (configuring)
 ===================
 
@@ -60,19 +57,19 @@
 Make sure you have set the correct path in cmake (the -DCMAKE_INSTALL_PREFIX option).
 
 
-Automated tests
+Running
 ==================
 
-While not required, you are encouraged to run 'make plugintests' *after* completing the installation. This will run a series of automated diagnostics, covering various functionality.
+For now it's recommended to run RKWard from the command-line for debug-output. For the few available command-line options see
 
-If all or most tests fail, this will typically indicate a problem in your installation. In this case, please make sure, you have followed all above instructions diligently.
+> rkward --help
 
-If individual tests fails, this may indicate a problem in RKWard. Please report such failures to rkward-devel AT lists DOT sourceforge DOT net, including details on your installed versions of KDE, R, and RKWard.
+If an error occurs directly after starting, this will typically indicate a problem in your installation. In this case, please make sure, you have followed all above instructions diligently.
 
 
-Running
+Automated tests
 ==================
 
-For now it's recommended to run RKWard from the command-line for debug-output. For the few available command-line options see
+A series of automated functionality tests can be run unsing 'make plugintests' *after* completing the installation. Unfortunately, these tests are rather prone to false alarms, and thus end users are not currently encouraged to run the tests. However, esp. developers, and packagers patching the sources should run 'make plugintests' after doing their changes. For failed tests, please take some time trying to understand, exactly how the test failed. Often it's just a harmless difference in rounding or formatting of output.
 
-> rkward --help
+If you see a genuine test failure, unrelated to your patches, please report this to rkward-devel AT lists DOT sourceforge DOT net, including details on your installed versions of KDE, R, and RKWard.

Modified: trunk/rkward/tests/CMakeLists.txt
===================================================================
--- trunk/rkward/tests/CMakeLists.txt	2012-03-20 11:51:24 UTC (rev 4197)
+++ trunk/rkward/tests/CMakeLists.txt	2012-03-22 19:03:43 UTC (rev 4198)
@@ -3,4 +3,4 @@
 	WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR})
 
 # This will hopefully run *after* everything is installed
-INSTALL(CODE "MESSAGE(STATUS \"\n--------------------\nInstallation appears to be complete (unfortunately it is hard to tell in CMake).\nConsider running\n    make plugintests\nfor some automated functionality tests.\nIn case of errors, consult the file 'INSTALL'.\n--------------------\")")
+INSTALL(CODE "MESSAGE(STATUS \"\n--------------------\nInstallation appears to be complete (unfortunately it is hard to tell in CMake).\nIn case of errors, please make sure to consult the file 'INSTALL'.\n--------------------\")")

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.