How to change the CMT version
the default CMT version is hard coded in CMT.(c)sh, lhcbsetup.bat, localsetup.bat and ExtCMT.(c)sh, .bat. Before changing the version, it must be first tested on win32, slc3 and slc4, installed on win32, tested in production.
test on various platform
- To change the CMT version for a session:
- source $LHCBSCRIPTS/CMT.csh <new-version>
- call %CMTROOT%\..\<new-version>\mgr\setup.bat
build tar files
- from a Linux platform:
- mkexternaltar CMT <new-version> linux
- mkexternaltar CMT <new-version> win32
install on various platforms
-
- it is always installed by the CMT team on afs/cern.ch/sw/contrib/CMT/<new-version>
- to install it on a local area on win32
- cd %MYSITEROOT%
- python install_project.py -c <new-version> -p <project> -v <version>
test in production (DIRAC)
-
- when tar files exists ask Joel to install it everywhere and to test it.
- to test in a local installation or in Production after installation:
- source $MYSITEROOT/scripts/!ExtCMT.csh <new-version>
- call %MYSITEROOT%\scripts\!ExtCMT.bat <new-version>
make it the default
-
- update on $LHCBSCRIPTS/shell
- CMT.csh, .sh, ExtCMT.csh, .sh
- update on $LHCBSCRIPTS/win32
- lhcbsetup.bat, localsetup.bat, ExtCMT.bat
- commit changes on CVS
- rebuild the scripts tar files
- mkscriptstar Win32
- mkscriptstar Linux
- from the terminal server or your win32 PC make a cvs update on G:\Experiments\lhcb\scripts
--
FlorenceRanjard - 02 May 2007