(file) Return to release.notes CVS log (file) (dir) Up to [Development] / JSOC / CM / V3.0

  1 arta  1.1 			Release Notes JSOC V3.0		14Aug2006
  2           			-----------------------		---------
  3           
  4           (Release to implement Postgres namespace features for DRMS)
  5           (Notes will follow.)
  6           
  7           The official release version is in /home/production/cvs/jsoc.
  8           This will remain unchanged until the next release.
  9           You may make any changes you want in your sandbox, but anything that you 
 10           commit will appear in the next offical release.
 11           
 12           **************** If You Don't Have a Sandbox ********************************
 13           
 14           You need a cvs "sandbox" to contain your view of a JSOC release:
 15           (There is no need to do this unless you're going to be a jsoc developer.)
 16           
 17           Set the env variables:
 18           CVSROOT=:ext:sunroom.stanford.edu:/home/cvsuser/cvsroot
 19           CVS_RSH=ssh
 20           
 21           Make a cvs dir and do:
 22 arta  1.1 > cd /home/you/cvs
 23           > cvs checkout jsoc
 24           ############################################################################
 25           
 26           ----------------------------------------------------------------------------
 27           Resync your sandbox with the V3.0 release:
 28           
 29           > cd /home/you/cvs/jsoc
 30           > cvs update -APd >& cvsupdate.log
 31           
 32           Inspect cvsupdate.log for any "C " status.
 33           
 34                  C file
 35                    A  conflict  was detected while trying to merge your changes to file
 36                    with changes from the source repository.  file  (the  copy  in  your
 37                    working  directory) is now the result of attempting to merge the two
 38                    revisions; an unmodified copy of your file is also in  your  working
 39                    directory, with the name .#file.revision where revision is the revi-
 40                    sion that your modified file started from.  Resolve the conflict
 41           
 42           
 43 arta  1.1 ----------------------------------------------------------------------------
 44           Check for any files that have not been commited (not Status: Up-to-date):
 45           
 46           > cvsstatus     (NOTE: s/b an alias for $JSOCROOT/scripts/cvsstatus.pl)
 47           		(see end)
 48           
 49           Determine if any modified files need to be committed or replaced with the
 50           repository version before proceeding.
 51           If you have a file here that you wanted in the release, please contact CM.
 52           
 53           ----------------------------------------------------------------------------
 54           You now need to make on linux_ia64 (lws) or linux_x86_64 or linuxia32 
 55           (some workstations) machines depending on where you want to run:
 56           Please use n12 and n00 for x86_64 and linuxia32 builds. (good compilers)
 57           
 58           > ssh lws		(and then again for n12, etc.)
 59           > cd /home/you/cvs/jsoc
 60           > ./configure -force -client 
 61           (ignore modification time in future msgs (small delta))
 62           
 63           > make clean
 64 arta  1.1 > make -j 4 >& make.log.lws   (optional, run 4 jobs in parallel for speed)
 65           
 66           Set your path for /home/you/cvs/jsoc/bin/linux_ia64 (or linux_x86_64 or 
 67           linux_ia32). NOTE: This is usually done by source .setJSOCenv in your .login.
 68           
 69           ****************Additional Info**********************************************
 70           
 71           The command 
 72           
 73           > configure -help
 74           
 75           will print information about how to create a customized build,
 76           to e.g. use a different compiler or turn on debugging flags.
 77           
 78           If you are unfamiliar with the use of cvs see the file:
 79           jsoc/CM/working_with_sandbox.txt. 
 80           
 81           There's a linux4 cvs gui at xim:/usr/bin/lincvs
 82           Also on our jsoc web page:
 83           
 84           http://jsoc.stanford.edu/cvs/jsoc/
 85 arta  1.1 
 86           ----------------------------------------------------------------------------
 87           
 88           WARNING: The "cvs diff" command does not always return differences even
 89           when there are some. The "cvs status" will show that the file is not
 90           Up-to-date but the "cvs diff" will not show any differences.
 91           
 92           Work Around: Use the Apache cvs gui to see the diffs. For example, go to
 93           http://jsoc.stanford.edu/cvs/jsoc/src/base/libdrms/
 94           and click on the name in the File column and then click on
 95           "diffs to previous #" to see the diffs.
 96           
 97           -----------------------------------------------------------------------------
 98           
 99           CHANGE to cvsstatus alias:
100           If you have this alias defined, please change it.
101           This was previously:
102           > alias cvsstatus
103           cvs status | egrep ^File: | egrep -v Up-to-date
104           
105           Now make it (as approriate for your location of the jsoc tree):
106 arta  1.1 > alias cvsstatus '$HOME/cvs/jsoc/scripts/cvsstatus.pl'
107           
108           The old cvsstatus could generate many file names without giving their location 
109           in the tree. This was hard to deal with.
110           
111           The new cvsstatus is now a perl script that will print out all the not 
112           Up-to-date files and also their full path name in the repository.
113           

Karen Tian
Powered by
ViewCVS 0.9.4