                Release notes-build software 1.5   (Jan 15)
                [Note: build version in [] is package version, not version of bu
ild.pl itself]
[build 1.5]

        New build-env.pl parameter to allow some OOserver software to be
built in a data server
        New build-env.pl parameter to allow OOservers to locally access data
servers instead of accessing via http

===========

[build 1.4]
        Various adjustments to build-env.pl for building OOservers
        Don't require .conf file software if there is no .conf file

===========

[build 1.3]

        build 1.3b includes more input validation in build-env.pl

        build 1.3 (& 1.3a) include modifications to build-env.pl to support
a new source for the information displayed by the "Documentation" link.
This work is described in the info.doc file included with info 4.0 (& 4.1).

        Further modifications to build-env.pl allow user-specified values
to be to come from a file other than build-env.pl.  Values specified
in this other file supersede values specified in build-env.pl.  For more
information, please see build-env_conf.doc included in this release.

===========

[build 1.2]

        A compile-time definition for linux systems has been added for those
programs whose make files, etc can use them.

        A USEDATABASE environment variable will be defined if a user
so chooses.  See _build-env_.pl for a description of this variable
[Note: this capability expanded in build 1.3.  Please see the info.doc
file included w/ info 4.0.  If that is not installed, the expanded
capabilities are moot]

        Bug fix: make  build.pl clean  work



        When a web data page is displayed by the JGOFS system, there is
a link labeled "Download and Other Operations".  This link points to
a program located on a computer host called the "option server".
This version of build-env.pl redefines the name of that program
in order to implement a new logical operator on the "Subselections" page.
        Except for these enhancements, the definition in old versions
of build-env.pl will continue to work.

        In the exceptional circumstances below, the newly
made modification will NOT work, and another definition is required.
1)      The build 1.1b definition points to a program on the option server
   called "otheropt2".   The new definition is "otheropt3".  The new definition
   will NOT work unless the option server has a program named otheropt3.
   This program was added to the default option server (optserv1.whoi.edu)
   1 Jun 09.
2)      If the option server is in fact the default (optserv1.whoi.edu),
   then the new definition assumes that the JGOFS server
   being built with build-env.pl is being built with at least version 3.2
   of a JGOFS software program called outer.
        The packaging which includes this document is expected to include
   outer 3.2.  If the new build software is being retrofitted into an
   old data server, an older definition should be used.  The choices
   are "otheropt" and "otheropt2".  They are described in the build 1.1a
   readme file.

=========================

Installation issues:

        build-env.pl is  delivered as _build-env_.pl to avoid an
accidental overwriting of an existing build-env.pl, which is
likely to contain site-specific information.
        It is up to the installer to reconcile new, needed features from
_build-env_.pl into a "master" build-env.pl, which can be an onerous task.
It may be eased by noting that build-env.pl is divided into thirds by
2 lines of hash marks (###).  Most site-specific modifications will have
been made in the middle third.  Most modifications in new releases will
have been made in the first and last thirds.  Assuming no local
modifications outside the middle third, and unless noted elsewhere in
these release notes, a correct local version of build-env.pl can be
made by grafting the middle third of the current version of build-env.pl
over the middle third of _build-env_.pl and renaming _build-env_.pl
to be build-env.pl.  It's a good idea to back up the original
version of build-env.pl before doing the rename.
        As of build v 1.3, there is a facility to separate user modifications
into a file other than build-env.pl.  Please see config_file.doc, included
in the build package
