SLAC	PEP-II
BABAR
SLAC<->RAL

HEPIC	E,S & H	Databases	PDG	HEP preprints
Organization	Detector	Computing	Physics	Documentation
Personnel	Glossary	Sitemap	Search	Hypernews

Comp. Search Who's who? Meetings FAQ Homepage Archive Environment Administration New User Info. Web Info/Tools Monitoring Training Tools & Utils Programming C++ Standard SRT, AFS, CVS QA and QC Remedy Histogramming Operations PromptReco Simulation Production Online SW Dataflow Detector Control Evt Processing Run Control Calibration Databases Offline Workbook Coding Standards Simulation Reconstruction Prompt Reco. BaBar Grid Data Distribution Beta & BetaTools Kanga & Root Analysis Tools RooFit Toolkit Data Management Data Quality Event display Event Browser Code releases Databases Check this page for HTML 4.01 Transitional compliance with the W3C Validator (More checks...)

Creating a New Package   Information on B A B A R software administration can be found at /BFROOT/doc/www/SoftwareAdmin.html Package coordinators should take advantage of the information there. In particular, you can find the link to the form to request the creation of a new package: /BFROOT/doc/www/Computing/SoftwareAdmin/pkgRequest.html Fill in the html form and submit it. If you check ``yes'' for e-mail notification, e-mail will be sent to the primary e-mail address (as listed in the B A B A R database) of each package coordinator each time changes are made to the package. A new offline (or online) package will usually be created within one working day. A package intended for both will take longer; only check this option if you really need it. Note that the naming convention for packages is a 3-letter prefix (first letter capitalized), followed by another word or words, also with first letter(s) capitalized. Examples are: DchOnline; IfrPid; SvtData. This is not rigidly enforced (cf. RecoData or SoftRelTools), but please use the convention if possible. Once created, you can check the (empty) package out of the repository. Then you can copy your files into the package directory and use cvs add <filename> to prepare them to be added to the repository. They won't actually be added until you do the cvs commit. See also Committing Your Changes to the Repository. When you have a package that is ready to be included in the next offline release, you should fill in the announcement form at http://www-hep.colorado.edu/reltest/Checklist.html Upon submission, you will be prompted to create a HyperNews item to announce the new package version. Two packages, in particular, that package co-ordinators should be aware of are PackageList and RegrTest. PackageList contains files that need to know about all the packages in the release system. For example, packages used in reconstruction need an entry in link_all_reco.mk. See the PackageList README for more information. A new package, RegrTest (``Regression Test''), contains utilities to help other packages make and run tests of their software. See the RegrTest web page: http://www.cithep.caltech.edu/~samuel/regr.html Also recall the Package Test page, mentioned in subsection  3.4.