# Document for new caos developers
# Beta-1

How to get an account:

If you are interested in contributing or maintaining RPM's for the caos project
you need to start by requesting a temple account here:
	https://temple.caosity.org/account_request.php
	(cookies are being flakey on sessions bugrep 223 at
	https:bugzilla.caosity.org/)
Someone will then notify you by e-mail when your account is created, and you will be
given access based on your role as a maintainer (rsync upload privs, etc.)
	Also setup a Bugzilla account at:
	https://bugzilla.caosity.org/


How to setup a build environment:

Once you have been granted rsync access, you will be able to get the latest
buildroot. First create a directory somewhere that has about 1G of space
(i.e. /home/buildroot). Then get the latest updated buildroot like this:
	rsync -avH --delete temple.caosity.org::buildroot-1 [path]/buildroot/
Once you have updated you can 'chroot [path]/buildroot/' and begin creating your
packages


How to rsync your RPM's and use the temple interface:

Once you have been granted rsync access you will be able to sync your RPM's 
like this: rsync -avH --delete SRPMS/ username@temple.caosity.org::username
	(password is your chosen 'temple' password)
After you have uploaded your RPM's to temple you can login at 
https://temple.caosity.org and click on "Package Depot" to see your RPM's.
From the Package depot screen you will see that your freshly uploaded RPM's are 
not currently in any Repository. In order to release your packages to the
autobuilder, you will need to click on the SRPM and assign 
it to cAos-1 by clicking "Submit Query". 

	Optionally, add 'Hints' (which are soft BuildReqs):
	[ button at bottom of form ]

	After you have assigned it, the autobuilder will build it and place it 
	in the "Crazy" repository in about an hour. Once your RPM has recieved 
	enough QA votes, it will be moved into "Current".

Note: If the package you synced is not "owned" by you then, somone will need
to assign it to you Otherwise you will be able to 'adopt' it. 


Procedure for updating your packages:

If the package is not in "Current" yet, you can obsolete it by clicking on the
SRPM in your package depot, and then clicking on obsolete. You can then remove
the old package from your local directory and rsync the new one up.

Important Note: If your package is in "Current" do not obsolete it, as this
can potentially cause problems if your package is a dependency for other
packages.

master at: http://www.jamrockmusic.com/~ras1/temple.txt