		README for the Fast Installation Option
			Updated: November 21, 2011

These are the instructions for installing the JGOFS/GLOBEC
software using the "Fast Install" method. This method takes
advantage of a tar file with all the latest JGOFS/GLOBEC
software in place and is based on the JGOFS/GLOBEC V2.2
software.

This process by be hampered if you do not own the files
so can delete and/or edit them in the JGOFS/GLOBEC root
directory. Check the file protections to verify that you
have the necessary privileges.

To take advantage of this fast install option it is best 
if you are already running Version 2.00 or higher of the
software. If you are not, then we recommend that you install
the software in an empty directory. The only subdirectory
structure you want to preserve and reuse is your ../objects
directory and its contents. Since the fast install option does
not automatically replace your existing ../objects subdirectory,
you should be okay. However, if you want to be sure, rename
your objects subdirectory. (See step 2d.)

To install the software it is highly recommended that you
save a complete copy of your current installation as a tar 
file just in case reality strikes. (We do make an attempt not
to replace your existing copy of dir, however.)

	1. Change directory to your JGOFS/GLOBEC root directory:

		cd /JGOFS_GLOBEC_root

	2.a Create a tar file of your existing software

		tar -cvf existing_jgofs_globec_site.tar .

In any case, you must save your existing copy of the dir
application located in /JGOFS_GLOBEC_root/htmlbin subdirectory.
You will either use this version of dir or make edits to the new
dir to match your existing copy. This is necessary since the
dir application has not yet been updated to take advantage
of the build-env.conf configuration file.

	2.b It may be useful to save a copy of dir and dir-join2-new

		cp htmlbin/dir htmlbin/dir-save
and
		cp htmlbin/dir-join2-new htmlbin/dir-join2-new-save	

	
The versions provided (located in the <root directory>/htmlbin as
_dir_ and _dir-join2_ would have to be edited for such entries
as $jghome, $topdir, and $office. The dir application does not yet
take advantage of the configuration file so have to be hand edited.
Until then, the new versions are supplied as _dir_ and _dir-join2_
so as not to delete your existing copies. At this point, you are
usually safe to use your own, existing copies of these routines.


	2.c Open an editor displaying your existing copy of build_env.pl
or make a copy of it, if this is the first time you will be using
the build_env.conf file. It is useful to see what options and
choices you made for options (e.g. $jghome, $topdir, and $office) 
so you can duplicate these in the build_env.conf file.

	2.d If you are installing the software in an existing JGOFS/GLOBEC
root directory, then first save the ../objects subdirectory by renaming it.

	cd <JGOFS/GLOBEC root directory>
	mv objects objects-save

If you are deleting the contents of your JGOFS/GLOBEC directories
in order to do a clean install, you still want to save the objects
subdirectory. You can do this using the following:

	mv objects ~/objects-save

which will move this directory to your home directory.

	3. ftp://globec.whoi.edu/pub/software/JGOFS_GLOBEC/pre-release

Untar the "Fast Install" tar file. YOU DID BACKUP YOUR OWN SITE FIRST,
RIGHT?

	4. tar -xvf fast_install-V1.xx

Get a copy of the "Fast Install" tar file from the JGOFS/GLOBEC
software site and place it in your JGOFS/GLOBEC root directory.

	ftp://globec.whoi.edu/pub/software/JGOFS_GLOBEC

After untaring, several files need to be either put in place or
modified.

In the JGOFS/GLOBEC root directory, copy the _build-env_.pl file
to build-env.pl. If you have your own, modified version of this file
you will have to check on the differences. However, if you take full 
advantage of the build-env.conf file (see below) you should not have
to worry about changes made to the build-env.pl file and this copy
can proceed without a second thought. 
	
	5. cp _build-env_.pl build-env.pl

Compare your copy of the build-env.conf file to the new version
called _build-env_.conf. Make any changes necessary. If you do not
have a copy of the build-env.conf file, create it and make the few
necessary changes. Remember that the values specified in this
configuration file superseed the values specified in the build-env.pl
file.

	6a. diff _build-env_.conf build-env.conf

or

	6b.  cp _build-env_.conf build-env.conf

Make the necessary edits to the build-env.conf file, such as
the name of your data server.

If this is a new installation, rename the _objects_ directory to
objects. If this is an existing installation, please skip this 
step.

	7. mv _objects_ objects  [Only if this is a new installation]

Reuse your saved version of dir or edit it as necessary


	8. ./build.pl

This step builds the software using the build.pl program taking advantage
of the build_env.conf file. Before doing this step verify that the perl
compiler is located where several scripts expect them to be, namely in
/usr/bin/perl. Perl is used by the build-env.pl script and the
../htmlbin/info script, and maybe a few others. Either edit these scripts
to find the Perl compiler where it is located on your system or, if
you have the necessary system privelege, create a symbolic link to
the location of your Perl compiler as

		ln -s your_location_of_perl_compiler /usr/bin/perl

The cgi-lib.pl perl code is provided in the ../htmlbin directory since it
is needed by the info and the perl_utils.pl scripts. You can delete the
cgi-lib.pl file from the ../htmlbin directory if you have your own copy.
If you are not sure, then just leave the one provided in place.

If there are errors during the build or if you have questions, please 
contact rgroman@whoi.edu.


	9.a Using new dir version [OPTIONAL]
	
In ../htmlbin rename _dir_ to dir but be sure to look at your
existing copy of dir (saved in step 2 above) to see what has to
be changed.

		mv  _dir_ dir

	9.b Using new version of dir-join2 version [OPTIONAL]
	
In ../htmlbin rename _dir-join2-new_ to dir-join2-new but be sure to
look at your existing copy of dir-join2-new (saved in step 2 above) 
to see what has to be changed.

		mv _dir-join2-new_ dir-join2-new


	9.c To get back your copy of the objects directory move
it back in place, if necessary:

		cd <JGOFS/GLOBEC root>
		mv objects-save objects
		
or
		mv ~/objects-save objects
		
if you saved this directory structure in your home directory. However,
this step should not be necessary since the fast install does not
automatically replace your existing objects subdirectory.
	
If you want to use the empty version, then issue the following:

		mv _objects_ objects
		
