New SRT Package

Table of Contents:

• Add files to CVS repository.
• problem diagnosis

Add files to CVS

     Once you receive a notice that the package has been created, you can
start add files into CVS. The new package will have a single GNUmakefile to
begin with. To commit your files into the CVS repository, follow the steps below: 

     1. Check out the new (empty) CVS package, e.g.
        $ cvs co newPkg
     2. cd into that directory,
        $ cd newPkg
     3. copy existing files into this directory or create new files from
        scratch, do not overwrite the GNUmakefile there  !!
        $ cp myOldCode/* .
     4. tell cvs that all of these files are to become part of the package,
        $ cvs add *
     5. store them into the repository,
        $ cvs commit
     6. from a working area, type 'cvs co newPkg' to get a working copy.
	Revise this copy if there is problem.

   An alternative scheme is import files into new package, not recommended
but may be necessary under some circumstances such as importing a vendor
software (use it as the last resort):

     1. make sure the repository is empty by typing 'ls $CVSROOT/newPkg'
        where 'newPkg' is the name of the new package. It should have only
 	single GNUmakefile.
     2. cd to the directory of your source file. This is step is very
        important!!! Import from wrong directory will overwrite files
        in the CVS repository.
     3. Type 'cvs import {newpkg} {vendortag} {version}' to import your files.
    	e.g. 'cvs import DchReco BaBar V00-00-01'. 
	[Note]: ignore conflict message of the GNUmakefile. There is a
		template GNUmakegile exists. It will be used in later step.
     4. from a working area, type 'cvs co newPkg' to get a working copy.
	You will get a template 'GNUmakefile'.
     5.	cd newPkg, revise GNUmakefile based on the GNUmakefile in the
	source directory. Then 'cvs ci GNUmakefile' to commit it. 

Problem Diagnosis

     1. cvs import: cannot make path to
    /afs/slac.stanford.edu/g/babar/repo/{pkg}: Permission denied
    
    Ignore this message, most users do not have write access to
    the top-level BaBar repository. Make sure the rest of import
    works.  

     2. cvs import: cannot make path to {dir} : Permission denied 
    If you receive error on other directories, either you do not have
    write access to the repository or the files in repository already
    exists.