SVTVME pacakge maintenance

basic rules:

• make sure you read Thomas's SVT software page first, especially the introduction to CVS usage.
• all code/headers/doc is in online cvs repository (setup cvs -q online).
• changes in cvs repository are done with individual user names.
  NEVER, NEVER make changes in cvs as cdf_svt or similar.
• instead handling of ups packages (i.e. of source/doc/libraries/binaries etc. made available to users on the cdf online disk via the setup svtvme commandI is done by user cdf_svt.
• read Jim Patrick's tutorial in here also a lot of usefull stuff about e.g. ups and setup is in the online software pages.
• usefull pointers:
  • CVS home
  • UPS/UPD manuals
  • make
  • gmake (ps)
  • gmake (html)
• setup svtvme will setup the current fision version. This may or may not be the best choice. As of March 2001, this is 2_15 which is fine.
• following instructions indicate to use b0dap30 to compile for VxWorks, b0dau30 can not be used anymore. Official updates using the svtvme_update_k5 procedure will do Linux and VxWorks flavors.
• Kerberos is required for online machines. So in the following I only give instructions that require a kerberos ticket. Also note that to log on an online machine from offsite (or a laptop using DHCP !) you need to log into antoher on-site CDF machine first.

how to make changes in CVS repository

1. get a kerberos ticket and log on b0dapxx
2. create a work directory: e.g. mkdir ~/work
3. setup cvs -q online
4. cd ~/work
5. cvs checkout svtvme
   • cvs creates the directory svtvme and all the tree below it
6. cd svtvme
7. look at setup_local scriprt in this directory, it has the command:
   setup svtvme -r ${PWD} -M ups -m svtvme.table
   you must execute this command so the svtvme logicals point to this new work area, rather then to the real package directory on the online code disk. Then:
8. cd svtvme/src
9. gmake
   this makes local copies of libraries. If you want to test local copied of VxWorks libraries as well, you need to re-issue the previous setup command (from svtme directory, not svtvme/src !) with qualifier -qppc and then -q68k. And re-run gmake (in svtvme/src) each time. Also you need to log b0dau30 machine and run gmake to make Irix library. I recommend to test Irix compiler when making big changes, it has different pickyness then gcc or $VXCC that helps getting code straight.
10. cd svtvme/src
11. edit/change/test/.... source code
12. similarly on header files in svtvme/include etc/.
13. when done: cvs commit -m"comment" file_name for each file you changed, or commit -m"comment" with no file name if same comment applies to all changed files
    • not all users can committ. At present ukyang,barchies,spinella,sdonati,belforte,rescigno,speer,ashmansk,sarkar and zanetti can. Ask Jim Patrick for permission if needed (or ask Stefano or Bill to ask it for you). Or ask them to put in the new code.
    • list of authorised is in b0dau30:/cdf/code/cvs/CVSROOT/check_access (only accessible on b0dau30 !)

how to make changes in development version of the package
(development version is just the head of the repository)

• Easy and fast via kerberised script: just type ~cdf_svt/svtvme_update_k5
  • for this to work your kerberos principal has to be listed in ~cdf_svt/.k5login. If not so, ask someone who has his/hers there to add you.
• slow and tedious to control all details
  1. put the new code in cvs as for above procedure
  2. get a kerberos ticket on b0dap30 and type: ksu cdf_svt
  3. setup cvs -q online
  4. setup svtvme -d
  5. cd $SVTVME_DIR
  6. cvs update -d
  7. gmake
  8. setup svtvme -q ppc -d
  9. gmake
  10. setup svtvme -q 68k -d
  11. gmake

How to make a new frozen version of the package (or new release),
for example v5_18, i.e. something users will access with: setup svtvme v5_18

1. test first as development as above
2. when happy with head of repository status tag it in cvs from your individual account with
   • cvs tag v5_18
3. log in b0dap30 and ksu cdf_svt
4. setup cvs -q online
5. setup svtvme -d (or any other version)
6. cd $SVTVME_DIR
7. cd ..
8. mkdir v5_18
9. cd v5_18
10. cvs checkout -r v5_18 svtvme
11. mv svtvme/* .
12. rmdir svtvme
13. now must declare this to ups so setup can work:
    1. ups declare -f NULL -r ${PWD} -m svtvme.table -z /cdf/code-common/cdfonline/upsii_database svtvme v5_18
    2. ups declare -f NULL -q ppc -r ${PWD} -m svtvme.table -z /cdf/code-common/cdfonline/upsii_database svtvme v5_18
    3. ups declare -f NULL -q 68k -r ${PWD} -m svtvme.table -z /cdf/code-common/cdfonline/upsii_database svtvme v5_18
14. setup svtvme v5_18
15. gmake
16. then re-execute setup and run gmake for all flavors as before, logging on the needed operating systems