Build Farm/New Package Access

Purpose
Outline a method for bringing in new packages from which to 
generate build sets.

Function
New packages from which to generate build sets must be added
to the 'package' table periodically.  The status and unit_gate
fields must be set to the appropriate values.

Scenario:  Use Gentoo Host to pull packages and as a unit 
    gate.  This host will be configured to update only packages
    we want.  Periodically we will run the update and it will
    record any new packages in BRT.  If it successfully
    builds the package it will indicate a 'PASS', otherwise it
    will flag that version as a problem and not try to
    pull it again until an administrator intervenes.

Benefits:  
    1.  Automatically detect packages as they are released, 
        or if that is not fast enough put out our own ebuilds 
        and submit to Gentoo or local override tree. 
    2.  Gentoo host can do unit_gate test.
    3.  Easy to set up, like SUT with cron job.


Drawbacks:
    1. Gentoo specific.  Since we are currently using Gentoo, this is 
        okay for now.  However it may not be a long term solution.
    2. Any custom ebuilds might not be the final one for a release.  
       If we begin generating ebuilds it may take several passes to get 
       right.

Script needed 
    1. Get new packages-Run through 'cron' 
        - Script to parse output of emerge -up  and 
        - Insert into 'packages' with status='NEW', unit-gate='PENDING'.
        - Run build portion for each package.
        - Collect results-save for 2 weeks
        - Mark 'unit_gate' to 'PASS' or 'INVESTIGATE'
        - Mask package version if 'BROKEN'

    2. Admin-mask and unmask packages
        - User can 'unmask' package if issue is resolved
    3. Admin-mark unit_gate to 'BROKEN'    


Extra steps
    1. User will investigate packages that do not build. and then 
        set the package mask accordingly.