Managing Build Sets

'Build sets' will be defined as a group of packages made up of 
    various 'packages sets'.

build_set Field Definitions:
     bat_gate:  PASS or FAIL
     build_set_def_uid:  relate back to build_set_def
     version:  
     status:  ACTIVE or INACTIVE

'Package sets' are sets of packages and versions, along with 
properties like install order and some dependency information.
The property 'package_set_type' will be 'BASE' or 'DELTA'.  A
BASE  set will be the definition and will not change.  The DELTA
set will include any desired upgrades on the software already
included in the corresponding BASE set. 

Package_set Field Definitions:
     package_set_type:  BASE or DELTA
          BASE means a fully defined set that will not changed
          DELTA means a set of changes from a BASE set
     distro_tag_uid:  Ties back to table distro_tag in STP.  Can 
          be NULL.

Table package_set_to_package Field Definitions
     install_order:  order to install packages in, can be NULL 
          and the it will order by package uid.
     build_only: 0 or 1, where '1' represents packages to remove 
          before running a test.
     upgrade:  0 or 1, where '1' indicates packages should be 
          updated.
     
Table package Field definitions
     software_type:  usually will match descriptor minus any version.
     unit_gate:  PASS or FAIL a unit test.
     status:  ACTIVE or INACTIVE or BROKEN
   

A 'Build Set Definition' will have the BASE package sets defined.  
Change sets will be made and applied for the 'build set'. 
build_set_def Field Definitions:
     status:  ACTIVE or INACTIVE
     continues_build_set_def:  uid of build set where a break to 
              the new build_set_def was made.  Will be NULL for 
              the initialbuild sets.
     current_version:  last build_set made ACTIVE.

New build sets and package set should be generated automatically or manually.
The package sets generated automatically will be ACTIVE while manual ones will
be PRIVATE.  The ACTIVE ones will be used to generate build sets automatically.
If one desires to include a PRIVATE set in the chain, changing its status to
ACTIVE will do it.  Build sets will be generated when a new release of a package
with the same package type as a package in the base marked with 'upgrade' field 
of the package_set_to_package table is put out.

User Generated Build Sets

Users may want to generate their own build sets.  They should not have to go
through a complicated process to do this.  They should be able to choose a 
build set and specify new packages or upgrades that they wish to include.
As a possible implementation these additional changes may be included as a 
new package set or in table 'build_set_to_packages'.  They user should not have 
to know how this is done.

Utilities to create User Build Set: