X-Git-Url: http://git.uio.no/git/?a=blobdiff_plain;f=HLT%2FREADME;h=8af0689180a0006b3f6d98f342b64a15dab1e936;hb=48bcc98ba9601f4d7913eb5015822cc53a4e791d;hp=68ac6faa833f76b208c55f19eae826d6b4d20489;hpb=f59fee6df2ea7ba8faa1648ad48a5bca1bef42ad;p=u%2Fmrichter%2FAliRoot.git

diff --git a/HLT/README b/HLT/README
index 68ac6faa833..8af0689180a 100644
--- a/HLT/README
+++ b/HLT/README
@@ -16,13 +16,13 @@ Comments, bug reports, suggestions welcome!
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 + 1. Overview
 + 2. Requirements
-+ 3. Setting up a version retrieved from CVS
++ 3. Setting up a version retrieved from SVN
 + 4. Modifying a distributed package
 + 5. Installation
 + 6. Documentation
 + 7. Further information
 + 8. Reporting bugs/Asking for support
-+ 9. Committing to the AliRoot CVS
++ 9. Committing to the AliRoot SVN
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
 1. Overview
@@ -55,7 +55,7 @@ usual way (ROOTSYS, ALICE_ROOT, library locations evtl. specified in
 LD_LIBRARY_PATH, ...). Actually, the BASE and SampleLib modules are
 not dependend on AliRoot. The TPCLib does.
 
-To set up a version retrieved from CVS, autoconf 2.57, automake 1.6
+To set up a version retrieved from SVN, autoconf 2.57, automake 1.6
 ,and libtool 1.4 or higher versions are required. Thats the versions
 which come with the Scientific Linux CERN 3. The same applies if
 you want to change the Makefiles.
@@ -63,11 +63,11 @@ you want to change the Makefiles.
 If your GNU build tools are too old, ask the maintainers for a distributed
 package.  
 
-3. Setting up a version retrieved from CVS
+3. Setting up a version retrieved from SVN
 ==========================================
 Skip this section if you have started from the tar ball.
 
-A version checked out from CVS requires a few steps to set up the Makefiles.
+A version checked out from SVN requires a few steps to set up the Makefiles.
 Go to the directory and run
 
   autoreconf -i -f
@@ -143,6 +143,9 @@ Some important options (all options are on by default):
   --disable-trd              # disable compilation the TRD library
   --disable-dimuon           # disable compilation the MUON library
   --disable-aliroot-logging  # disable logging
+  --disable-doc		     # disable creation of doxygen documentation
+  --disable-strict           # disable strict coding conventions and compilation flags
+
 
 All detector libraries (including sample and util lib) require AliRoot,
 compilation is disabled if no working AliRoot version was found. This can
@@ -210,7 +213,7 @@ A wiki with detailed information is set up at
 
 8. Reporting bugs/Asking for support
 ====================================
-Please include the following information into your request:
+Please include the following information into your report/request:
  - config.log from your build directory
  - output of the make process. Note: Redirect BOTH the stdout and stderr
    channel to a log file. Redirection depends on the shell you are using:     <br>
@@ -220,20 +223,23 @@ Please include the following information into your request:
  - history of the commands you are using for compilation
    history > history.log
 
-9. Committing to the AliRoot CVS
+9. Committing to the AliRoot SVN
 ================================
 For development of HLT analysis code check out a HEAD version from the 
 repository and implement your code. 
 
 For committing do:
  - 1. make sure that the code changes are correct                    <br><tt>
-      cvs diff | less                                                </tt><br>
+      svn diff | less                                                </tt><br>
       \b Remember to restore all temporary changes you made (e.g. log level)
- - 2. cvs update
+ - 2. svn update
  - 3. correct merging conflicts
  - 4. compile and test your code again
- - 5. send the whole HLT module except the build sub-directories to
+ - 5. depending on where you changes are send the whole HLT module except the build
+      sub-directories or your HLT sub- directory to
       Matthias.Richter@ift.uib.no
+      Please include a message/description for the check in
  - 6. you will get a notification when the code is committed, right after that
-      you must either do another cvs update or check out the complete module
-      again in order to have the right CVS information.
+      you must either do another svn update or check out the complete module
+      again in order to have the right SVN information. Please check that your
+      code has been correctly committed.