1. OpRelease 1.0 J.E Campagne CERN 14/2/02

2. The different areas Official Area OpRoot OpRec … User Devel. Area OpRoot/TgtScin OpRec/Tracking … use CVS cmt co cvs ci ROOT CERNLIB CLHEP BOOST External kits use cmt co or Web download At CERN or Local PC Possible because CMTPATH = « dev-area »:« official-area »

3. Directory structure u /OpRelease –requirements configuration file –At CERN: doc. files, OpRelease-1.0.tgz Web downlable official sources and shared-libraries (Linux) u OpRelease/Configurator –common configuration package u OpRelease/1.0 –root dir. of the 1.0 release u OpRelease/1.0/CMTI –Root dir. of the CMT interfaces to the External kits u OpRelease/1.0/Op –OpRoot, OpRec, OpUtils: main Opera packages and general purpose packages u OpRelease/1.0/OperaPolicy –General code policy package that is used by Op Policy dedicated packages u OpRelease/1.0/OpManager –Package that uses the frozen version of all packages

4. The top level « requirements » file u CMTSITE: tag to set the environment/macro variable according to local settings: ex. CERN, PC_LOCAL u KITS_DIR: directory where the External Kits are installed in case of PC_LOCAL (if the kits are already installed then each CMT Interfaces should be tuned: ex. at CERN) u OPERA_DIR: directory where is installed the official release u OPERA_RELEASE: version number of the release (1.0) u CMT_INTERFACES: directory where the CMT Interfaces to the External Kits are installed (in general ${OPERA_DIR}/${OPERA_RELEASE})

5. « Policy » structure OperaPolicy OpRecPolicy Used by OpRec and all subpackages OpRootPolicy Used by OpRoot and all subpackages use Defines commonalities - compilation options - binary directory - cmt patterns -… particularities refinements

6. « Manager » structure OpManager OpRec/OpRecManager OpRoot/OpRootManager « These packages make explicit the version of the (sub)-packages used for a dedicated release » use CLHEP v1r7 CMTI use CERNLIB v2001 CMTI use BOOST v1r20 CMTI use OperaPolicy v1 use OpUtils v1 use OpRec v1 use OpRecPolicy v1 OpRec use Kalman v1 OpRec use Pattern v2 OpRec use Tracking v1 OpRec Ex. OpRec/OpRecManager of OpRelease 1.0 Used for « cmt co –R OpRoot/OpRootManager »

7. What is a Release? v1 v1r1 v2r3 HEAD v3r6 v3r7 v4r1 HEAD OpRecOpRoot 1.0 2.0 OpRec and OpRoot will evolves from OpRelease 1.0 independantly (cvs co, cvs ci, cvs rtag), but at a certain point we will decide that the developments should converge to froze a new complet set that will be called 2.0. Version backward compatibility: based on I/O? v1, v1r1: backward compatible v1, v2 : non backward compatible

8. Source of Documentations u CVSWeb: –Look at the CVS repository setup by H. Meinhard (CERN-IT) »http://opera-sw.cern.ch/cgi-bin/cvsweb.cgi u « HowTo » file: –Get the list of official packages and their version –Get the API documentation of OpRec. –Install at CERN a private version for developments. –Install at home a private version for developments. –Get the external kits. –Add a new subpackage. –Compile. –Work with the Opera CVS repository. »/afs/cern.ch/exp/opera/OpRelease/HowTo.html Of course feed back will improve the use case description.