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

File: [Development] / JSOC / CM / V3.0 / release.notes (download)
Revision: 1.1.1.1 (vendor branch), Mon Oct 1 23:12:21 2007 UTC (15 years, 4 months ago) by arta
Branch: Vtag, MAIN
CVS Tags: Ver_LATEST, Ver_9-5, Ver_9-41, Ver_9-4, Ver_9-3, Ver_9-2, Ver_9-1, Ver_9-0, Ver_8-8, Ver_8-7, Ver_8-6, Ver_8-5, Ver_8-4, Ver_8-3, Ver_8-2, Ver_8-12, Ver_8-11, Ver_8-10, Ver_8-1, Ver_8-0, Ver_7-1, Ver_7-0, Ver_6-4, Ver_6-3, Ver_6-2, Ver_6-1, Ver_6-0, Ver_5-9, Ver_5-8, Ver_5-7, Ver_5-6, Ver_5-5, Ver_5-3, Ver_5-2, Ver_5-14, Ver_5-13, Ver_5-12, Ver_5-11, Ver_5-10, Ver_5-1, Ver_5-0, Ver_4-7, Ver_4-6, Ver_4-5, Ver_4-4, Ver_4-3, Ver_4-2, Ver_4-1, Ver_4-0, NewTree01_cp09_JSOC, NewTree01_cp08_JSOC, NewTree01_cp07_JSOC, NewTree01_cp06_JSOC, NewTree01_cp05_JSOC, NewTree01_cp04_JSOC, NewTree01_cp03_JSOC, NewTree01_cp02_JSOC, NewTree01_cp01_JSOC, NetDRMS_Ver_LATEST, NetDRMS_Ver_9-5, NetDRMS_Ver_9-41, NetDRMS_Ver_9-4, NetDRMS_Ver_9-3, NetDRMS_Ver_9-2, NetDRMS_Ver_9-1, NetDRMS_Ver_9-0, NetDRMS_Ver_8-8, NetDRMS_Ver_8-7, NetDRMS_Ver_8-6, NetDRMS_Ver_8-5, NetDRMS_Ver_8-4, NetDRMS_Ver_8-12, NetDRMS_Ver_8-11, NetDRMS_Ver_8-10, HEAD
Changes since 1.1: +0 -0 lines
First new, reorganized JSOC tree

			Release Notes JSOC V3.0		14Aug2006
			-----------------------		---------

(Release to implement Postgres namespace features for DRMS)
(Notes will follow.)

The official release version is in /home/production/cvs/jsoc.
This will remain unchanged until the next release.
You may make any changes you want in your sandbox, but anything that you 
commit will appear in the next offical release.

**************** If You Don't Have a Sandbox ********************************

You need a cvs "sandbox" to contain your view of a JSOC release:
(There is no need to do this unless you're going to be a jsoc developer.)

Set the env variables:
CVSROOT=:ext:sunroom.stanford.edu:/home/cvsuser/cvsroot
CVS_RSH=ssh

Make a cvs dir and do:
> cd /home/you/cvs
> cvs checkout jsoc
############################################################################

----------------------------------------------------------------------------
Resync your sandbox with the V3.0 release:

> cd /home/you/cvs/jsoc
> cvs update -APd >& cvsupdate.log

Inspect cvsupdate.log for any "C " status.

       C file
         A  conflict  was detected while trying to merge your changes to file
         with changes from the source repository.  file  (the  copy  in  your
         working  directory) is now the result of attempting to merge the two
         revisions; an unmodified copy of your file is also in  your  working
         directory, with the name .#file.revision where revision is the revi-
         sion that your modified file started from.  Resolve the conflict


----------------------------------------------------------------------------
Check for any files that have not been commited (not Status: Up-to-date):

> cvsstatus     (NOTE: s/b an alias for $JSOCROOT/scripts/cvsstatus.pl)
		(see end)

Determine if any modified files need to be committed or replaced with the
repository version before proceeding.
If you have a file here that you wanted in the release, please contact CM.

----------------------------------------------------------------------------
You now need to make on linux_ia64 (lws) or linux_x86_64 or linuxia32 
(some workstations) machines depending on where you want to run:
Please use n12 and n00 for x86_64 and linuxia32 builds. (good compilers)

> ssh lws		(and then again for n12, etc.)
> cd /home/you/cvs/jsoc
> ./configure -force -client 
(ignore modification time in future msgs (small delta))

> make clean
> make -j 4 >& make.log.lws   (optional, run 4 jobs in parallel for speed)

Set your path for /home/you/cvs/jsoc/bin/linux_ia64 (or linux_x86_64 or 
linux_ia32). NOTE: This is usually done by source .setJSOCenv in your .login.

****************Additional Info**********************************************

The command 

> configure -help

will print information about how to create a customized build,
to e.g. use a different compiler or turn on debugging flags.

If you are unfamiliar with the use of cvs see the file:
jsoc/CM/working_with_sandbox.txt. 

There's a linux4 cvs gui at xim:/usr/bin/lincvs
Also on our jsoc web page:

http://jsoc.stanford.edu/cvs/jsoc/

----------------------------------------------------------------------------

WARNING: The "cvs diff" command does not always return differences even
when there are some. The "cvs status" will show that the file is not
Up-to-date but the "cvs diff" will not show any differences.

Work Around: Use the Apache cvs gui to see the diffs. For example, go to
http://jsoc.stanford.edu/cvs/jsoc/src/base/libdrms/
and click on the name in the File column and then click on
"diffs to previous #" to see the diffs.

-----------------------------------------------------------------------------

CHANGE to cvsstatus alias:
If you have this alias defined, please change it.
This was previously:
> alias cvsstatus
cvs status | egrep ^File: | egrep -v Up-to-date

Now make it (as approriate for your location of the jsoc tree):
> alias cvsstatus '$HOME/cvs/jsoc/scripts/cvsstatus.pl'

The old cvsstatus could generate many file names without giving their location 
in the tree. This was hard to deal with.

The new cvsstatus is now a perl script that will print out all the not 
Up-to-date files and also their full path name in the repository.


Karen Tian
Powered by
ViewCVS 0.9.4