Howto setup CVS for NPA
-----------------------

setenv CVSROOT /afs/slac.stanford.edu/g/npa/repo


Howto use CVS
-------------

Some fundamental CVS commands:

cvs co <pkgname>       # Checkout <pkgname> from HEAD of CVS
cvs -n update          # Update dry run (no changes are made to current dir)
cvs update -dA         # Update current directory to the HEAD of CVS
cvs diff               # Difference from HEAD (or current tag if sticky tag)
cvs diff -r <tagname>  # Difference from tag <tagname>
cvs add <filename>     # Add new file to your package
cvs rm <filename>      # Remove file from your package (must be deleted first)
cvs commit -m "<comment>" <filename> # Commit changes to modified 
                                     # file <filename> using <comment>
cvs commit             # Commit all modified files under current dir
cvs log <filename>     # Show history for file <filename>
cvs tag <tagname>      # Tag package with <tagname>


Howto create a new package
--------------------------

- change to your working directory and call cvs import:

cd <wdir>
cvs import -m "Initial import" <pkgname> <vendortag> <releasetag>

- since the above command will commit all the files under <wdir>, you
  might consider to keep <wdir> empty and then add files and sub
  directories by hand later (that way you might be able to maintain a
  better control of what you commit)

- use a meaningful name for <pkgname>, possibly starting with the
  string 'Npa'

- the <vendortag> and <releasetag> strings are mandatory, but it's not
  important what you actually specify

- after import checkout the CVS package:

cd ..
cvs co <pkgname>
cd <pkgname>

- optionally add files and directories:

cvs add <fileA>
cvs add <directory>
cvs add <directory>/<fileB>

- edit your working files as needed

- when ready, commit and tag:

cvs commit
cvs tag <tagname>

- use a meaningful name for <tagname>, eg something like Vjj-nn-rr
  (typically bump <rr> by one for bug fixes, <nn> for new features and
  <jj> for major changes)