***** WARNING ******
This is an automatic procedure to update the condor distribution 
of jim_client. It was written in 2002 and was used a couple of times.
Every time it needed some change to fit in e.g. new condor binaries.
DO NOT USE THIS PROCEDURE BLINDLY!!!

GG, Apr 15, 2004
***** WARNING ******

--------------------------------------------------------------------
Updating the jim_client package : 
--------------------------------------------------------------------
1. Check out the packages from cvs.
cvs co jim_client
 
2. To update the pakages when new release of condor is available
   <i>   modify "CONDOR_REPOSITORY = /home/condorg/CondorG-snap" in
         "GNUmakefile" to point to the location of the new CondorG
         release.
   <ii>  make cleanpkg 
   <iii>  Then do "make package".
   <iv>  Depending on if there are new files to be added or some files will no 
         longer be used, issue 
           cvs add .  OR 
           cvs remove .
   <iv> cvs commit -m"new condor release" .

 
3. To build the tarball and add the product to kits, do:
source DIST
 
--------------------------------------------------------------------
Important notes 
--------------------------------------------------------------------
 
1. A single "condor_config" file is used for configuration instead of
   a combination of condor_config + condor_config.local. This single
condor_config is constructed as explained in the next section.
 
-------------------------------------------------------------------------
Creating condor_config.template file from a new condor release
-------------------------------------------------------------------------
1. Download the "condor-6.x.x-linux-x86-glibc22.tar.gz" and "condor-g-6.4.1.tar.gz".

2. First extract the condor-only release. Then extract condor-g into the same directory 
as condor-only release. 
In this location <releasedir/etc/examples> you should see the following files
condor_config.generic
condor_config.local.central.manager
condor_config.local.dedicated.submit
condor_config.local.condor-g

3. When you do a "make package", a condor_config.template file is created from 
one or more of the following files
condor_config.generic 
condor_config.local.central.manager 
condor_config.local.dedicated.submit 
condor_config.local.condor-g.

4. So you must make sure when you have new release of condor that these files
are present , and that the GNUmakefile is able to find them.

------------------------------------------------------------------------
Installing jim_client package
--------------------------------------------------------------------------
1. products> upd install jim_client vxx_xx

2. products> ups tailor jim_client