Getting started at the cAos temple

for cAos builder access and use:
        - set up an account at:
                https://temple.caosity.org/
        - upload priv's will be granted (manual
                        'vetting' process presently)
        - transfer in a SRPM by
                rsync <srpm>   <userid>@temple.caosity.org::<userid>
                        (password is your chosen 'temple' password);
                        presently a management interface for
                        resets being re-written by me, but works
                        sufficiently now - Bug XXX
        - with yum, it is easy enough to set up a local
                cAos build chroot instance on a RH distro based box;
                that is how cAos was bootstrapped
        - log into the 'temple' and go to release it to the
                        autobuilder by 'adopting' it;
                        optionally, adding 'Hints'
                       (which are soft BuildReqs):  URL is
                https://temple.caosity.org/pkg_adoptions.php
        - one does buildchain needs that way as well. It is
                probably the case that we should have the capability
                to set up and manage 'per user' development yum
                archives, so a given chroot can be updated, on a
                per user basis, to do remote testing.  But it
                is not unreasonable to expect a 'general case' cAos
                developer will already have a buildbox, and so
                not need this feature much.  Someday ...
        - the autobuilder will build it and place it in the
                        untrusted archive in about an hour (again 
			there is a non-visible release review process).
                        Ditto buildlogs become visible,  XXX add 
			base URC; The Build Turn for
                        the builder is under an hour; I am
                        working a design on a 'EoBuild notification'
                        system for buildresults - Bug XXX

It ain't much, but it is enough to produce a traceable, and functional
public build system

------------------------

TBD: - Build error evaluation; troubleshooting common build problems; 
	local fork and fix process outline; filing against SRPM with 
	Adopter; sending patches upstream

--------------
Initial - RPH - 040129
couch:~/caos/getting_started_temple.txt
external: http://www.herrold.com/caos/getting_started_temple.txt
----------------